> I ran into this yesterday. It turned out that my project.xml
> was missing
> its tag. I inserted at the end and all is well.
I had a build tag already, but this did lead me to the solution.
My build tag had an (evidently) outdated tag in it (probably from beta 7,
not sure):
*
I ran into this yesterday. It turned out that my project.xml was missing
its tag. I inserted at the end and all is well. YMMV
> There really is a resources:copy dynamic tag defined, it's in maven.jar
> in a file called driver.jelly.
>
> Can you post the result of running 'maven -e '??
> --
> dI
There really is a resources:copy dynamic tag defined, it's in maven.jar in
a file called driver.jelly.
Can you post the result of running 'maven -e '??
--
dIon Gillard, Multitask Consulting
Blog: http://blogs.codehaus.org/people/dion/
Work: http://www.multitask.com.au
Lester Ward <[EM
Looks like an old version of the xml taglib
--
dIon Gillard, Multitask Consulting
Blog: http://blogs.codehaus.org/people/dion/
Work: http://www.multitask.com.au
Martin Skopp <[EMAIL PROTECTED]> wrote on 15/07/2003 05:32:57 PM:
> Hi folks,
>
> discovered problems with my own maven proj
The reactor problems will definitely be sorted out in rc1.
Cheers,
Brett
-Original Message-
From: James Ward [mailto:[EMAIL PROTECTED]
Sent: Monday, 14 July 2003 3:05 PM
To: Maven Users List
Subject: Re: b10
Great work Maven team!
The .tgz seems to work fine. I just have two comments
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
