Aw: Maven Release Plugin

[Peter Rader]

Can you tell more about your SCM urls? Did you rewrote them to git instead of svn?
 
Kind regards

Peter Rader
--
Fachinformatiker AE / IT Software Developer
 
 

Gesendet: Donnerstag, 10. August 2023 um 20:16 Uhr
Von: "D Kern" <dillon...@gmail.com>
An: "Jenkins Developers" <jenkin...@googlegroups.com>
Betreff: Maven Release Plugin
I'm having issues with the maven release plugin after migrating from SVN to GIT. This seems to be a known issue ( https://jira.codehaus.org/browse/MRELEASE-812 , https://groups.google.com/g/jenkinsci-dev/c/qkmbl3HrYgk[https://groups.google.com/g/jenkinsci-dev/c/qkmbl3HrYgk] , https://stackoverflow.com/questions/15166781/mvn-releaseprepare-not-committing-changes-to-pom-xml?noredirect=1&lq=1#comment130269452_20657721[https://stackoverflow.com/questions/15166781/mvn-releaseprepare-not-committing-changes-to-pom-xml?noredirect=1&lq=1#comment130269452_20657721] , https://www.mail-archive.com/iss...@maven.apache.org/msg88067.html[https://www.mail-archive.com/iss...@maven.apache.org/msg88067.html] ). I have a multi module project and my pom for the release plugin configuration is below:

                    <groupId>org.apache.maven.plugins</groupId>
                    <artifactId>maven-release-plugin</artifactId>
                    <version>3.0.0-M1</version>
                    <dependencies>
                        <dependency>
                        <groupId>org.apache.maven.scm</groupId>
                        <artifactId>maven-scm-provider-gitexe</artifactId>
                        <version>1.13.0</version>
                        </dependency>
                        <dependency>
                        <groupId>org.apache.maven.scm</groupId>
                        <artifactId>maven-scm-api</artifactId>
                        <version>1.13.0</version>
                        </dependency>
                    </dependencies>
 
When I run release:prepare  release:perform, it checks out the project, then proceeds to tag the version with a -SNAPSHOT and deploys to my Nexus snapshot repo. It works fine on SVN. I’ve tried setting the language to English, I’ve used different versions of the SCM’s and release plugin. If I go to 3.0.1 of the release plugin, I do get API errors within my build. I have searched for a solution for a MULTI-MODULE project, and all versions variations do not seems to be working. I can get successful build each time, but again it just goes to the snapshot repo. Are there any alternative, or solutions for this issue?


Thank you
 
--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-de...@googlegroups.com[mailto:jenkinsci-de...@googlegroups.com].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/d4330475-3959-4551-a3e4-88a14237cf90n%40googlegroups.com[https://groups.google.com/d/msgid/jenkinsci-dev/d4330475-3959-4551-a3e4-88a14237cf90n%40googlegroups.com?utm_medium=email&utm_source=footer].

[Gavin Mogan]

This sounds like a thread for users mailing list or forums. Actually probably more of a maven question. All jenkins development is done on GitHub so no svn involved.

On Thu, Aug 10, 2023, 12:21 PM D Kern <dillon...@gmail.com> wrote:

Hello, yes I did, I've attached them. I did notice that once I create my branch through Jenkins, the HEAD tag turns into the name of the branch... Hopefully that's not an issue, and is expected.

To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/0c267e47-92b8-4ffa-ba28-3aa094a088d8n%40googlegroups.com.