Re: Strange behavior using maven build-cache extension in maven-release-plugin goals

d to deploy artifacts: Could not > transfer artifact temp.mectagcore:mectagcore:pom:1.0.0 from/to > maven-artifacts (https://xxx.jfrog.io/artifactory/maven-artifacts): status > code: 403, reason phrase: (403) > > If we disable the build-cache during release targets, we see

Strange behavior using maven build-cache extension in maven-release-plugin goals

usual release plugin configuration is:     org.apache.maven.plugins maven-release-plugin   3.0.0   *    -DskipEnforceSnapshots -DskipITs -DskipTests -DskipUTs     deploy * SemVerVersionPolicy GithubReleaseStrategy     @{prefix} Prepare release

ANN] Apache Maven Release Plugin 3.0.1 Released

The Apache Maven team is pleased to announce the release of the Apache Maven Release Plugin, version 3.0.1 https://maven.apache.org/maven-release/maven-release-plugin/ You should specify the version in your project's plugin configuration: org.apache.maven.plugins maven-release-plugin

Re: mismatch between maven-release-plugin site and available artifacts

ite and the available artifact. > > https://maven.apache.org/maven-release/maven-release-plugin/index.html > lists 3.0.0-M2 published 2020-04-07 as the current release, but it > cannot be downloaded from eg. > https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-release->

mismatch between maven-release-plugin site and available artifacts

There is a mismatch between the published site and the available artifact. https://maven.apache.org/maven-release/maven-release-plugin/index.html lists 3.0.0-M2 published 2020-04-07 as the current release, but it cannot be downloaded from eg. https://repo.maven.apache.org/maven2/org/apache

What is remoteTagging in maven-release-plugin?

Hello, I am having trouble understanding remoteTagging. I use Maven 3.5. 4, maven-release-plugin 3.0. 0-M1 and Subversion 1.8 to build multimodule projects. Sunbversion is a standard structure: trunk, branches, and tags. trunk/ ├ myProject/ │ ├ pom.xml (parent pom) │ ： ├ sub1

[ANN] Apache Maven Release Plugin 3.0.0-M1 Released

The Apache Maven team is pleased to announce the release of the Apache Maven Release Plugin, version 3.0.0-M1. This plugin is used to release a project with Maven, saving a lot of repetitive, manual work. Releasing a project is made in two steps: prepare and perform. https

[maven-release-plugin] Tagging & branching at the same commit

Hi list, I'm using the Maven Release Plugin together with Git for version control. I would like to achieve the following. When I create a release on master, say version 1.5.0, I would like to have both a tag and a new branch - starting at that tag. The branch would be there to release fix

Re: Maven Release Plugin Message Format

looks like there is WIP on that: https://issues.apache.org/jira/browse/MRELEASE-980 Help welcome (testing, providing feedback, ...) Regards, Hervé Le jeudi 31 octobre 2019, 02:31:47 CET Scott Rossillo a écrit : > We're using the maven-release-plugin and all our tags end up looking l

Re: Maven Release Plugin Message Format

don' t recall any commits like that, generally I see that the last commit in a tag is "[maven-release-plugin] prepare release <https://github.com/B3Partners/brmo/commit/bdcc63208bd4a8b521f3b82bd82d87148e9c2687> ..." and in my master branch I see "[maven-release-plugin] p

Maven Release Plugin Message Format

We're using the maven-release-plugin and all our tags end up looking like: vX.Y.Z copy for tag vX.Y.Z With git "copy for tag" is pretty nonsensical. Preferably, the message would be "Release X.Y.Z". I looked at the source code and see the actual tagging is delegate

Maven Release Plugin : SCM- Jazz

Hello, We use Maven release plugin with Jazz repository for automated release. While performing deliver operation below command is used. "scm deliver --repository-uri --username --password * --source --target --overwrite-uncommitted" Internally we have configured commit ru

Continuous Delivery / Continuous Deployment with the Maven Release Plugin

So I wrote a blog post on how we use the Maven Release Plugin with Jenkins to do Continuous Delivery and Continuous Deployment in the DevOptics team of CloudBees. If you are interested it's at: https://www.cloudbees.com/blog/apache-maven-continuous-deliverydeployment-devoptics-teams-approach

Re: [maven-release-plugin] Passing additional parameters

quot; already has quotes, so you need to escape the > those. > > thanks, > Robert > > > On Thu, 17 May 2018 23:20:59 +0200, Naveen Swamy <mnnav...@gmail.com> > wrote: > > Hello there, >> >> I have a question regarding maven release plugin. We use codehaus &

Re: [maven-release-plugin] Passing additional parameters

quotes, so you need to escape the those. thanks, Robert On Thu, 17 May 2018 23:20:59 +0200, Naveen Swamy <mnnav...@gmail.com> wrote: Hello there, I have a question regarding maven release plugin. We use codehaus native-plugin to build jni, I want to pass the cflags during rele

[maven-release-plugin] Passing additional parameters

Hello there, I have a question regarding maven release plugin. We use codehaus native-plugin to build jni, I want to pass the cflags during release phase. However I see that I am unable to pass any of the arguments through release plugin. Any experience or pointers would help this is mvn command

Re: maven release plugin

On 1 Mar 2018, at 23:18, Matthew Broadhead wrote: > Thanks Mark.  looks easy enough.  i may try a maven plugin first though as i > like the idea of maven controlling all the git pushes etc I tend to NOT let maven do the git pushes, for the cases we're doing releases on a hot fix, or a support

Re: maven release plugin

ster, develop, feature/* branches).  If so, we use the jgitflow-maven-plugin instead of maven-release-plugin, which handles these transitions and the inherent conflicts caused by the maven versioning. Unfortunately, the maintainer is no longer working on it (and says he's not even working in java

Re: maven release plugin

s quite sweetly. … and it is being actively maintained. Cheers, Steve C On 1 Mar 2018, at 12:56 am, Ben Tatham <bentat...@nanometrics.ca> wrote: Sounds like you're using gitflow (master, develop, feature/* branches). If so, we use the jgitflow-maven-plugin instead of maven-release

Re: maven release plugin

/* branches). If so, we use the jgitflow-maven-plugin instead of maven-release-plugin, which handles these transitions and the inherent conflicts caused by the maven versioning. Unfortunately, the maintainer is no longer working on it (and says he's not even working

Re: maven release plugin

cs.ca> wrote: > > Sounds like you're using gitflow (master, develop, feature/* branches). If > so, we use the jgitflow-maven-plugin instead of maven-release-plugin, which > handles these transitions and the inherent conflicts caused by the maven > versioning. > > Unfort

Re: maven release plugin

On 1 Mar 2018, at 2:56, Ben Tatham wrote: > Sounds like you're using gitflow (master, develop, feature/* branches). If > so, we use the jgitflow-maven-plugin instead of maven-release-plugin, which > handles these transitions and the inherent conflicts caused by the maven >

Re: maven release plugin

thanks Ben that looks just the job On 28/02/2018 14:56, Ben Tatham wrote: Sounds like you're using gitflow (master, develop, feature/* branches). If so, we use the jgitflow-maven-plugin instead of maven-release-plugin, which handles these transitions and the inherent conflicts caused

Re: maven release plugin

Sounds like you're using gitflow (master, develop, feature/* branches). If so, we use the jgitflow-maven-plugin instead of maven-release-plugin, which handles these transitions and the inherent conflicts caused by the maven versioning. Unfortunately, the maintainer is no longer working

maven release plugin

hi, not sure if this is the correct place to ask questions about the maven release plugin i am trying to set my snapshots and releases properly i am using git with a master branch and a development branch how do i work in the snapshot on development and then tag the releases to master? if you

Re: how to use both buildnumber-maven-plugin and maven-release-plugin

Doh! I misinterpreted the docs and was thinking that the flatten-maven-plugin was something only needed for multi-module projects… Thanks for clearing that up. Steve C > On 25 Oct 2017, at 7:46 pm, Karl Heinz Marbaise wrote: > > Hi, > > On 25/10/17 08:50, Stephen Coy

Re: how to use both buildnumber-maven-plugin and maven-release-plugin

Hi, On 25/10/17 08:50, Stephen Coy wrote: Hi Pascal, Unfortunately this method results in pom files being deployed with releases that do not have corresponding versions in them. In fact, the version is literally: ${revision} This results in build warnings for consumers of the

Re: how to use both buildnumber-maven-plugin and maven-release-plugin

Hi Pascal, Unfortunately this method results in pom files being deployed with releases that do not have corresponding versions in them. In fact, the version is literally: ${revision} This results in build warnings for consumers of the released artifact. Cheers, Steve C > On 24 Oct

RE: [EXTERNAL] Re: how to use both buildnumber-maven-plugin and maven-release-plugin

[EXTERNAL] Re: how to use both buildnumber-maven-plugin > and maven-release-plugin > > External Sender: Use caution with links/attachments. > > > > Hi, > > On 24/10/17 15:59, Justin Georgeson wrote: > > I want to enforce in every build (not just release builds)

Re: [EXTERNAL] Re: how to use both buildnumber-maven-plugin and maven-release-plugin

arguments="-Dmaven.buildNumber.doCheck=false"' but that just seems hacky, so I was curious if there's a better way. You know about the release:prepare goal what it is exactly doing ? http://maven.apache.org/maven-release/maven-release-plugin/examples/prepare-release.html Maybe I misunderstand your que

RE: [EXTERNAL] Re: how to use both buildnumber-maven-plugin and maven-release-plugin

aven Users List <users@maven.apache.org>; Justin Georgeson <justin.george...@halliburton.com> Subject: [EXTERNAL] Re: how to use both buildnumber-maven-plugin and maven-release-plugin External Sender: Use caution with links/attachments. Hi, the question is what the real problem is? C

Re: how to use both buildnumber-maven-plugin and maven-release-plugin

Hi, the question is what the real problem is? Can you have an example project which shows the problem? Or can you describe more in detail what exactly does not work or not work like you expect it.. Kind regards Karl Heinz Marbaise

Re: how to use both buildnumber-maven-plugin and maven-release-plugin

For me it's hard to understand the problem you are having, it might help to specify the exact errors you are getting. If you are willing to try something other than the release plugin, have a look at https://axelfontaine.com/blog/dead-burried.html Cheers, Pascal 2017-10-23 18:40 GMT+02:00

how to use both buildnumber-maven-plugin and maven-release-plugin

The 'clean verify' invoked by release:prepare fails in buildnumber-maven-plugin because pom.xml is modified. I can pass arguments to release:prepare have buildnumber-maven-plugin skip the check for modifications, but that check is one of the main motivations for using it in the first place.

Maven release plugin, branch goal behavior

Hi, I'm trying to use the release plugin (2.5.2 with maven 2.2.1) to perform a delivery. I did some tests using the release:perform goal. In the current branch, it - updates the pom with the release version, - commit the modification, - add a tag, - updates the pom to next snapshot, -

maven release plugin: help page is showing a deprecated version 2.5

Hi all, not sure to be on the good ML but I would like to ask to one of the maven-release-plugin leader/owner to update some help page about the plugin version to use. for example, this help page is up-to-date and refers to the latest plugin vrersion : 2.5.2 http://maven.apache.org/maven

Re: maven release plugin: help page is showing a deprecated version 2.5

Hi Brice, On 7/31/15 3:56 PM, Brice Vandeputte wrote: Hi all, not sure to be on the good ML but I would like to ask to one of the maven-release-plugin leader/owner to update some help page about the plugin version to use. It is very good to get in contact with us to show there is something

maven-release-plugin: syntax of connectionUrl with git?

-plugin:perform -DconnectionUrl=scm:svn:https://svn.mycompany.com/repos/path/to/myproject/tags/myproject-1.2.3 as outlined at http://maven.apache.org/maven-release/maven-release-plugin/examples/perform-release.html. But I did not find the correct syntax for GIT. In the end, I created

Re: maven-release-plugin: syntax of connectionUrl with git?

at http://maven.apache.org/maven-release/maven-release-plugin/examples/perform-release.html . But I did not find the correct syntax for GIT. In the end, I created a release.properties with the content scm.tag=myproject-1.2.3 and could run mvn release-plugin:perform -DconnectionUrl=scm:git:git

Re: maven-release-plugin: syntax of connectionUrl with git?

something like: mvn release-plugin:perform -DconnectionUrl=scm:svn: https://svn.mycompany.com/repos/path/to/myproject/tags/myproject-1.2.3 as outlined at http://maven.apache.org/maven-release/maven-release-plugin/examples/perform-release.html . But I did not find the correct

Issue with maven-release-plugin and maven 3.3.1

It appears as though the maven-release-plugin needs to be updated for Maven 3.3.1 (similar to the maven-invoker-plugin)? I get this error trying a dry run: [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-release-plugin:2.5.1:prepare (default-cli) on project parent: Failed

[ANN] Apache Maven Release Plugin 2.5.2 Released

The Apache Maven team is pleased to announce the release of the Apache Maven Release Plugin, version 2.5.2 This plugin is used to release a project with Maven, saving a lot of repetitive, manual work. Releasing a project is made in two steps: prepare and perform. http://maven.apache.org

Re: Issue with maven-release-plugin and maven 3.3.1

Hi, a short solution could be https://issues.apache.org/jira/browse/MRELEASE-902 after the new release of maven-release-plugin 2.5.2 is there you could change to the new release which contains a fix for that... Kind regards Karl Heinz Marbaise On 4/22/15 10:02 PM, cody.a.fy

RE: Issue with maven-release-plugin and maven 3.3.1

That works for me. Thanks! Cody Fyler Lending Grid Build Team G=Lending Grid Builds (515) – 441 - 0814 -Original Message- From: Karl Heinz Marbaise [mailto:khmarba...@gmx.de] Sent: Wednesday, April 22, 2015 3:11 PM To: Maven Users List Subject: Re: Issue with maven-release-plugin

AW: AW: maven-release-plugin / SVN credentials

the credentials from somewhere which is related to the Active Directory / Kerberos ticket. However this seems to fail if using the maven-release-plugin. However this may relate to https://jira.codehaus.org/browse/MRELEASE-892 as there is also an error message to use --force interactive to make

AW: maven-release-plugin / SVN credentials

Hi Robert, - I have looked at the Maven SCM project but do not get my problem solved or more hints on it - The maven-release-plugin is locked (with version 2.5, not 2.5.1) - If running maven with -X according to console no credentials are provided when accessing the SVN - If running maven

Re: maven-release-plugin / SVN credentials

Hi Sebastian, since your issue has to do with svn, one needs to look at the Maven SCM project.[1] That's what the maven-release-plugin is using to the commits, tags and checkouts. First ensure you've locked the version of the maven-release-plugin, preferably the lastest (i.e. 2.5.1

Re: AW: maven-release-plugin / SVN credentials

Hi Sebastian, this is first of all more an svn commandline issue rather than a Maven / maven-release-plugin issue. For that reason you should start by calling svn directly from the commandline. In the end, that's exactly what maven-release-plugin (actually the scm-svn-provider) does. Once

maven-release-plugin / SVN credentials

Hello, I have a problem with the maven-release-plugin using the SVN credentials (details below). I always get an SVN authorization error. It seems that the release plugin does not use the existing credentials. Unfortunately I'm even not sure whether it is a problem of the maven-release-plugin

Maven Release Plugin Unexpected Behaviour

Hello! I has already posted this question to StackOverflow, though I didn’t get much help (expect warning about git requirements for 2.5.x version). The thing is that I’m trying to set up our project deployment to Nexus process via release-plugin. My script is:  git checkout -b

Re: Maven Release Plugin Unexpected Behaviour

plugin artifactIdmaven-release-plugin/artifactId version2.5.1/version /plugin does the job as does mvn org.apache.maven.plugins:maven-release-plugin:2.5.1:prepare org.apache.maven.plugins:maven-release-plugin:2.5.1:perform On 23 October 2014 09:51, Vlad Slepukhin slp@gmail.com

Re: Maven release plugin fail during javadoc generation

Hi, the plugin causing this problem must be the maven-javadoc-plugin :) the release:perform isn't that magic, you can do the same steps by hand: - check out the code from tag (created by release:prepare) - go to target/checkout - execute mvn deploy site-deploy (site-deploy depends on the

Maven release plugin fail during javadoc generation

Hello all, I've a project since several years and I had not problem to build it. I recently installed JDK1.7 on my Windows 7 and now my build fail during mvn release:perform ! The build fail saying unmappable character for encoding utf-8. That's true as my source file are encoded in

RE: Maven Release Plugin - release:branch: branch versions not set as expected

Ok, thanks Robert. Sadly this doesn't fit my expectations or needs. I'll look to do something a little more manual. Mark -Original Message- From: Robert Scholte [mailto:rfscho...@apache.org] Sent: 29 August 2014 17:51 To: Maven Users List Subject: Re: Maven Release Plugin

Re: Maven Release Plugin - release:branch: branch versions not set as expected

On 1 Sep 2014, at 03:21, Mark Gibson mark.gib...@deltaonesolutions.com wrote: Ok, thanks Robert. Sadly this doesn't fit my expectations or needs. I'll look to do something a little more manual. Are you perhaps mixing up tagging and branching? What you describe sounds like what

Re: Maven Release Plugin and Java 8 issue

Hi, I guess you configured IntelliJ to compile with Java8 instead of instructing Maven to do so. Did you set the source and target in the configuration of the maven-compiler-plugin?[1] It's not the maven-release-plugin which is responsible for setting the java source and target. thanks

Maven Release Plugin and Java 8 issue

Hi I apologize I'm kind of new to maven and I cant figure out how get the Maven Release plugin to work for a Java 8 project. I'm using version 2.5 (The maven compiler version is 3.1) . When i just use the compiler plugin and do a compile it works in fact i can use most of the other plugins

Maven Release Plugin - release:branch: branch versions not set as expected

version 1.9.4.msysgit.1 Maven-release-plugin 2.5 Maven-scm-plugin 1.9.1

Re: Maven Release Plugin - release:branch: branch versions not set as expected

\jre Default locale: en_GB, platform encoding: Cp1252 OS name: windows 8, version: 6.2, arch: amd64, family: windows git --version git version 1.9.4.msysgit.1 Maven-release-plugin 2.5 Maven-scm-plugin 1.9.1 - To unsubscribe, e

maven-release-plugin: multi module project with multiple git repositories

Hi,   i wonder if it's possible to use the maven-release-plugin for a project where each child project is served by a different git repository:   root - pom.xml [stored in git1] child1 - pom.xml [stored in git2] child2 - pom.xml [stored in git3] I searched the web for hours because

Re: maven-release-plugin: multi module project with multiple git repositories

-release-plugin for a project where each child project is served by a different git repository: root - pom.xml [stored in git1] child1 - pom.xml [stored in git2] child2 - pom.xml [stored in git3] I searched the web for hours because there are some promising (?) comments in https

Maven release plugin having trouble with transformations?

This is very puzzling. For years I've used the maven-release-plugin to automate my releases with no trouble. Now, on a particular project on GitHub, it is incorrectly transforming my pom.xml and attempting to release the project as a snapshot. The project is drop-dead brainlessly simple

Re: Maven release plugin having trouble with transformations?

On Thu, May 29, 2014 at 7:52 PM, Laird Nelson ljnel...@gmail.com wrote: Now, on a particular project on GitHub, it is incorrectly transforming my pom.xml and attempting to release the project as a snapshot. Whittling this down a bit, it looks like the transformation works properly, because

Re: Maven release plugin having trouble with transformations?

On Thu, May 29, 2014 at 8:15 PM, Laird Nelson ljnel...@gmail.com wrote: It is as though the transformation is not being committed properly. Sure enough, I'm never seeing a git commit operation (with -X turned on). How can I get commits to start working again? Am I overlooking an option?

Re: Maven release plugin having trouble with transformations?

On Thu, May 29, 2014 at 8:48 PM, Laird Nelson ljnel...@gmail.com wrote: Sure enough, I'm never seeing a git commit operation (with -X turned on). How can I get commits to start working again? Am I overlooking an option? Upgrading the maven-release-plugin version to 2.5 caused commit

Re: maven release-plugin 2.5 bug - releasing snapshots...

to the company-repository, ready to be used by everyone. I will look into this - seem like a sensible way to go about things Thanks for the advice given by all cheers - good @ being sucked @ -- View this message in context: http://maven.40175.n5.nabble.com/maven-release-plugin-2-5-bug-releasing

maven release-plugin 2.5 bug - releasing snapshots...

v 2.2.2 successfully.By reverting back to v2.2.2 of org.apache.maven.plugins.maven.release-plugin this work perfectly http://maven.40175.n5.nabble.com/file/n5789837/release-version-prompt-v2.2.2.jpg Is this a known issue and is it linked to v2.5 of the maven release plugin ?I can do snapshot

Re: maven release-plugin 2.5 bug - releasing snapshots...

Weird, many users reported the 2.5 had fixed their issues. What (version) are you actually using for: * maven * maven-release-plugin (triple-check you hadn't redefined maven-scm-* dependency somewhere) * svn ? Git ? Something else ? On a unrelated subject : issuing a mvn clean install deploy

Re: maven release-plugin 2.5 bug - releasing snapshots...

I don't think this issue have been rectified. The maven release plugin I use (downloaded from maven central via my plugin) is as follows... This fail: plugin groupIdorg.apache.maven.plugins/groupId

Re: maven release-plugin 2.5 bug - releasing snapshots...

On 28 March 2014 11:12, ghostwolf59 martin.cederv...@commerce.wa.gov.auwrote: version2.2.2/version Then you are not using version 2.5

Re: maven release-plugin 2.5 bug - releasing snapshots...

.n5.nabble.com/maven-release-plugin-2-5-bug-releasing-snapshots-tp5789837p5789868.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional

Re: maven release-plugin 2.5 bug - releasing snapshots...

to overwrite this with anything that then takes me to the scm prompt and so on - which ultimately allow me to do what I really want. -- View this message in context: http://maven.40175.n5.nabble.com/maven-release-plugin-2-5-bug-releasing-snapshots-tp5789837p5789868.html Sent from the Maven - Users

Re: maven release-plugin 2.5 bug - releasing snapshots...

/release-version-prompt-v.2.4.1.jpg http://maven.40175.n5.nabble.com/file/n5789892/release-version-prompt-v.2.4.jpg - good @ being sucked @ -- View this message in context: http://maven.40175.n5.nabble.com/maven-release-plugin-2-5-bug-releasing-snapshots-tp5789837p5789892.html Sent

Re: maven release-plugin 2.5 bug - releasing snapshots...

http://maven.40175.n5.nabble.com/file/n5789892/release-version-prompt-v.2.4.1.jpg http://maven.40175.n5.nabble.com/file/n5789892/release-version-prompt-v.2.4.jpg - good @ being sucked @ -- View this message in context: http://maven.40175.n5.nabble.com/maven-release

Re: maven release-plugin 2.5 bug - releasing snapshots...

@ -- View this message in context: http://maven.40175.n5.nabble.com/maven-release-plugin-2-5-bug-releasing-snapshots-tp5789837p5789916.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users

RE: maven release-plugin 2.5 bug - releasing snapshots...

: Stephen Connolly [mailto:stephen.alan.conno...@gmail.com] Sent: 28 March 2014 13:32 To: Maven Users List Subject: Re: maven release-plugin 2.5 bug - releasing snapshots... Let me rephrase. The release plugin is designed to make release versions. It is not designed to make -SNAPSHOT versions

Re: maven release-plugin 2.5 bug - releasing snapshots...

earlier versions of the maven-release-plugin allow for this when at the same time the same plugin prevent final releases to refer to -snapshot's ? Fair enough if a line has been drawn between snapshots and formal release, but the convenience factor seem get lost in the discussion. Exactly what

Re: maven release-plugin 2.5 bug - releasing snapshots...

(and both should be used for ongoing development so should be snapshots...) /James -Original Message- From: Stephen Connolly [mailto:stephen.alan.conno...@gmail.com] Sent: 28 March 2014 13:32 To: Maven Users List Subject: Re: maven release-plugin 2.5 bug - releasing snapshots

Re: maven release-plugin 2.5 bug - releasing snapshots...

non tagged release without the -SNAPSHOT tag I find it somewhat difficult to understand why earlier versions of the maven-release-plugin allow for this when at the same time the same plugin prevent final releases to refer to -snapshot's ? Fair enough if a line has been drawn between snapshots

Re: maven release-plugin 2.5 bug - releasing snapshots...

/maven-release-plugin-2-5-bug-releasing-snapshots-tp5789837p5789916.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail

Re: maven release-plugin 2.5 bug - releasing snapshots...

Let me join this thread, because that someone is me. As said by Stephen: the version handling prior to 2.4 contained several issues, so you were relying on a bug. Reminds me of this classic XKCD... :) https://xkcd.com/1172/ Wayne

Re: maven release-plugin 2.5 bug - releasing snapshots...

. I will look into this - seem like a sensible way to go about things Thanks for the advice given by all cheers - good @ being sucked @ -- View this message in context: http://maven.40175.n5.nabble.com/maven-release-plugin-2-5-bug-releasing-snapshots-tp5789837p5789950.html Sent from

Maven Release Plugin releases SNAPSHOT instead of STABLE version

Hi, We are suffering from SCM-740 [1]. Is there any chance to apply the attached patch? Thanks [1]: http://jira.codehaus.org/browse/SCM-740

Re: Maven Release Plugin throws Authentication Required error

Jenkins or any other automated system. Cheers Le 6 mars 2014 15:14, D Vijay vijayd1...@gmail.com a écrit : Dear All, I need help in configuring the Maven Release plugin. I am trying to configure the plugin in Jenkins job. I am getting authentication exception. For invoking maven release

Problems with dependencyManagement in maven-release-plugin

say we have a 'son' project com.example.test:A without other dependencies P version 1.0.0-SNAPSHOT POM specifies A version as ${project.version}, so it moves in synchronicity with P we want to use maven release plugin to prepare two local changes for its release. I use shell to illustrate

Re: Unable to use the maven-release-plugin to release

This is still an issue. Can someone please fix the maven-release-plugin to work with a decent version of git? Martijn On Sat, Dec 28, 2013 at 4:22 PM, Robert Scholte rfscho...@apache.orgwrote: Hi, it depends on the type of problem you're facing. as said before, these are probably the best

Re: Unable to use the maven-release-plugin to release

Dashorst martijn.dasho...@gmail.com wrote: This is still an issue. Can someone please fix the maven-release-plugin to work with a decent version of git? Martijn On Sat, Dec 28, 2013 at 4:22 PM, Robert Scholte rfscho...@apache.orgwrote: Hi, it depends on the type of problem you're facing

maven-release-plugin updates modules with wrong versioning

Hi all mates, in Apache Oltu we have a commons modules set[1] which I am trying to cut a release, but I am experiencing for the first time a strange issue: when installing all modules from /trunk, versions respect what it is specified in project.version field in the POM, but when releasing them,

Re: maven-release-plugin updates modules with wrong versioning

are you using git 1.8.5.x? On 3 February 2014 15:56, Simone Tripodi simonetrip...@apache.org wrote: Hi all mates, in Apache Oltu we have a commons modules set[1] which I am trying to cut a release, but I am experiencing for the first time a strange issue: when installing all modules from

Re: maven-release-plugin updates modules with wrong versioning

nevermind... wrong question that this is the answer for On 3 February 2014 15:57, Stephen Connolly stephen.alan.conno...@gmail.comwrote: are you using git 1.8.5.x? On 3 February 2014 15:56, Simone Tripodi simonetrip...@apache.org wrote: Hi all mates, in Apache Oltu we have a commons

Re: Unable to use the maven-release-plugin to release

the Maven Release Plugin DOES NOT USE IT. We should really have a new release of m-r-p that forces the use of current scm-providers cause I can see this problem only increasing as more people a) upgrade git or b) move to git and get pissed off with maven+git This work around works, but really

Re: Unable to use the maven-release-plugin to release

Hi, it depends on the type of problem you're facing. as said before, these are probably the best options: - try maven-release-plugin 2.4 - use an older version of GIT with English locale. For details see https://jira.codehaus.org/browse/MRELEASE-812 Robert Op Sat, 28 Dec 2013 15:34:26 +0100

Re: Unable to use the maven-release-plugin to release

modified files ( git 1.8.x finally drops the leading # from its output and broke the old scm provider. On 26 Dec 2013, at 1:28, Martijn Dashorst wrote: I have tried to revert to maven-release-plugin:2.3.2 (the 6.12.0 release was baked with this one), I have tried to apply apache-parent pom v13

Re: Unable to use the maven-release-plugin to release

get the new version that actually picks up modified files ( git 1.8.x finally drops the leading # from its output and broke the old scm provider. On 26 Dec 2013, at 1:28, Martijn Dashorst wrote: I have tried to revert to maven-release-plugin:2.3.2 (the 6.12.0 release was baked with this one

Re: Unable to use the maven-release-plugin to release

You're correct - 1.8.1 is not related to Git 1.8, however it is the latest release - and a fix that SUPPORTS Git 1.8 was actually released back in something like scm-provider 1.5 earlier in the year - only the Maven Release Plugin DOES NOT USE IT. We should really have a new release of m-r-p

Unable to use the maven-release-plugin to release

and have migrated all settings to my new box. I have tried to revert to maven-release-plugin:2.3.2 (the 6.12.0 release was baked with this one), I have tried to apply apache-parent pom v13, and both failed with the same result. I am currently at a loss... Does anyone have a solution? Thanks, Martijn

Re: Unable to use the maven-release-plugin to release

have 2 options: - try maven-release-plugin 2.4 - use an older version of GIT with English locale. For details see https://jira.codehaus.org/browse/MRELEASE-812 Robert Op Wed, 25 Dec 2013 13:28:26 +0100 schreef Martijn Dashorst martijn.dasho...@gmail.com: I'm currently in week 4 of trying

RE: Unable to use the maven-release-plugin to release

To: users@maven.apache.org Subject: Re: Unable to use the maven-release-plugin to release Date: Wed, 25 Dec 2013 13:46:43 +0100 From: rfscho...@apache.org Hi, MGGuten Tag the problem you're facing has to do with the version of the git-client. They've changed the output, which

Re: maven-release-plugin oddity - no git commit under mvn 3.1.1

There is a know issue with Git and release plugin 2.4.2 and something to do with SCM version bundled in Maven 3.1.1? (or maybe 3.1.x) Olivier may know more. On 9 December 2013 02:40, Mark Derricutt m...@talios.com wrote: Hey all, Just encountered a strange issue with the maven-release-plugin

Re: maven-release-plugin oddity - no git commit under mvn 3.1.1

I was speaking with Olivier on IRC earlier, so far I've managed to work around the issue by adding a dependency/ on the latest maven-scm-providers-gitexe inside my maven-release-plugin plugin/ block and that seems to have resolved the issue. Simply dropping back to 2.3.2 of the release plugin

  1   2   3   4   5   6   7   8   >