The release plugin does handle properties in dependencies, just take a look at the maven poms themselves. If properties won't work, you'd probably have to build your own piece of code.
On Fri, Aug 14, 2009 at 12:15 PM, GRELLIER SEBASTIEN<[email protected]> wrote: > Hi everyone > > I would like to be able to get the versions of my project dependencies > so that I can reuse them in a resource file, through the filtering step. > > Say my resource file is something like: > <dependency name="dep1" version="${dep1.version}" /> > <dependency name="dep2" version="${dep2.version}" /> > <dependency name="dep3" version="${dep3.version}" /> > > So when I run mvn package, I expect it to be: > <dependency name="dep1" version="1.0.0" /> > <dependency name="dep2" version="1.0.1-SNAPSHOT" /> > <dependency name="dep3" version="1.1.1" /> > > I do not want to define the versions of my dependencies as properties > because of the maven-release-plugin which does not handle such a > situation. And I do want to use the release plugin. > > I thought it would be easy but cannot figure out how to do that! > I checked the dependency-plugin but failed to find a solution. > I tried to use project properties like for example > ${project.dependencies.versions} but failed as well. > > Did I miss something? > Do I need to develop my own piece of code for that? > > Thanks in advance for your help. > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
