But it needs to be clarified that the ant-plugin in rc1 isn't this fixed
version...its 1.4. I downloaded and installed the rc1 distribution and
ran the ant goal, it generated absolute paths. I had to upgrade the
plugin to 1.5 to get the fix.
-Mark
[EMAIL PROTECTED] wrote:
It's been fixed for a
It's been fixed for ages
--
dIon Gillard, Multitask Consulting
Blog: http://blogs.codehaus.org/people/dion/
__matthewHawthorne <[EMAIL PROTECTED]> wrote on 29/01/2004 10:29:38 AM:
> Mark R. Diggory wrote:
> > And to elaborate even more, it also happens to
> > ${pom.build.unitTestSourc
Ahhh, I just discovered the joy's of
maven -DgroupId=maven -DartifactId=maven-ant-plugin -Dversion=1.5
plugin:download
fixes everything... :-)
__matthewHawthorne wrote:
Mark R. Diggory wrote:
And to elaborate even more, it also happens to
${pom.build.unitTestSourceDirectory}
I see, this was altered in the CVS head recently. Sorry for the traffic.
-Mark
Mark R. Diggory wrote:
And to elaborate even more, it also happens to
${pom.build.unitTestSourceDirectory}
Is this something that changed just recently?
-Mark
Mark R. Diggory wro
Mark R. Diggory wrote:
And to elaborate even more, it also happens to
${pom.build.unitTestSourceDirectory}
Is this something that changed just recently?
It's been like that for awhile. I've always had to manually hack the
Maven-generated Ant build files to re
And to elaborate even more, it also happens to
${pom.build.unitTestSourceDirectory}
Is this something that changed just recently?
-Mark
Mark R. Diggory wrote:
Just to elaborate, it happens on *nix too.
I have my tag set properly in the POM. It appears tha
Just to elaborate, it happens on *nix too.
I have my tag set properly in the POM. It appears that
the path is getting turned into an absolute before the template in the
ant plugin is run...
-Mark
Mark R. Diggory wrote:
I have a problem with the ant:generate task, it seems to be producing
