> > > 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.
Ok, that's fine with me ;-)
> 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.
No, you're right, that would be hell! And anyway, that's not part of this discussion
:).
Alef
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
