(I've been working with Maven since at least 2004 and I think I *still* don't
get transitive dependencies.)
I have a pom.xml file of type pom that has some compile-scoped dependencies
in it. (P1 -> A(compile), B(compile))
I have another project that depends on this pom in provided scope (I'm
Hi,
I looked into this issue and committed a fix for it. The core problem
was that the 'attachartifact' task launched from the external Ant build
was working from a clone of the Maven project, instead of the project
itself. Can you try the latest 3.0.0-SNAPSHOT and report back?
Le
Hi,
I found a solution, not pretty, but it actually works:
in an pom-inline antrun task call a Javascript function with the
project as parameter, in Javascript one can do all interesting things
(loop over properties from an ant property file) and call the
attachartifact task.
Cheers,
Juergen
Hi,
if i correctly understand you have a property file for each environment
and maybe some other files and a base artifact (jar/war?) now it sounds
you have to build for each environment a different jar/war ?
Maybe something like this could help here:
Hi Jörg,
problem is, I have to build message driven beans, some 20, only difference
is the queue name in the deployment descriptor. Queue names are listed in a
property file.
I know that Maven wants no environment specific properties in artifacts,
but Sun defined the activation spec for MDBs. And
