Will the "deploy" phase actually resolve this version property? Or I have to go through maven release plug-in?
-----Original Message----- From: news [mailto:[EMAIL PROTECTED] On Behalf Of Insitu Sent: Wednesday, September 12, 2007 12:13 AM To: users@maven.apache.org Subject: Re: properties in settings.xml "Huang, Yan" <[EMAIL PROTECTED]> writes: > Hi, > > I noticed that the "install" phase does not resolve the properties that > are defined in settings.xml. For example, I use a property in my > settings.xml to define the release version: > > <profile> > <id>DefaultProfile</id> > <activation> > <activeByDefault>true</activeByDefault> > </activation> > <properties> > <myversion>1.1.1.1</myversion> > </properties> > </profile> > > > Now, I have a pom that access that property: > > <groupId>myexample.myexample</groupId> > <artifactId>foo1</artifactId> > <version>${myversion}</version> > > When I run "mvn install", it does creat and install foo1-1.1.1.1.jar in > my local repo in ~/.m2/repository/myexample/.... However, when I look at > the foo1-1.1.1.1.pom file, the "version" tag is not resolved and instead > it still refers to ${myversion}. Is it a problem? AFAIK this is perfectly normal: The deployed .pom file is the actual pom of the project without any modification. You can find the effective pom (ie. the one used to build the artifact) inside the META-INF/ directory of the jar. The rationale behind this (speaking within control of more knowledgeable maven developers) is that the deployed pom can be used as a dependency to construct another pom withing another process, where the variables would need to be instantiated to other values according to settings/profiles/whatever. HTH -- OQube < software engineering \ génie logiciel > Arnaud Bailly, Dr. \web> http://www.oqube.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
