On Wed, 22 May 2002, Alef Arendsen wrote:
> > I'd like to leave the ability to specify what the name of the
> > webapp is
> > based on the maven.j2ee.webapp.name (or whatever it is)
> > property, and the
> > current directory structure. Anything else makes it
> > difficult to create
> > multiple webapps out of a single code base.
>
> The problem is that I'd like to have one consistent build file that does not change
>at all for ANY project I have. The only thing that changes is the project.xml file.
>If I would have to specify a separate property, I would either have to specify that
>in my ${user.home}/build.properties file or in the project's build.xml file. That
>seems nasty.
Right, and the default name for the property comes from the project name.
So where we currently do the check for the property being set and then
failing if its not, we would modify that to set the property to the
project name if it was missing.
>
> It might be an option to put something in the project.xml like this:
>
> <wars>
> <war name="firstwar">
> <!-- extra resource might be specified here (just as with <jar>) -->
> </war>
> <war name="secondwar">
> <!-- extra resource might be specified here (just as with <jar>) -->
> </war>
> </wars>
We are *desperately* trying to keep the POM as clean as possible. Adding
j2ee specific artifact tags into the pom isn't clean, unfortunately.
There has to be a better way to approach this.
Glenn McAllister
> This would make everything pretty consistent I would say (but it's just a hunch).
>I'm also thinking about the discussion of generating multiple jars (client jars,
>rmi-server-jars, etc.) out of one project (was discussed some time ago)
Well, it does and doesn't answer the problem. Are we willing to add a new
element to the pom everytime a new Java artifact comes along?
Personally, I'm not. Thats a maintenance nightmare waiting to happen.
Glenn McAllister
SOMA Networks, Inc.
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
