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 < [email protected]> wrote: > > 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.version>1.1</mygroup-myartifact.version> > <properties> > > > Then you can build with -Dmygroup-myartifact.version=1.2-SNAPSHOT > > > Kristian > > Den 15.04.2011 11:16, skrev Anders Hammar: > > 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<[email protected] >> >wrote: >> >> Hi, >>> >>> Is it possible to inject properties into pom.xml from the command line at >>> runtime? >>> >>> consider this dependency: >>> >>> <dependencies> >>> <dependency> >>> <groupId>mygroup</groupId> >>> <artifactId>myartifact</artifactId> >>> <version>${mygroup-myartifact.version}</version> >>> <type>war</type> >>> </dependency> >>> </dependencies> >>> >>> ${mygroup-myartifact.version} can of course be set in the<properties> >>> tag, >>> but I need to be able to change the version number without changing >>> pom.xml. >>> This should peferrably be done from command line - is there a way to set >>> properties from commandline? >>> >>> Thanks, >>> Geir >>> >>> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
