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 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. Martijn -- Learn Wicket at ApacheCon Europe: http://apachecon.com Join the wicket community at irc.freenode.net: ##wicket Wicket 1.2.5 will keep your server alive. Download Wicket now! http://wicketframework.org
