On 4/5/07, Lacoste, Dana <[EMAIL PROTECTED]> wrote:
OK, well, I still don't have a solution as to why this doesn't work :)
But I've figured out a way to "make it go" at least :)
http://www.nabble.com/Classloader-issue-with-ant-optional-tasks-in-a-hie
rarchical-structure-tf2431669s177.html#a6780357
That earlier post (October 12, 2006) showed someone with a similar
problem.
The problem appears to be that if the maven-antrun-plugin is called
BEFORE
you declare the dependencies as in below (i.e. from a different level
pom
in the project), then these dependencies will be IGNORED
So you have to include the dependencies mentioned in the above link,
in the format in the above link, in the first call to
maven-antrun-plugin
in the project.
So, basically, you need to do it in the super pom.
And if you want it to work in the "child" pom, I guess you have to do it
there too.
Any suggestions on how to make that work easier? Perhaps a way of
defining plugin dependencies in the parent pom without calling them, so that if
the plugin is called anywhere in the child, it will inherit those
dependencies properly?
Hei Dana,
http://jira.codehaus.org/browse/MNG-1323
One of the most voted issue I think.
Seems like there's no solution today. At least I don't have a work-around.
I would probably try to use a different approach when trying to
generate this file. Avoid using the ant run plugin and a regular
expression altogether. Can't you just use the standard resource
filtering (maybe filtering it twice, once for 'define VERSION' once
for 'define TEST') ?
If that doesn't work, you can also write your own maven2 regexp
plugin... That shouldn't be too much work.
Cheers,
Jerome (also Lacoste, from the other side of the ocean)
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
