I just notice you are using ${project.version}. This particular var is your
current pom's version.
which may explain why it no longer work after install. Try a different
variable name.
-D
On 1/22/07, Balasubramanian, Ravi Shankar <[EMAIL PROTECTED]> wrote:
Hi,
My local projects(installing it only to my local repository) has to be
built on a user-dependent way where-in the user specifies the version
for the dependencies he is interested in, in his settings.xml file. And
when I install my local project into my local maven repository, I want
the pom to be resolved. Is there a way by which I can accomplish this?
-R
-----Original Message-----
From: Dan Tran [mailto:[EMAIL PROTECTED]
Sent: Monday, January 22, 2007 12:28 PM
To: Maven Users List
Subject: Re: Using of properties from settings.xml
The current deploy process does not alter your pom.
Just curious, why do you want to do that?
If you do that, how do you reproduce your deployed artifact? since your
settings.xml change over time.
-D
On 1/21/07, Balasubramanian, Ravi Shankar <[EMAIL PROTECTED]>
wrote:
>
> Hi,
> I just want to be running "mvn install" and the pom that gets
installed
> for my project should have the property names replaced with their
> values. Is there any way by which I can accomplish this?
>
> Regards,
> Ravi
>
> -----Original Message-----
> From: Dan Tran [mailto:[EMAIL PROTECTED]
> Sent: Saturday, January 20, 2007 3:31 PM
> To: Maven Users List
> Subject: Re: Using of properties from settings.xml
>
> I think you need go thru release process to deploy ( ie
> maven-release-plugin) so that
> the expression can be replaced. It does not do so in deploy-plugin
>
> -D
>
>
> On 1/20/07, Balasubramanian, Ravi Shankar <[EMAIL PROTECTED]>
> wrote:
> >
> > Hi all,
> >
> > I am using values of properties defined in my settings.xml file into
> my
> > pom.xml. For instance, I have parameterized the version for m
project
> > dependencies in the settings.xml with a property called
> > "project.version". I am using this property in my pom.xml as
follows:
> >
> > <dependency>
> >
> > <groupId>Group1</groupId>
> >
> > <artifactId>Artifact1</artifactId>
> >
> > <version>${project.version}</version>
> >
> > </dependency>
> >
> >
> >
> > This works fine when I build my current project where in the
> appropriate
> > version of the dependencies gets downloaded. However, when I
> > install/deploy my project into the repository, the installed pom
file
> > for the project still has the version parameterized in it and does
not
> > have the original property value replaced in it. Hence when other
> > projects use my project as a dependency, it is not able to resolve
the
> > version of the dependencies.
> >
> >
> >
> > When my project is used as a dependency in other projects, maven
fails
> > the build saying it is not able to download
> > Artifact1-${project.version}.
> >
> >
> >
> > Can anybody please let me know how do I resolve this?
> >
> >
> >
> > Regards,
> >
> > Ravi.
> >
> > "Tough times never last, but tough men do..."
> >
> >
> >
> >
> >
>
> ---------------------------------------------------------------------
> 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]
