jmaxwell wrote:
Dan,
I might just cheat and use xslts to create the poms (not pretty).
I hate breaking the DRY (Don't Repeat Yourself) rule.
I do wish that the ant task evaluated ant properties in the poms.
At least in this way I could set the value in one place (build.properties or
parent pom).
Then you could have a pom similar to this:
<project>
<modelVersion>4.0.0</modelVersion>
<groupId>${mymodule.groupId}</groupId>
<name>${mymodule.name}</name>
<version>${mymodule.version}</version>
<artifactId>${mymodule.version}-lib</artifactId>
<packaging>zip</packaging>
</project>
You could do it the other way around. If you define your pom as a
reference in your ant script like this:
<artifact:pom id="maven.project" file="pom.xml" />
Then you can reference the values from it as ant properties like this:
<echo>The version is ${maven.project.version}</echo>
dan tran wrote:
the alternative ( my be not desirable by you ) is to create one maven
project to call your ant's build which
creates multiple artifacts?
-Dan
On 4/28/06, jmaxwell <[EMAIL PROTECTED]> wrote:
Dan,
I am using the "Maven 2.0.4 Tasks for Ant".
Cheers,
Jeff
--
View this message in context:
http://www.nabble.com/Maven-Ant-Tasks-and-Multiple-artifacts-in-one-POM-t1525854.html#a4147709
Sent from the Maven - Users forum at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
View this message in context:
http://www.nabble.com/Maven-Ant-Tasks-and-Multiple-artifacts-in-one-POM-t1525854.html#a4148199
Sent from the Maven - Users forum at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Dennis Lundberg
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
