Using of properties from settings.xml

["Balasubramanian, Ravi Shankar" <rb...@informatica.com>]

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..."

 

Re: Using of properties from settings.xml

[Dan Tran <da...@gmail.com>]

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 <rb...@informatica.com> 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..."
>
>
>
>
>

Re: Maven2 compile in windows 2000

[Carlos Sanchez <ca...@apache.org>]

you need the latest version of the compiler plugin from svn until it's released


On 1/29/07, Niels Gylling <ng...@it-practice.dk> wrote:
> Some of our users still run Windows 2000 and now they get an error
> during compile of max command length exceeded - propably around 2k chars..
>
> I believe this happens during a forked compile where some artifacts
> required the 1.3 compiler.
>
> Are there any known workarounds in m2?
>
> /Niels
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>


-- 
I could give you my word as a Spaniard.
No good. I've known too many Spaniards.
                             -- The Princess Bride

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org

Maven2 compile in windows 2000

[Niels Gylling <ng...@it-practice.dk>]

Some of our users still run Windows 2000 and now they get an error 
during compile of max command length exceeded - propably around 2k chars..

I believe this happens during a forked compile where some artifacts 
required the 1.3 compiler.

Are there any known workarounds in m2?

/Niels

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org

Re: Inherited plugin configuration

[franz see <fr...@gmail.com>]

Good day to you, Niels,

Care to share the buid logs of your console so that we can have a look at
it? :-)

Thanks
Franz


Niels Gylling wrote:
> 
> I have a plugin I wish to define at a parent pom so that all child 
> projects can share the configuration.
> 
> At the parent level it is loaded as
> <plugin>
>   <groupId>..
>   <artifactId>sample-plugin</artifactId>
>   ..
>   <configuration>
>     <name>value</name>
>   </configuration>
> </plugin>
> 
> so that the child projects can invoke
> mvn sample:some-goal
> 
> and refer to the parent level config.
> 
> This works fine, but if, in a child project, configure an execution
> to this plugin as
>    ..
>    <execution>
>      <goals>
>        <goal>some-clean-goal</goal>
>      </goals>
>      <phase>clean</phase>
>     </execution>
> 
> the some-clean-goal gets executed twice when I invoke
> 
> mvn clean
> 
> Any clues??
> 
> /Niels
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
> 
> 
> 

-- 
View this message in context: http://www.nabble.com/Using-of-properties-from-settings.xml-tf3044487s177.html#a8487636
Sent from the Maven - Users mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org