> However, you can't include a version number in the resulting war file
> name. Most webapp containers rely on the war file name being
> the correct
> default name of the application. Do you really want to stick
> a version
> number in there? :)
About the versioning you're right! No versioning there...
>
> 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.
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>
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)
alef
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
