On 20/12/2010 1:11 PM, Wayne Fay wrote:
I'm guessing that some sort of condition will need to be put into
place in the core-module's pom.xml file to let it know which
dependency it needs? Based on what is specified in an env variable or
Whenever you are looking for this kind of conditional building of your
projects, you should immediately think of "profiles."
You should also think "Why are my modules optional?"
Am I really trying to build separate artifacts? Should I have a simple
project that just builds the artifact with optional module 1 and another
that just builds with optional module 2 rather than a project that is
hopelessly complex and prone to errors and requires a lot of maintenance.
Am I mixing deployment environment information(properties, database
connections, site info, web service endpoints) with code. This should
not be done at all.
Ron
/Maven Profiles are like Good Intentions. They are far from evil but
they both can pave the way to hell./
This is well documented online if you just search for it.
Wayne
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
