Exactly...
-James
James CE Johnson wrote:
I can't seem to find the reactor
Is that the problem where some funky sequence of reactor usage causes
maven to forget what goals it has? I agree that's critical. Most of my
reactor-based goals now have to a new maven instance in order for
the buil
I can't seem to find the reactor & console problems in jira, but I know
we have talked about it a million times here on the list. I think that
bug fix it crucial for 1.0.
-James
On Wed, 2003-07-30 at 23:50, [EMAIL PROTECTED] wrote:
> If you have a fix or a change you would like to be in maven 1
Actually if you are packaging your war into an ear, you can specify the
context, or if you have jboss you can put a jboss-web.xml in your
WEB-INF and specify it there. Regardless, the default behavior should
be the same as the jar and ejb plugins where it is named with the
version. And of course
Great work Maven team!
The .tgz seems to work fine. I just have two comments...
I think the inconsistency between jar, war and ejb final.name's should
be fixed. For example:
The maven.war.final.name gets set to ${pom.artifactId}.war
while maven.ejb.final.name gets set to ${maven.final.n
