Hi,
I am migrating an M1 Jelly script over to an Maven2 plugin and encountering a
situation where I can actually end up defining numerous configuration
keys/properties in a project pom.
My use case is as follows:
I need to setup a 'build control' project that checks out a project defined by
an SCM location based on a 'target' invoked. (more on notion of target below).
Now, the 'build control' project:
o has its own POM
o has a notion of set of targets - UAT, integration, production...
yadayada
o has a notion of set of goals (tomcat5-stop, tomcat5-delete,
tomcat5-create, tomcat5-start...) for each of the targets.
o Targets have properties which are used by goals to do what they need
to do.
To enumerate an example: for an invocation of target UAT and goal j2ee-deploy,
I end up with properties like:
myproject.uat.tc5.server.port = 8100
myproject.uat.tc5.ajp.port = 8101
myproject.uat.tc5.worker.name = myproject
myproject.uat.tc5.db.jndi.name = jdbc/myproject
myproject.uat.tc5.context.path = /custom
myproject.uat.apache.vhost.name = myproject.company.co.nz
....so on and so forth
I am running into a situation where combinations of these Targets plus Goals
result in numerous properties (more than 100).
Could anyone suggest what might be a good way to factor/handle these or do I
really need to include all these properties in the project POM.
Much appreciate any pointers!
Cheers,
Rahul
