Le lundi 10 mars 2008, Matthew Tordoff a écrit : > Hi all, > > It looks like this could have been fixed in 2.0.9 which introduces support > for default profiles. I am guessing because I am defining my properties > within a profile , this is why it is not being read by the Maven ANT tasks. I just put a SNAPSHOT on http://people.apache.org/~hboutemy/maven-ant-tasks-2.0.9-SNAPSHOT.jar to let you check if it works for you.
> > Does anyone know when or how to find out when this version will be > available? I have looked on their roadmap and it seems like all issues have > been resolved for 2.0.9. Maven Ant Tasks 2.0.9 will be released 1 or 2 weeks after Maven 2.0.9. regards, Hervé > > Matt > > -----Original Message----- > From: Matthew Tordoff [mailto:[EMAIL PROTECTED] > Sent: 10 March 2008 16:26 > To: [email protected] > Subject: Bug within Maven ANT Tasks? > > > Hi all, > > I am using Maven ANT tasks to deploy a number of JAR files I produce as > part of my build. For each JAR file I have a corresponding pom.xml file > (not called pom.xml however:) ). > > I define references to these files in my build script as follows: > > <artifact:pom id="xxx.pom" file="xxx.xml"/> > > And later refer to them when I want to deploy as follows: > > <artifact:deploy file="xxx.jar"> > <remoteRepository refid="my-repository"/> > <pom refid="xxx.pom"/> > </artifact:deploy> > > Since I have multiple pom files (one for each JAR file to deploy) I need to > set the version of the JAR artifacts in every pom file. To avoid having to > do this I tried adding a property <deploy.version> inside of my > settings.xml as follows: > > <settings> > ... > <profiles> > <profile> > <id>default</id> > <activation> > <activeByDefault>true</activeByDefault> > </activation> > ... > <properties> > <deploy.version>version_number</deploy.version> > </properties> > ... > </profile> > </profiles> > ... > </settings> > > I have then put ${deploy.version} inside of the version tag of each of my > poms. The issue is that when I run my ANT deploy task this variable is not > translated from ${deploy.version}, however, if I rename each of the pom > files to pom.xml and run "mvn help:effective-pom" then the property name is > appropriately substituted with whatever I have set <deploy.version> to in > settings.xml. > > My question is... why is there this inconsistency in substitution? > > Any help would be greatly appreciated. > > Kind Regards, > > Matt > > _________________________________________________________________ > Telly addicts unite! > http://www.searchgamesbox.com/tvtown.shtml > > > _________________________________________________________________ > Free games, great prizes - get gaming at Gamesbox. > http://www.searchgamesbox.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
