Re: Maven Release Plugin - Reopen MRELEASE-282

Hi, Reopened. PR are welcome. pt., 17 cze 2022 o 18:08 Pablo Caraballo Llorente napisał(a): > Hello. > > As a user of the maven-release-plugin, I find that the issue MRELEASE-282 > is an improvement > that > would be useful to improve the

Re: Maven Release Plugin 3.0.0-M6

Guys, let me know when you are done with all issues for M6, I will happily do the release for the community. M - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail:

Re: Maven Release Plugin 3.0.0-M6

MRELEASE-1087 is a massive cleanup in terms of quantity of code, but it's not really functional changes: just get rid of old Plexus APIs and associated tricks to make our life easier. I'm confident our ITs would catch issues at that level. on my own side, having feedback on

Re: Maven Release Plugin 3.0.0-M6

Nice it looks like the call for release suddenly generates a lot of activity for this plugin :) but how long will it take to get all those issues done? Because at the start it was just a bug fix release and now we have a lot of changes coming. Can we just cut a release and then look after all of

Re: Maven Release Plugin 3.0.0-M6

Hi, I would like to enhance the list with this one: https://issues.apache.org/jira/browse/MRELEASE-1079 Kind regards Karl Heinz Marbaise On 05.05.22 08:37, Hervé BOUTEMY wrote: https://issues.apache.org/jira/projects/MRELEASE/versions/12351336 3 issues to finish:

Re: Maven Release Plugin 3.0.0-M6

https://issues.apache.org/jira/projects/MRELEASE/versions/12351336 3 issues to finish: https://issues.apache.org/jira/browse/MRELEASE-955 https://issues.apache.org/jira/browse/MRELEASE-1084 https://issues.apache.org/jira/browse/MRELEASE-1087 Le mercredi 4 mai 2022, 14:51:21 CEST Samuel Le

Re: Maven Release Plugin 3.0.0-M6

Hello, any news on this? Without putting any pressure, I'd just like to be able to tell whether I should wait a few days or whether I should plan around having an M6. Thanks, SaM On Tue, Apr 26, 2022 at 2:36 PM Olivier Lamy wrote: > > Hi > It looks there is a plan for early (ish) next week > >

Re: Maven Release Plugin 3.0.0-M6

IIUC, the key aspect we need to solve to remove that milestone aspect is https://issues.apache.org/jira/browse/MRELEASE-955 (and relatives) if someone else knows other topics, please share, so we can focus Regards, Hervé Le mardi 26 avril 2022, 21:14:39 CEST Jeff Jensen a écrit : > M is for

Re: Maven Release Plugin 3.0.0-M6

Am 2022-04-26 um 21:14 schrieb Jeff Jensen: M is for Milestone, an incremental release towards the eventual final release considered early production ready but incomplete for full planned features and implementation. To the point!

Re: Maven Release Plugin 3.0.0-M6

M is for Milestone, an incremental release towards the eventual final release considered early production ready but incomplete for full planned features and implementation. On Tue, Apr 26, 2022 at 2:10 PM Gary Gregory wrote: > Can someone explain the M release meaning? Is it an alpha release?

Re: Maven Release Plugin 3.0.0-M6

Can someone explain the M release meaning? Is it an alpha release? A beta version? Is it production ready? Does it depend on the plugin (please say no)? Gary On Tue, Apr 26, 2022, 07:49 Samuel Le Berrigaud wrote: > Hello devs, > > I'd just like to get an idea of when a potential 3.0.0-M6 of

Re: Maven Release Plugin 3.0.0-M6

Hi It looks there is a plan for early (ish) next week cheers Olivier On Tue, 26 Apr 2022 at 9:48 pm, Samuel Le Berrigaud wrote: > Hello devs, > > I'd just like to get an idea of when a potential 3.0.0-M6 of the > maven-release-plugin might happen. > > I've managed to contribute a bug fix

Re: Maven release plugin

My current proposal: the start situation is a folder containing several checked out projects. the folder contains an aggregator pom, which is NOT under version control. release:prepare should start as normal, but it should end with a commit+tag+commit on every checked out folder.

Re: Maven release plugin

Hi Robert, i'll give it a try. Can you please summarize what needs to be done, or perhaps point me the right direction? 2017-11-20 21:32 GMT+02:00 Robert Scholte : > Hi Petar, > > would be great if you could pick this up. > There's enough work I want to finish first,

Re: Maven release plugin

Hi Petar, would be great if you could pick this up. There's enough work I want to finish first, maven-release-plugin is not one of them right now. thanks, Robert On Mon, 20 Nov 2017 18:38:56 +0100, Petar Tahchiev wrote: Hi Robert, any updates on the

Re: Maven release plugin

Hi Robert, any updates on the release-aggregator? Is there anything I can do to help? 2017-06-27 22:43 GMT+03:00 Robert Scholte : > Hi Petar, > > This is a clear sign that ${project} should not be used to resolve this. > Instead the pom should be analyzed again and if

Re: maven-release-plugin and signing artifacts

On Sat, 05 Aug 2017 22:05:22 +0200, Karl Heinz Marbaise wrote: Hi Robert, On 04/08/17 10:55, Robert Scholte wrote: Hi Karl Heinz, this can happen when the plugin configuration contains a fixed value for arguments, i.e -Dkey=value If you want arguments to be extended

Re: maven-release-plugin and signing artifacts

Hi Robert, On 04/08/17 10:55, Robert Scholte wrote: Hi Karl Heinz, this can happen when the plugin configuration contains a fixed value for arguments, i.e -Dkey=value If you want arguments to be extended via commandline argument, you need to do this: -Dkey=value ${arguments}

Re: maven-release-plugin and signing artifacts

Hi Karl Heinz, this can happen when the plugin configuration contains a fixed value for arguments, i.e -Dkey=value If you want arguments to be extended via commandline argument, you need to do this: -Dkey=value ${arguments} Robert On Thu, 03 Aug 2017 19:57:10 +0200, Karl Heinz

Re: Maven release plugin

Hi Petar, This is a clear sign that ${project} should not be used to resolve this. Instead the pom should be analyzed again and if there's a system property matching the parent, it should be replaced before loading the parent. That'll require quite some new lines of code :) The suggested

Re: Maven release plugin

Petar Tahchiev wrote: > Hey guys, > > my pull-request worked fine to not show the prompt to specify a version. > However, it fails to update snapshot dependency versions when you resolve > the parent to a concrete version. > Particularly in my case: > > > [BOM] >

Re: Maven release plugin

Hey guys, my pull-request worked fine to not show the prompt to specify a version. However, it fails to update snapshot dependency versions when you resolve the parent to a concrete version. Particularly in my case: [BOM] /\

Re: Maven release plugin

MRELEASE-362[1] is probably the matching issue. Be aware that some are talking about tagging every module. In most situations I don't like that. If the structure is hierarchical and the root is tagged, then all the modules are already tagged. All tags must be checked out during

Re: Maven release plugin

Yup. I don't think I understand the problem, and shouldn't comment. On Sat, Jun 24, 2017 at 4:59 PM, Petar Tahchiev wrote: > Hi Paul, > > I think you misunderstood. The [BOM] is a separate project and the > [PLATFORM] and [DEMO_STORE] are also separate projects, both of

Re: Maven release plugin

Hi Paul, I think you misunderstood. The [BOM] is a separate project and the [PLATFORM] and [DEMO_STORE] are also separate projects, both of which declare as their parent the [BOM]. @Robert: I have added the test-case: https://github.com/apache/maven-release/pull/18/commits/ Release-aggregator is

Re: Maven release plugin

What we're still missing is a release-aggregator, which can release multiple release-roots at once. That would probably be the preferred fix, the suggested patch is just an easy work-around. It is still on my todo-list. Robert On Sat, 24 Jun 2017 12:42:22 +0200, Paul Hammant

Re: Maven release plugin

Easy to fix. Have a profile 'platformOnly' in the root module (I'm not sure if 'BOM' should mean anything to me) that includes only 'platform' as a child module. mvn release:prepare -PplatformOnly # etc Later when you're ready to do the demo store release, use another (from root): mvn

Re: Maven release plugin

Hi Peter, This fix looks good to me, but I would appreciate one integration test to confirm it and to prevent regression in the future. thanks, Robert On Sat, 24 Jun 2017 08:58:58 +0200, Petar Tahchiev wrote: Hey guys, I'm facing a number of challenges when I

Re: Maven Release Plugin And A BOM

Yeah, I guess I feel the same and that's why I wanted to consult the dev list first before raising a JIRA. 2016-05-03 23:21 GMT+02:00 Jörg Schaible : > Hi Petar, > > Petar Tahchiev wrote: > > > Hi all, > > > > @Uwe - the enforcer rules are great, but I don't think I need

Re: Maven Release Plugin And A BOM

Hi Petar, Petar Tahchiev wrote: > Hi all, > > @Uwe - the enforcer rules are great, but I don't think I need them. > @Jorg - Resolving the parent during release:prepare is fine. What I don't > like is that it also asks me to resolve the platform version. The point is, that Maven does not

Re: Maven Release Plugin And A BOM

Hi all, @Uwe - the enforcer rules are great, but I don't think I need them. @Jorg - Resolving the parent during release:prepare is fine. What I don't like is that it also asks me to resolve the platform version. I'll go with Robert's suggestion. 2016-05-03 19:51 GMT+03:00 Jörg Schaible

Re: Maven Release Plugin And A BOM

Petar Tahchiev wrote: > Hi guys, > > I have a question regarding the release plugin. In my project I have a BOM > in which I declare a property and a dependencyManagement section: > > com.mycompany > my-bom > 1.0-SNAPSHOT > > > 1.0-SNAPSHOT > > > > > com.mycompany >

Re: Maven Release Plugin And A BOM

Hi Petar, I found a very old enforcer rule at smartics and asked them to provide these as OS. They did it two weeks ago at github under Apache Software License. :-) Take a look at https://github.com/smartics/smartics-enforcer-rules -- barthel On May 3, 2016 4:25:55 PM Petar Tahchiev

Re: Maven Release Plugin And A BOM

Hi Robert, thank you for your comment. The idea behind the property was that I also give the BOM to my clients and they declare it as their parent. So now if they want to use a newer version of the platform, all they have to do is redeclare the property to be 1.2 or 1.5 or whatever they want.

RE: Maven Release Plugin And A BOM

Why bother with the custom property? Do this instead and the release plugin is happy: com.mycompany my-bom 1.0-SNAPSHOT com.mycompany platform ${project.version} -Original Message- From: Petar Tahchiev [mailto:paranoia...@gmail.com] Sent: Tuesday, May

Re: Maven Release Plugin with Git broken?

Hi Robert, Is this a mult module project ? Have you defined the scm connection only in the root module ? Are you trying to release from the root of ? Kind regards Karl Heinz Marbaise On 10/7/15 4:48 AM, Robert Patrick wrote: Hi, Sorry for the noise but it seems like the Maven Release

Re: Maven Release Plugin with Git broken?

Hi Robert, not a developer list question, better use the users list for that kind of questions. Indeed, like what Karl-Heinz says, I suspect you're trying to release from a submodule/subdirectory. Cheers 2015-10-07 9:23 GMT+02:00 Karl Heinz Marbaise : > Hi Robert, > > Is this

Re: maven-release-plugin: consolidating release:perform and release:stage

Concerning. @since, that's really easy then. I had another thought: while pushChanges does allow to defer pushing, you have to do an extra execution of e.g. git push; git push --tags. What about having a property pushChangesAfterDeploy in prepare and stage which would do this in the release

Re: maven-release-plugin: consolidating release:perform and release:stage

the annotation takes free text, then let's try a descrptive text: @since xxx in release:perform, yyy in release:stage Regards, Hervé Le mardi 24 mars 2015 21:15:20 Mirko Friedenhagen a écrit : Hello everybody, today I stumbled upon a difference between perform and stage: - while perform

Re: maven-release-plugin does not build cleanly - M2_HOME is missing

Hello, further inspection of the problem leads to a possible solution: - the shell script does retrieve M2_HOME, however, as it is not exported it is not available furtheron. - so a quick fix would be to export M2_HOME directly before invoking exec $JAVACMD ... - however this will not help with

Re: maven-release-plugin does not build cleanly - M2_HOME is missing

What I do not understand is, that https://builds.apache.org/view/All/job/maven-release/261/consoleFull is just running fine with Maven 3.0.5. Two wild guesses: - it is because we do not use a Jenkins freestyle job but a beloved by Stephen ;-) Maven job. - or maybe something changed with

Re: maven-release-plugin does not build cleanly - M2_HOME is missing

Hello there, I now have a workaround. I am setting: injectedMavenHome${maven.home}/injectedMavenHome in maven-release-manager/pom.xml and use this to set: releaseEnvironment.setMavenHome( new File( System.getProperty( injectedMavenHome ) ) ); in the testcase. Works fine from the command line.

Re: maven-release-plugin does not build cleanly - M2_HOME is missing

Hi Mirko, On 3/25/15 9:31 PM, Mirko Friedenhagen wrote: What I do not understand is, that https://builds.apache.org/view/All/job/maven-release/261/consoleFull is just running fine with Maven 3.0.5. Two wild guesses: - it is because we do not use a Jenkins freestyle job but a beloved by Stephen

Re: maven-release-plugin does not build cleanly - M2_HOME is missing

Unfortunately, we may not use Assume in this testcase because it is derived from PlexusTestcase and this one does fail on AssumptionViolated as well. As a dirty workaround we could just return when System.getenv(M2_HOME) is null. Regards Mirko -- http://illegalstateexception.blogspot.com/

Re: maven-release-plugin does not build cleanly - M2_HOME is missing

Am Wed, 25 Mar 2015 21:01:53 +0100 schrieb Mirko Friedenhagen mfriedenha...@gmail.com: - however this will not help with IDEs like Eclipse or Intellij which use their own code to invoke stuff. I guess it is better when you pass it as a system property: -Dmaven.home=${M2_HOME} that way you

Re: maven-release-plugin does not build cleanly - M2_HOME is missing

Hello Robert, I see maven-shared-invoker was just released by you. I will take a look at MSHARED-261, which at least has a suggestion for a fix. Regards Mirko -- Sent from my mobile On Mar 24, 2015 10:31 PM, Robert Scholte rfscho...@apache.org wrote: Hi Mirko, This confirms why Karl Heinz

Re: maven-release-plugin does not build cleanly - M2_HOME is missing

Hi Mirko, This confirms why Karl Heinz had issues with the Maven Invoker 2.2 (take 1) On Windows there's no issue, the mvn.bat/mvn.cmd always sets M2_HOME if it's not there. We could add an AssumeThat-clause in this test as well... thanks, Robert Op Tue, 24 Mar 2015 22:16:59 +0100 schreef

Re: Maven Release Plugin and Java 8 issue

Hi, please only use the Maven users mailing list for these kind of questions. The Maven Developers List is meant for development of Maven itself. thanks, Robert Op Fri, 29 Aug 2014 09:05:30 +0200 schreef Vijaysenthil Veeriah vijaysent...@gmail.com: Hi I apologize I'm kind of new to

Re: Maven-release-plugin and scm site publication: need help

Never mind, I found the shell script left behind by the last person who did this. I On Sun, Feb 23, 2014 at 7:38 AM, Benson Margulies bimargul...@gmail.com wrote: I've staged 2.5 of the maven-release component. However, the documentation staging process is failing. mvn -Preporting site

RE: Maven-release-plugin and scm site publication: need help

MGso in your instance why does'nt maven-scm-publish to ~/maven-sites ?? Date: Sun, 23 Feb 2014 09:52:12 -0500 Subject: Re: Maven-release-plugin and scm site publication: need help From: bimargul...@gmail.com To: dev@maven.apache.org Never mind, I found the shell script left behind

Re: Maven-release-plugin and scm site publication: need help

-publish to ~/maven-sites ?? Date: Sun, 23 Feb 2014 09:52:12 -0500 Subject: Re: Maven-release-plugin and scm site publication: need help From: bimargul...@gmail.com To: dev@maven.apache.org Never mind, I found the shell script left behind by the last person who did this. I On Sun, Feb 23

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

Hi Mark. Yes it is, just define them as dependencies of the maven-release-plugin in your parent (or otherwise) pom. -Chris On Mon, Dec 9, 2013 at 3:23 PM, Mark Derricutt m...@talios.com wrote: Ok - so this looks to be an issue introduced in Git 1.8.5, from

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

Ok - so this looks to be an issue introduced in Git 1.8.5, from https://raw.github.com/git/git/master/Documentation/RelNotes/1.8.5.txt * git status now omits the prefix to make its output a comment in a commit log editor, which is not necessary for human consumption. Scripts that parse the

Re: maven-release-plugin: Is it possible to participate in the release phases by adding in you own extensions?

On Sat, Aug 4, 2012 at 9:51 AM, Chris Graham chrisgw...@gmail.com wrote: On Fri, Aug 3, 2012 at 3:28 PM, Barrie Treloar baerr...@gmail.com wrote: On Fri, Aug 3, 2012 at 2:49 PM, Chris Graham chrisgw...@gmail.com wrote: Why make it so hard? Why cann't you filter the resources and/or package

Re: maven-release-plugin: Is it possible to participate in the release phases by adding in you own extensions?

On Fri, Aug 3, 2012 at 3:28 PM, Barrie Treloar baerr...@gmail.com wrote: On Fri, Aug 3, 2012 at 2:49 PM, Chris Graham chrisgw...@gmail.com wrote: Why make it so hard? Why cann't you filter the resources and/or package them via the assembly plugin. Remember that plugins still run during

Re: maven-release-plugin: Is it possible to participate in the release phases by adding in you own extensions?

Why make it so hard? Why cann't you filter the resources and/or package them via the assembly plugin. Remember that plugins still run during the release process, so why not use them? I don't see why you need extensions here (but then, I've just come back from my first loong lunch in ages!)

Re: maven-release-plugin: Is it possible to participate in the release phases by adding in you own extensions?

isn't http://maven.apache.org/plugins/maven-release-plugin/examples/run-goals- before-commit.html sufficient? Le vendredi 3 août 2012 13:11:24 Barrie Treloar a écrit : I'm almost after something like eclipse extensions here. My particular use case: Get

Re: maven-release-plugin: Is it possible to participate in the release phases by adding in you own extensions?

On Fri, Aug 3, 2012 at 2:49 PM, Chris Graham chrisgw...@gmail.com wrote: Why make it so hard? Why cann't you filter the resources and/or package them via the assembly plugin. Remember that plugins still run during the release process, so why not use them? Because these are not things you

Re: maven-release-plugin: Is it possible to participate in the release phases by adding in you own extensions?

On Fri, Aug 3, 2012 at 2:55 PM, Hervé BOUTEMY herve.bout...@free.fr wrote: isn't http://maven.apache.org/plugins/maven-release-plugin/examples/run-goals- before-commit.html sufficient? I think because the goal I want to run org.eclipse.tycho:tycho-versions-plugin:set-version will also

Re: maven release plugin introducing scm urls into modified poms

Am 20.02.2012 06:51 schrieb Chris Graham chrisgw...@gmail.com: Hi All. I have a multi module project that I have working perfectly. In tracking down a reported problem, I ran the release plugin with the -DpreparationGoals=help:effective-pom clean verify In it, I can see that it has added

Re: Maven release plugin not honoring -Darguments

Am 27.09.2011 14:48 schrieb David Blevins david.blev...@gmail.com: Is it a known issue that the release plugin does not honor the -Darguments? Specifically, I'm attempting to: mvn release:prepare -DdryRun=true -Darguments=-DskipTests=true -DfailIfNoTests=false Try: mvn release:prepare

Re: Maven release plugin not honoring -Darguments

This situation was discussed once before. The author of this pom, as I recall, had pretty strong feelings about it. You can work with it by making your own profile named apache_release that has the additional stuff you want, or by overriding the execution configuration in your pom to use your

Re: Maven release plugin not honoring -Darguments

An FYI on the escaping/quoting as that's come up twice and isn't the issue. public class Arguments { public static void main(String[] args) { for (String arg : args) { System.out.printf([%s], arg); } System.out.println();

Re: Maven release plugin not honoring -Darguments

On Tue, Sep 27, 2011 at 1:09 PM, David Blevins david.blev...@gmail.com wrote: Did some more digging and it seems the issue is in the apache-10 parent pom.   If you alter it like so, the arguments are passed as expected:    plugin      groupIdorg.apache.maven.plugins/groupId      

Re: maven-release-plugin: using git where do I see the tag used to build the release in the pom?

Hello, I erroneously opened the issue in the SCM plugin (https://jira.codehaus.org/browse/SCM-655), however it is an issue of MRELEASE probably. Would someone with the according rights move it to http://jira.codehaus.org/browse/MRELEASE, please? Best regards Mirko On Mon, Dec 19, 2011 at 22:56,

RE: maven-release-plugin: using git where do I see the tag used to build the release in the pom?

https://jira.codehaus.org/browse/MRELEASE-723 From: mfriedenha...@gmail.com Date: Tue, 20 Dec 2011 21:14:59 +0100 Subject: Re: maven-release-plugin: using git where do I see the tag used to build the release in the pom? To: dev@maven.apache.org Hello, I erroneously opened

Re: maven-release-plugin: using git where do I see the tag used to build the release in the pom?

As discussed on the user-list: On Fri, Dec 16, 2011 at 22:58, Mirko Friedenhagen mfriedenha...@gmail.com wrote: Hello, I know that with SVN the developerConnection and connection are updated to the real URL, that is when I invoke release:prepare with a URL

Re: maven-release-plugin: using git where do I see the tag used to build the release in the pom?

On 19 December 2011 10:45, Mirko Friedenhagen mfriedenha...@gmail.com wrote: As discussed on the user-list: On Fri, Dec 16, 2011 at 22:58, Mirko Friedenhagen mfriedenha...@gmail.com wrote: Hello, I know that with SVN the developerConnection and connection are updated

Re: maven-release-plugin: using git where do I see the tag used to build the release in the pom?

some scm providers have something implemented. for git it's : git rev-parse --verify HEAD for svn: svn info for hg: hg id more details on those providers in various Info command impls. 2011/12/19 Stephen Connolly stephen.alan.conno...@gmail.com: On 19 December 2011 10:45, Mirko Friedenhagen

Re: maven-release-plugin: using git where do I see the tag used to build the release in the pom?

Hm, this will be a hard one. I know detected, that the rewrite of the SCM section happens in the maven-release-plugin (org.apache.maven.shared.release.phase.RewritePomsForReleasePhase). Two problemes I encountered now: - The maven-scm-plugin does not seem to implement the equivalent of scm:info

Re: maven-release-plugin: using git where do I see the tag used to build the release in the pom?

Then it will have to be the tag name so... On 19 December 2011 21:28, Mirko Friedenhagen mfriedenha...@gmail.com wrote: Hm, this will be a hard one. I know detected, that the rewrite of the SCM section happens in the maven-release-plugin

Re: Maven release plugin not honoring -Darguments

IIRC you have to include your forked maven arguments in the release plugin configuration under arguments-DskipTests=true -DfailIfNoTests=false/arguments Perhaps someone else can say _why_ the m-r-p is set up so you can't set this on the command line? thanks david jencks On Sep 27, 2011, at

Re: Maven release plugin not honoring -Darguments

you can if you understand shell escaping. - Stephen --- Sent from my Android phone, so random spelling mistakes, random nonsense words and other nonsense are a direct result of using swype to type on the screen On 27 Sep 2011 17:58, David Jencks david_jen...@yahoo.com wrote: IIRC you have to

Re: Maven release plugin not honoring -Darguments

That's not it, the quoting was fine. Even with a single argument with no spaces to -Darguments it still does not work. Did some more digging and it seems the issue is in the apache-10 parent pom. If you alter it like so, the arguments are passed as expected: plugin

Re: maven-release-plugin release?

Hi Brett, Brett Porter wrote: On 17/09/2010, at 2:23 AM, Jörg Schaible wrote: Hi Baptiste, Baptiste MATHUS wrote: Well, from my understanding, this is not a regression. What Paul says in the end

Re: maven-release-plugin release?

I answered that since I opened the attached test project, and I didn't see any relativePath tag anywhere (though I might have missed it). Cheers 2010/9/17 Jörg Schaible joerg.schai...@gmx.de Hi Brett, Brett Porter wrote: On 17/09/2010, at 2:23 AM, Jörg Schaible wrote: Hi Baptiste,

Re: maven-release-plugin release?

Baptiste MATHUS wrote: I answered that since I opened the attached test project, and I didn't see any relativePath tag anywhere (though I might have missed it). The problem is that the author of comment #1 did not open a new issue for the release plugin but used instead this maven issue to

Re: maven-release-plugin release?

So... does someone want to open it? :) On 17/09/2010, at 1:07 AM, Jörg Schaible wrote: Baptiste MATHUS wrote: I answered that since I opened the attached test project, and I didn't see any relativePath tag anywhere (though I might have missed it). The problem is that the author of

Re: maven-release-plugin release?

On 17/09/2010, at 1:07 AM, Jörg Schaible wrote: Baptiste MATHUS wrote: I answered that since I opened the attached test project, and I didn't see any relativePath tag anywhere (though I might have missed it). The problem is that the author of comment #1 did not open a new issue for

Re: maven-release-plugin release?

Brett Porter wrote: On 15/09/2010, at 2:26 PM, Mark Derricutt wrote: Hey guys, I was wondering what was happening with the new release of the maven-release-plugin? Things seemed to go quiet on that front this past week or so... I see that the SCM plugin got released tho, would be

Re: maven-release-plugin release?

Well, from my understanding, this is not a regression. What Paul says in the end http://jira.codehaus.org/browse/MNG-4687?focusedCommentId=235494page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#action_235494is not a workaround, but the right way to go. See also

Re: maven-release-plugin release?

Hi Baptiste, Baptiste MATHUS wrote: Well, from my understanding, this is not a regression. What Paul says in the end http://jira.codehaus.org/browse/MNG-4687?focusedCommentId=235494page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment- tabpanel#action_235494is not a workaround, but

Re: maven-release-plugin release?

On 17/09/2010, at 2:23 AM, Jörg Schaible wrote: Hi Baptiste, Baptiste MATHUS wrote: Well, from my understanding, this is not a regression. What Paul says in the end

Re: maven-release-plugin release?

On 15/09/2010, at 2:26 PM, Mark Derricutt wrote: Hey guys, I was wondering what was happening with the new release of the maven-release-plugin? Things seemed to go quiet on that front this past week or so... I see that the SCM plugin got released tho, would be good to get the release

Re: Maven Release Plugin Question

You may want to take a look at the enforcer plugin and the rules, many of the release criteria checks are already implemented as enforcer rules. If you build something that could consume the enforcer rule api, that would be pretty handy at least for the validation parts of the release process. On

RE: maven-release-plugin: useReleaseProfile - how does this work to add sources and javadocs?

The release profile is built into the superpom. http://svn.eu.apache.org/viewvc/maven/components/branches/maven-2.1.x/ma ven-project/src/main/resources/org/apache/maven/project/pom-4.0.0.xml?vi ew=markup -Original Message- From: Barrie Treloar [mailto:[EMAIL PROTECTED] Sent: Monday,

Re: maven-release-plugin: useReleaseProfile - how does this work to add sources and javadocs?

On Tue, Nov 11, 2008 at 1:23 PM, Brian E. Fox [EMAIL PROTECTED] wrote: The release profile is built into the superpom. http://svn.eu.apache.org/viewvc/maven/components/branches/maven-2.1.x/ma ven-project/src/main/resources/org/apache/maven/project/pom-4.0.0.xml?vi ew=markup Thanks. Now I

Re: maven-release-plugin svn branch command failed

The beta-8 was just released but I didn't notice this bug when I tried it. You can try the 2.0-beta-7 If it doesn't solve your problem you can try to change you're svn version like Borut proposes. If it solves it, you can open an issue ;-) On Tue, Nov 4, 2008 at 3:11 PM, Peter Nedonosko [EMAIL

Re: maven-release-plugin svn branch command failed

Hi, Thank you for fast feedback! 2008/11/4 Arnaud HERITIER [EMAIL PROTECTED] Hi Peter, which version of the release plugin are you using? We just released a new version, perhaps there's an issue in it ? I use 2.0-beta-8 version of the plugin. Which version do you release? If you

Re: maven-release-plugin svn branch command failed

Hi Peter, which version of the release plugin are you using? We just released a new version, perhaps there's an issue in it ? If you didn't change your version of the plugin it's probably an issue in svn because you are reproducing the issue with the svn command line. There are several

[Fwd: Re: maven-release-plugin not able to locate extensions]

Any comments??? Please 'cc' me in the response as I am not in this alias. Thanks, Sahoo ---BeginMessage--- Wendy Smoak wrote: On Wed, Oct 15, 2008 at 3:50 AM, Sahoo [EMAIL PROTECTED] wrote: As you can see, it uses a packaging type called distribution-fragment, which is understood by our

Re: Maven release plugin

Hi, ping again... 2008/9/25 Olivier Lamy [EMAIL PROTECTED] Oups (it looks my name here in the previous email :-) ). I can but first I'd like to release invoker plugin 1.3. Now that maven invoker plugin 1.3 is released (cf.

Re: Maven release plugin

Hi, I have a current vote pending for maven-resources-plugin. And there is 3 issues open for release [1]. IMHO we can move this to a next version. And for MRELEASE-3, perso I'd like to mark it as won't fix or move it to MNG (there is a workaround and IMHO it's not a release plugin issue). Others ?

Re: Maven release plugin

Oups (it looks my name here in the previous email :-) ). I can but first I'd like to release invoker plugin 1.3. -- Olivier 2008/9/24 Arnaud HERITIER [EMAIL PROTECTED]: Someone wants to take the lead ? there are 2 issues to fix in the roadmap Arnaud On Wed, Sep 24, 2008 at 6:36 PM, Zucchi

Re: Maven release plugin

On Wed, Sep 24, 2008 at 10:04 AM, Arnaud HERITIER [EMAIL PROTECTED] wrote: Someone wants to take the lead ? there are 2 issues to fix in the roadmap If they are not regressions, and no one is actively working on them, then let's push them out to the next version and get the work that's already

Re: Maven release plugin

Someone wants to take the lead ? there are 2 issues to fix in the roadmap Arnaud On Wed, Sep 24, 2008 at 6:36 PM, Zucchi Alessandro [EMAIL PROTECTED] wrote: Olivier Lamy said: Hi, Personnaly, I have planned to do it near end of September. I hope will be so. Bye Remy Sanlaville

Re: Maven Release Plugin - 2.0-beta-7 and MRELEASE-326

Any updates on this? hirowla wrote: Is anybody working on this but not updated in JIRA? This problem prevents any automated use of the plugin. Thanks, Ian Disclaimer: The information transmitted is intended only for the person or entity to which it is addressed and may

Re: Maven release plugin question

I tested the plugin without the requiresDependencyResolution parameter, and it was still able to find test scope snapshots. So I don't think it needs that to find snapshot versions. I looked into the issue a bit more, and I was wrong about the cause of the problem. Maven tricked me! The

RE: Maven release plugin question

Done. -Original Message- From: Paul Gier [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 23, 2007 3:54 PM To: Maven Developers List Cc: Brian E. Fox Subject: Re: Maven release plugin question I tested the plugin without the requiresDependencyResolution parameter, and it was still able

RE: Maven release plugin question

Maybe they want to check that no test dependencies are snapshots either? -Original Message- From: Paul Gier [mailto:[EMAIL PROTECTED] Sent: Monday, October 22, 2007 5:36 PM To: Maven Developers List Subject: Maven release plugin question Hi All, Does anyone know why the release plugin

  1   2   >