Re: Re: How to up date a property in a POM to a specific value
User questions for the mojohaus plugins should be posted here at the Maven users list. There is a separate dev list but that's for the development of the plugins. /Anders On Mon, Aug 28, 2017 at 10:20 AM,wrote: > Thank you for the hint. I will repeat my question on the Mojohaus > mailinglist. > > > Gesendet: Samstag, 26. August 2017 um 19:26 Uhr > > Von: "John Patrick" > > An: "Maven Users List" > > Betreff: Re: How to up date a property in a POM to a specific value > > > > If your talking about the codehaus version plugin which is now hosted > > at mojohaus, it's a different mailing list i think... > > > > http://www.mojohaus.org/versions-maven-plugin/mail-lists.html > > > > > > > > On 23 August 2017 at 21:07, Sandra Parsick wrote: > > > Thanks for your answers. > > > > > > Passing the property value from command line don't meet my condition, > > > because the new value has to be stored in the POM. > > > > > > I found out that a new mojo called "set-property" was implemented in > the > > > current master branch of versions maven plugin. This mojo would meet my > > > use cases. > > > > > > Does it exist a target date for the next release of version maven > plugin? > > > > > > Best regards, > > > > > > Sandra > > > > > > > > > Am 22.08.2017 um 11:07 schrieb Anders Hammar: > > >> Specifying property values from command line when doing a release > could be > > >> bad practice, as the pom deployed would not contain the value from > command > > >> line. It all depends on what the property is used for. > > >> > > >> /Anders > > >> > > >> On Tue, Aug 22, 2017 at 10:34 AM, John Patrick < > nhoj.patr...@gmail.com> > > >> wrote: > > >> > > >>> I think I do similar and I simply use > > >>> -DpropertyName=newValueForProperty on the command line when > executing > > >>> the maven command, or via a profile and then activate the required > > >>> profile. > > >>> > > >>> Just checking the property is already defined in a pom e.g. > > >>> ..oldValueForProperty > >>> propertyName> > > >>> > > >>> At build time I would simply change the command line I'm using to > > >>> build. I do this type of thing all the line when testing new > > >>> dependencies, different external systems, loading different > > >>> properties/config via a different dependency. > > >>> > > >>> John > > >>> > > >>> > > >>> On 21 August 2017 at 08:50, wrote: > > Hello mailing, > > > > I use property values, defined in a POM, during resource filtering. > I'd > > >>> like to change this properties during my release process. I know > that the > > >>> Maven Version Plugin has a goal named update-properties. But it > requires > > >>> that the properties are used in the dependency definition. I search > for > > >>> something like 'set-property -Dname=propertyName > > >>> -Dvalue=newValueForProperty'. Do you know a Maven Plugin that > supports this > > >>> use case? > > > > Thank you and best regards, > > > > Sandra Parsick > > > > > - > > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > > For additional commands, e-mail: users-h...@maven.apache.org > > > > >>> > > >>> > - > > >>> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > > >>> For additional commands, e-mail: users-h...@maven.apache.org > > >>> > > >>> > > >> > > > > > > > - > > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > > For additional commands, e-mail: users-h...@maven.apache.org > > > > > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
Aw: Re: How to up date a property in a POM to a specific value
Thank you for the hint. I will repeat my question on the Mojohaus mailinglist. > Gesendet: Samstag, 26. August 2017 um 19:26 Uhr > Von: "John Patrick"> An: "Maven Users List" > Betreff: Re: How to up date a property in a POM to a specific value > > If your talking about the codehaus version plugin which is now hosted > at mojohaus, it's a different mailing list i think... > > http://www.mojohaus.org/versions-maven-plugin/mail-lists.html > > > > On 23 August 2017 at 21:07, Sandra Parsick wrote: > > Thanks for your answers. > > > > Passing the property value from command line don't meet my condition, > > because the new value has to be stored in the POM. > > > > I found out that a new mojo called "set-property" was implemented in the > > current master branch of versions maven plugin. This mojo would meet my > > use cases. > > > > Does it exist a target date for the next release of version maven plugin? > > > > Best regards, > > > > Sandra > > > > > > Am 22.08.2017 um 11:07 schrieb Anders Hammar: > >> Specifying property values from command line when doing a release could be > >> bad practice, as the pom deployed would not contain the value from command > >> line. It all depends on what the property is used for. > >> > >> /Anders > >> > >> On Tue, Aug 22, 2017 at 10:34 AM, John Patrick > >> wrote: > >> > >>> I think I do similar and I simply use > >>> -DpropertyName=newValueForProperty on the command line when executing > >>> the maven command, or via a profile and then activate the required > >>> profile. > >>> > >>> Just checking the property is already defined in a pom e.g. > >>> ..oldValueForProperty >>> propertyName> > >>> > >>> At build time I would simply change the command line I'm using to > >>> build. I do this type of thing all the line when testing new > >>> dependencies, different external systems, loading different > >>> properties/config via a different dependency. > >>> > >>> John > >>> > >>> > >>> On 21 August 2017 at 08:50, wrote: > Hello mailing, > > I use property values, defined in a POM, during resource filtering. I'd > >>> like to change this properties during my release process. I know that the > >>> Maven Version Plugin has a goal named update-properties. But it requires > >>> that the properties are used in the dependency definition. I search for > >>> something like 'set-property -Dname=propertyName > >>> -Dvalue=newValueForProperty'. Do you know a Maven Plugin that supports > >>> this > >>> use case? > > Thank you and best regards, > > Sandra Parsick > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > > >>> > >>> - > >>> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > >>> For additional commands, e-mail: users-h...@maven.apache.org > >>> > >>> > >> > > > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > > - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: How to up date a property in a POM to a specific value
If your talking about the codehaus version plugin which is now hosted at mojohaus, it's a different mailing list i think... http://www.mojohaus.org/versions-maven-plugin/mail-lists.html On 23 August 2017 at 21:07, Sandra Parsickwrote: > Thanks for your answers. > > Passing the property value from command line don't meet my condition, > because the new value has to be stored in the POM. > > I found out that a new mojo called "set-property" was implemented in the > current master branch of versions maven plugin. This mojo would meet my > use cases. > > Does it exist a target date for the next release of version maven plugin? > > Best regards, > > Sandra > > > Am 22.08.2017 um 11:07 schrieb Anders Hammar: >> Specifying property values from command line when doing a release could be >> bad practice, as the pom deployed would not contain the value from command >> line. It all depends on what the property is used for. >> >> /Anders >> >> On Tue, Aug 22, 2017 at 10:34 AM, John Patrick >> wrote: >> >>> I think I do similar and I simply use >>> -DpropertyName=newValueForProperty on the command line when executing >>> the maven command, or via a profile and then activate the required >>> profile. >>> >>> Just checking the property is already defined in a pom e.g. >>> ..oldValueForProperty>> propertyName> >>> >>> At build time I would simply change the command line I'm using to >>> build. I do this type of thing all the line when testing new >>> dependencies, different external systems, loading different >>> properties/config via a different dependency. >>> >>> John >>> >>> >>> On 21 August 2017 at 08:50, wrote: Hello mailing, I use property values, defined in a POM, during resource filtering. I'd >>> like to change this properties during my release process. I know that the >>> Maven Version Plugin has a goal named update-properties. But it requires >>> that the properties are used in the dependency definition. I search for >>> something like 'set-property -Dname=propertyName >>> -Dvalue=newValueForProperty'. Do you know a Maven Plugin that supports this >>> use case? Thank you and best regards, Sandra Parsick - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org >>> >>> - >>> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org >>> For additional commands, e-mail: users-h...@maven.apache.org >>> >>> >> > - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: How to up date a property in a POM to a specific value
Thanks for your answers. Passing the property value from command line don't meet my condition, because the new value has to be stored in the POM. I found out that a new mojo called "set-property" was implemented in the current master branch of versions maven plugin. This mojo would meet my use cases. Does it exist a target date for the next release of version maven plugin? Best regards, Sandra Am 22.08.2017 um 11:07 schrieb Anders Hammar: > Specifying property values from command line when doing a release could be > bad practice, as the pom deployed would not contain the value from command > line. It all depends on what the property is used for. > > /Anders > > On Tue, Aug 22, 2017 at 10:34 AM, John Patrick> wrote: > >> I think I do similar and I simply use >> -DpropertyName=newValueForProperty on the command line when executing >> the maven command, or via a profile and then activate the required >> profile. >> >> Just checking the property is already defined in a pom e.g. >> ..oldValueForProperty> propertyName> >> >> At build time I would simply change the command line I'm using to >> build. I do this type of thing all the line when testing new >> dependencies, different external systems, loading different >> properties/config via a different dependency. >> >> John >> >> >> On 21 August 2017 at 08:50, wrote: >>> Hello mailing, >>> >>> I use property values, defined in a POM, during resource filtering. I'd >> like to change this properties during my release process. I know that the >> Maven Version Plugin has a goal named update-properties. But it requires >> that the properties are used in the dependency definition. I search for >> something like 'set-property -Dname=propertyName >> -Dvalue=newValueForProperty'. Do you know a Maven Plugin that supports this >> use case? >>> >>> Thank you and best regards, >>> >>> Sandra Parsick >>> >>> - >>> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org >>> For additional commands, e-mail: users-h...@maven.apache.org >>> >> >> - >> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org >> For additional commands, e-mail: users-h...@maven.apache.org >> >> > signature.asc Description: OpenPGP digital signature
Re: How to up date a property in a POM to a specific value
Specifying property values from command line when doing a release could be bad practice, as the pom deployed would not contain the value from command line. It all depends on what the property is used for. /Anders On Tue, Aug 22, 2017 at 10:34 AM, John Patrickwrote: > I think I do similar and I simply use > -DpropertyName=newValueForProperty on the command line when executing > the maven command, or via a profile and then activate the required > profile. > > Just checking the property is already defined in a pom e.g. > ..oldValueForProperty propertyName> > > At build time I would simply change the command line I'm using to > build. I do this type of thing all the line when testing new > dependencies, different external systems, loading different > properties/config via a different dependency. > > John > > > On 21 August 2017 at 08:50, wrote: > > Hello mailing, > > > > I use property values, defined in a POM, during resource filtering. I'd > like to change this properties during my release process. I know that the > Maven Version Plugin has a goal named update-properties. But it requires > that the properties are used in the dependency definition. I search for > something like 'set-property -Dname=propertyName > -Dvalue=newValueForProperty'. Do you know a Maven Plugin that supports this > use case? > > > > Thank you and best regards, > > > > Sandra Parsick > > > > - > > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > > For additional commands, e-mail: users-h...@maven.apache.org > > > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
Re: How to up date a property in a POM to a specific value
I think I do similar and I simply use -DpropertyName=newValueForProperty on the command line when executing the maven command, or via a profile and then activate the required profile. Just checking the property is already defined in a pom e.g. ..oldValueForProperty At build time I would simply change the command line I'm using to build. I do this type of thing all the line when testing new dependencies, different external systems, loading different properties/config via a different dependency. John On 21 August 2017 at 08:50,wrote: > Hello mailing, > > I use property values, defined in a POM, during resource filtering. I'd like > to change this properties during my release process. I know that the Maven > Version Plugin has a goal named update-properties. But it requires that the > properties are used in the dependency definition. I search for something like > 'set-property -Dname=propertyName -Dvalue=newValueForProperty'. Do you know a > Maven Plugin that supports this use case? > > Thank you and best regards, > > Sandra Parsick > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org