Setting properties in pom.xml from command line

Hi, Is it possible to inject properties into pom.xml from the command line at runtime? consider this dependency: dependencies dependency groupIdmygroup/groupId artifactIdmyartifact/artifactId version${mygroup-myartifact.version}/version

Re: Setting properties in pom.xml from command line

Yes, it is. -Dmygroup-myartifact.version=xxx However, for your example it would be a very bad thing as your pom will not be consumable by any client. /Anders On Fri, Apr 15, 2011 at 10:37, Geir Gullestad Pettersen gei...@gmail.comwrote: Hi, Is it possible to inject properties into pom.xml

Re: Setting properties in pom.xml from command line

The trick is to give the artifact a *default* version in properties so you can override from the command line but still build without any command line options; properties mygroup-myartifact.version1.1/mygroup-myartifact.version properties Then you can build with

Re: Setting properties in pom.xml from command line

Yes, but I still don't think this is a good idea for dependencies. What will happen is that the dependency declared in the pom being deploy is not what was used during build. Can lead to strange things IMO. /Anders On Fri, Apr 15, 2011 at 12:14, Kristian Rosenvold kristian.rosenv...@gmail.com

Re: Setting properties in pom.xml from command line

Anders, What other suggestion do you have for testing that a something works with multiple versions of something else? I completely agree that running 'install' let alone 'deploy' with a profile that changes a version is a really bad idea. But it's an effective mechanism for compatibility

Setting properties at runtime in a plugin component?

find any examples or documentation. -- View this message in context: http://www.nabble.com/Setting-properties-at-runtime-in-a-plugin-component--tf4707240s177.html#a13454401 Sent from the Maven - Users mailing list archive at Nabble.com

setting properties in the POM [m2]

Hi, I'm trying to setup a build mechanism that is able to build a version of our projects based on a property (${project.version}). I have tried to include this property in my POM but since maven2 doesn't use property files anymore, it doesn't seem to recognize this property, even when I

Re: setting properties in the POM [m2]

${project.version} is actually an expression that gets version (which in your case is an expression that at that point evaluates empty). It can actually be shortened to ${version}. What you probably want to do is set the version and then use the expression for the dependencies. - Brett On

Setting properties in Maven 2

Hi, Could anyone tell me how to set the following properties in maven 2 alpha 1? maven.repo.remote=file://c:/projects/idportal/Products/InformationDeliveryPortal/mavenrepo maven.site.deploy.method=fs maven.changelog.basedir=c:/projects/idportal/products/informationdeliveryportal/source/java

RE: Setting properties in Maven 2

approval. - Miguel de Cervantes - -Original Message- From: Will Gwaltney [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 12, 2005 8:25 AM To: users@maven.apache.org Subject: Setting properties in Maven 2 Hi, Could anyone tell me how to set

Re: Setting properties in maven.xml

Excellent, thanks Dan, that works. Still making the mental step from ant to maven when it comes to writing goals. dan tran wrote: try this, j:set var=maven.tomcat.precompile value=false/ -D On Wed, 17 Nov 2004 10:43:30 +, Andrew Watters [EMAIL PROTECTED] wrote: Is it possible to set

Setting properties in maven.xml

Is it possible to set properties in maven.xml using the property name= value=/? For example, the following code runs ok but the goal ignores the property that I have set property name=maven.tomcat.precompile value=false/ attainGoal name=tomcat:deploy/ However, if I set the property in

Re: Setting properties in maven.xml

try this, j:set var=maven.tomcat.precompile value=false/ -D On Wed, 17 Nov 2004 10:43:30 +, Andrew Watters [EMAIL PROTECTED] wrote: Is it possible to set properties in maven.xml using the property name= value=/? For example, the following code runs ok but the goal ignores the property

Setting properties

I'm sure the answer to this will be don't do it like that, but here goes... I have a base project (call it A) whose maven.xml contains the following: goal name=all m:reactor basedir=${basedir} includes=*/project.xml goals=${maven.all.goals} ignoreFailures=false/

Re: Setting properties

On Wed, 7 Jul 2004 15:03:51 +0100, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: I'm sure the answer to this will be don't do it like that, but here goes... When would you ever get a response like that on a Maven list? :) Anyway, I think the answer is to add scope=parent to your j:set/.

RE: setting properties

Networks OSS    gsm: +49-177-9413928, fax: +49-211-94123988    Heltorfer Straße 1, 40472 Düsseldorf, Germany -Original Message- From: ext Sonnek, Ryan [mailto:[EMAIL PROTECTED] Sent: Monday, March 01, 2004 4:42 PM To: 'Maven Users List' Subject: setting properties Any pointers

RE: setting properties

Hi, -Original Message- From: ext Sonnek, Ryan [mailto:[EMAIL PROTECTED] Thanks for the reply. I can't say I fully understand why it's needed from within maven.xml and not from the command line, unless settings passed from the command line are wrapped up and fed into maven's

RE: setting properties

Hi Heiko, -Original Message- From: ext Heiko Kundlacz [mailto:[EMAIL PROTECTED] Maybe it helps to check the deploy plugin. The deploy plugin will be invoked from within the jar plugin. And if I am not wrong, some properties will be set in the jar plugin. Thanks for the tipp. I

Re: setting properties

Maybe it helps to check the deploy plugin. The deploy plugin will be invoked from within the jar plugin. And if I am not wrong, some properties will be set in the jar plugin. Heiko [EMAIL PROTECTED] wrote: Hi, -Original Message- From: ext Sonnek, Ryan [mailto:[EMAIL PROTECTED]

Re: setting properties

Any pointers on how to set properties from within my maven.xml? I've got a short custom goal to set properties, then call install: goal name=all:install j:set var=maven.test.skip value=true / attainGoal name=multiproject:install-snapshot / /goal I just ran into the same

RE: setting properties

. -Original Message- From: Oliver Nölle [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 02, 2004 10:44 AM To: Maven Users List Subject: Re: setting properties Any pointers on how to set properties from within my maven.xml? I've got a short custom goal to set properties, then call install

setting properties

Any pointers on how to set properties from within my maven.xml? I've got a short custom goal to set properties, then call install: goal name=all:install j:set var=maven.test.skip value=true / attainGoal name=multiproject:install-snapshot / /goal when I run this goal, tests

Re: setting properties

Sonnek, Ryan wrote: Any pointers on how to set properties from within my maven.xml? I've got a short custom goal to set properties, then call install: goal name=all:install j:set var=maven.test.skip value=true / attainGoal name=multiproject:install-snapshot / /goal when I run

RE: setting properties

: matthew.hawthorne [mailto:[EMAIL PROTECTED] Sent: Monday, March 01, 2004 10:30 AM To: Maven Users List Subject: Re: setting properties Sonnek, Ryan wrote: Any pointers on how to set properties from within my maven.xml? I've got a short custom goal to set properties, then call install: goal

Re: setting properties

Sonnek, Ryan wrote: Thanks for the reply. I can't say I fully understand why it's needed from within maven.xml and not from the command line, unless settings passed from the command line are wrapped up and fed into maven's plugins. I read through the wiki, and tried to get it to work with the

Setting properties for repositories with maven-war-plugin

Hi, what properties must be set for maven-war-plugins's goals war:install war:deploy for the local and remote repository? I can't find it in the documentation for the maven-war-plugin TMS - To unsubscribe, e-mail: [EMAIL