Hello, I am writing a Wicket component that I would like to use in two different Wicket applications. One application is using Wicket 1.4.3, and the other is a legacy application using Wicket 1.3.6. Unfortunately upgrading this legacy app to 1.4 is not an option.
I'm using maven for my build process. Right now I am considering the following approach: 1. Set up a multi-module maven project. 2. Create a "common" module that contains all the code that will safely execute in both Wicket 1.3 and Wicket 1.4. 3. Create a "wicket13" module that contains the 1.3-specific code. 4. Create a "wicket14" module that contains the 1.4-specific code. That sounds like a lot of trouble. Can anyone think of a simpler solution, perhaps using maven build profiles? Or am I approaching this completely wrong? -- Matt --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
