Martijn Dashorst wrote:
On 3/8/07, Frank Bille <[EMAIL PROTECTED]> wrote:
Ok, so
http://www.nabble.com/Maven-2-project-structure-with-wicket-parent-tf3175043.html#a8812638is
still a problem?
Yep still a problem. But the biggest problem with getting all stuff
built in one go (*not* the release, but locally) could be resolved by
adding an 'all' profile that lists all modules. If you don't mind
building against 1.5, then that would solve the 90% usecase.
The new structure no longer requires profiles:
To just build JDK 1.4 stuff, execute mvn in the jdk-1.4 folder.
To just build JDK 1.5 stuff, execute mvn in the jdk-1.5 folder.
To build both, execute mvn in the root folder.
Getting it all into Eclipse:
mvn eclipse:eclipse in the root.
File | Import > Choose the root folder.
Check the ones you want and click OK.
The release build, and our bamboo should always explicitly use JDK 1.4
for wicket, extensions datetime and spring. The eclipse project
settings should also explicitly set a 1.4 profile to remove the
possibility to use 1.5 stuff.
Yeah. See previous threads on how mvn eclipse:eclipse will set you up
for 1.4 compliant code (no generics, etc.) but still use the default
(probably JDK 5) JRE libraries to build against. Hence the utility of
bamboo.
Al
