Re: Re: Release a snapshot version
Moreover if you are using git and want just to do `git tag && mvn deploy` then you can have a look at https://github.com/jgitver/jgitver-maven-plugin to understand how jgitver maven core extension can compute your project version automatically without never modifying your pom.xml. If you want to avoid unnecessary commits coming from the update of the pom version then it is worth looking at it. When it is activated you can work like below: $ mvn validate ... myproject-1.0.0-SNAPSHOT $ git tag -m "june release" 1.0 $ mvn deploy ... myproject-1.0.0 <-- version computed from tag without any pom modfication $ git add . && git commit -m "new feature blabla" $ mvn validate ... myproject-1.0.1-SNAPSHOT <-- version automatically followed maven conventions again without any pom modfication $ git branch featureX $ mvn validate ... myproject-1.0.1-featureX-SNAPSHOT <-- avoids automatically version collision in branch still without any pom modfication This way you never have to pollute your git history with commits containing only pom version changes ; this also avoids a lot of merge problems because there is no more unnecessary pom modifications. - Matthieu Brouillard On Thu, Jun 28, 2018 at 6:23 AM Ravindranatha Panikar, Renjith < rr...@allstate.com> wrote: > Thanks Thomas, that did the job. > > regards, > > > -Original Message- > From: Thomas Broyer [mailto:t.bro...@gmail.com] > Sent: Thursday, June 28, 2018 1:47 AM > To: Maven Users List > Subject: [External] Re: Release a snapshot version > > It looks like you just want to deploy your snapshot to a repository; in > that case you'll want to simply "mvn deploy", without even using the > maven-release-plugin (for the reasons Karl Heinz gave) > > Le mer. 27 juin 2018 18:30, Ravindranatha Panikar, Renjith < > rr...@allstate.com> a écrit : > > > I am planning to use maven release plugin for automating the release > > of our application. > > There can be two types of releases. > > > >Normal Release: > > Current code should be > tagged. > > Pom.xml should get > > updated to 'next-version-SNAPSHOT'. > > Artifacts should be > > public to remote repository. > > > >SNAPSHOT Release: it can contain one or more hot fixes > > which we would like to release on an immediate basis. > > Tagging is not > > required here. > > Pom.xml should > > not be updated. > > Artifacts should > > be published to remote repository with name 'ProjectName- > > next-version-SNAPSHOT'.jar' > > > > I know maven-release-plugin can perform the 'Normal Release'. But is > > there any way I can handle the 'SNAPSHOT release'? > > > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org >
RE: Re: Release a snapshot version
Thanks Thomas, that did the job. regards, -Original Message- From: Thomas Broyer [mailto:t.bro...@gmail.com] Sent: Thursday, June 28, 2018 1:47 AM To: Maven Users List Subject: [External] Re: Release a snapshot version It looks like you just want to deploy your snapshot to a repository; in that case you'll want to simply "mvn deploy", without even using the maven-release-plugin (for the reasons Karl Heinz gave) Le mer. 27 juin 2018 18:30, Ravindranatha Panikar, Renjith < rr...@allstate.com> a écrit : > I am planning to use maven release plugin for automating the release > of our application. > There can be two types of releases. > >Normal Release: > Current code should be tagged. > Pom.xml should get > updated to 'next-version-SNAPSHOT'. > Artifacts should be > public to remote repository. > >SNAPSHOT Release: it can contain one or more hot fixes > which we would like to release on an immediate basis. > Tagging is not > required here. > Pom.xml should > not be updated. > Artifacts should > be published to remote repository with name 'ProjectName- > next-version-SNAPSHOT'.jar' > > I know maven-release-plugin can perform the 'Normal Release'. But is > there any way I can handle the 'SNAPSHOT release'? > - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Maven Project Info Reports Plugin 3.0.0 released
The Apache Maven team is pleased to announce the release of the Maven Project Info Reports Plugin version 3.0.0. https://maven.apache.org/plugins/maven-project-info-reports-plugin/ You should specify the version in your project's plugin configuration: org.apache.maven.plugins maven-project-info-reports-plugin 3.0.0 Release Notes - Maven Project Info Reports Plugin - Version 3.0.0 ** Bug * [MPIR-348] - Usage of HTTP in web site for git-scm.com resources cause redirects to HTTPS * [MPIR-349] - Bad modules links in 'index/modules' reports when 'distributionManagement.site.url' comes from settings.xml * [MPIR-359] - Generated links for Mercurial SCM are broken * [MPIR-362] - Dependency Management report doesn't exclude system scoped dependencies * [MPIR-365] - Failed tests on Java 9 due to error with keytool plugin "keytool: not found" * [MPIR-370] - Upgrade transitive BCEL to 6.2 to avoid org.apache.bcel.classfile.ClassFormatException ** Improvement * [MPIR-352] - Use protocol-agnostic URL for Gravatar * [MPIR-358] - Add GitHub for issue management * [MPIR-366] - Drop Maven 2 support ** Task * [MPIR-323] - Align Mojo class names, goals and output names * [MPIR-345] - Upgrade to Doxia 1.8 * [MPIR-346] - Upgrade to Doxia Sitetools 1.8.1 * [MPIR-347] - Upgrade to Java 6 * [MPIR-350] - Upgrade of plexus-interpolation to 1.24. * [MPIR-353] - Upgrade parent to version 30 * [MPIR-354] - Upgrade Maven Site Plugin to version 3.5.1 for ITs * [MPIR-355] - Upgrade dependencies which are code- and testsafe * [MPIR-356] - Deprecate not used methods in ProjectInfoReportUtils * [MPIR-367] - Remove Dependency Repository Locations from dependency report * [MPIR-368] - Upgrade to Java 7 * [MPIR-369] - Drop Commons Lang for System builtins * [MPIR-372] - Remove fields duplicating parent class members ** Dependency upgrade * [MPIR-361] - Upgrade parent to 31 * [MPIR-363] - Upgrade dependencies to latest versions Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Release a snapshot version
It looks like you just want to deploy your snapshot to a repository; in that case you'll want to simply "mvn deploy", without even using the maven-release-plugin (for the reasons Karl Heinz gave) Le mer. 27 juin 2018 18:30, Ravindranatha Panikar, Renjith < rr...@allstate.com> a écrit : > I am planning to use maven release plugin for automating the release of > our application. > There can be two types of releases. > >Normal Release: > Current code should be tagged. > Pom.xml should get updated to > 'next-version-SNAPSHOT'. > Artifacts should be public to > remote repository. > >SNAPSHOT Release: it can contain one or more hot fixes > which we would like to release on an immediate basis. > Tagging is not > required here. > Pom.xml should not > be updated. > Artifacts should be > published to remote repository with name 'ProjectName- > next-version-SNAPSHOT'.jar' > > I know maven-release-plugin can perform the 'Normal Release'. But is there > any way I can handle the 'SNAPSHOT release'? >
Re: Release a snapshot version
Hi, On 27/06/18 12:25, Ravindranatha Panikar, Renjith wrote: I am planning to use maven release plugin for automating the release of our application. There can be two types of releases. Normal Release: Current code should be tagged. Pom.xml should get updated to 'next-version-SNAPSHOT'. Artifacts should be public to remote repository. SNAPSHOT Release: it can contain one or more hot fixes which we would like to release on an immediate basis. Tagging is not required here. Pom.xml should not be updated. Artifacts should be published to remote repository with name 'ProjectName- next-version-SNAPSHOT'.jar' I know maven-release-plugin can perform the 'Normal Release'. But is there any way I can handle the 'SNAPSHOT release'? A SNAPSHOT and a release is a contradiction in itself..cause a SNAPSHOT versions is not a release cause it can change etc. whereas a release is immutable can not change... Maybe I misunderstand your question but based on this it makes no sense to me... Kind regards Karl Heinz Marbaise - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Release a snapshot version
I am planning to use maven release plugin for automating the release of our application. There can be two types of releases. Normal Release: Current code should be tagged. Pom.xml should get updated to 'next-version-SNAPSHOT'. Artifacts should be public to remote repository. SNAPSHOT Release: it can contain one or more hot fixes which we would like to release on an immediate basis. Tagging is not required here. Pom.xml should not be updated. Artifacts should be published to remote repository with name 'ProjectName- next-version-SNAPSHOT'.jar' I know maven-release-plugin can perform the 'Normal Release'. But is there any way I can handle the 'SNAPSHOT release'?
Re: where to specify pluginRepositories for a custom maven core extension
Hi Nicolas, If you want perhaps you can also contribute to https://github.com/jgitver/jgitver-maven-plugin which computes project version automatically for maven (there is also a gradle project). Concerning your question, I never had such a problem. My core extensions are downloaded from the repositories I push them to (in my case central). Regards, Matthieu Brouillard On Wed, Jun 27, 2018 at 10:59 AM Nicolas Brasey wrote: > Hi, > > I developed a maven core extension which controls the project version and > the distribution managment repository depending on the git branch before > the build starts. > > I specify the coordinates of my extension by providing a file which is > located in the project git repo, inside .mvn/extension.xml, as described > here: > > https://maven.apache.org/docs/3.3.1/release-notes.html > > My problem is that Maven is not able to download this artifacts from a > remote repository. I would like that it is getting fetched from my private > maven repo. > > So the question is, where can I specify my private repository which > contains this extension ? Ideally, it should be inside my git repo (in .mvn > directory) > > Thanks > Nicolas >
where to specify pluginRepositories for a custom maven core extension
Hi, I developed a maven core extension which controls the project version and the distribution managment repository depending on the git branch before the build starts. I specify the coordinates of my extension by providing a file which is located in the project git repo, inside .mvn/extension.xml, as described here: https://maven.apache.org/docs/3.3.1/release-notes.html My problem is that Maven is not able to download this artifacts from a remote repository. I would like that it is getting fetched from my private maven repo. So the question is, where can I specify my private repository which contains this extension ? Ideally, it should be inside my git repo (in .mvn directory) Thanks Nicolas
