Bjorn Bringert | 1d580d0 | 2012-05-07 16:50:46 +0100 | [diff] [blame] | 1 | These folders host the maven metadata which are used to |
| 2 | build release binaries for hosting in the central maven |
| 3 | repositories. These are not considered the "canonical" |
| 4 | build, but are maintained seperately by (a) volunteer(s) |
| 5 | with an interest in easy use of Guava by the Maven build |
| 6 | system. |
| 7 | |
| 8 | As a convenience, these folders have been set up to |
| 9 | provide alternate packaging of the sub-pmodules, which |
| 10 | correspond to their respective java packages, with |
| 11 | sources symbolically linked back to the main project. |
| 12 | This will work to allow command-line builds on MacOS X |
| 13 | or other Unix platforms which support symbolic linking, |
| 14 | but is not known to work on Windows platforms. |
| 15 | (Obviously the deployed binaries in maven repostories |
| 16 | will work fine on any compliant JVM). |
| 17 | |
| 18 | The maintainers of these metadata have used M2Eclipse |
| 19 | to import these projects directly into Eclipse. Please |
| 20 | remember that this codebase uses @Override annotations |
| 21 | on methods which implement an interface method, and |
| 22 | therefore require a JDK 1.6 (or newer 1.5 with the |
| 23 | appropriate fix) to support this behaviour. Executing |
| 24 | Maven with an appropriate JAVA_HOME env is sufficient, |
| 25 | and these metadata do not have toolchain restrictions |
| 26 | currently set up. |
| 27 | |
| 28 | Christian |
| 29 | cgruber@google.com |