Re: svn commit: r1086889 - /maven/indexer/trunk/indexer-core/src/test/java/org/apache/maven/index/packer/NEXUS4149TransferFormatTest.java
Hi Tamas, Author: cstamas Date: Wed Mar 30 10:07:35 2011 New Revision: 1086889 URL: http://svn.apache.org/viewvc?rev=1086889view=rev Log: NEXUS-4152: added UT covering the same issue I think it would be more appropriate if those commits were mentioning the corresponding MINDEXER issue. Benjamin - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: svn commit: r1086889 - /maven/indexer/trunk/indexer-core/src/test/java/org/apache/maven/index/packer/NEXUS4149TransferFormatTest.java
Hi, completely agreed, but let me explain -- not that it matters: I had a lot of accumulated changes in my github fork of maven-indexer, and initially did not wanted to disturb other forks of my repository. Hence, I started pushing changes _without_ changing commit messages first -- thinking it would change history, hence screw other forks. I was distracted with ASF SVN mirroring pain (dcommiting multiple commits from EU, --no-rebase was not helping, there was a lot of interlaving changes for same file), but solved luckily: http://twitter.com/#!/cstamas/status/53021178750701568 And then I realized: git-svn _also modifies_ history, but it was late then :( I already started pushing (and had to recover few times until I found out the dnsmasq fix), since there was a LOT of commits to be dcommited back to ASF SVN. To at least make it better, I linked the MINDEXER jira issues to the SVN revisions, so at least we have the JIRA-SVN direction, but SVN commit logs does not point back. http://jira.codehaus.org/browse/MINDEXER-15 http://jira.codehaus.org/browse/MINDEXER-16 http://jira.codehaus.org/browse/MINDEXER-17 http://jira.codehaus.org/browse/MINDEXER-18 Thanks, ~t~ On Wed, Mar 30, 2011 at 12:20 PM, Benjamin Bentmann benjamin.bentm...@udo.edu wrote: I think it would be more appropriate if those commits were mentioning the corresponding MINDEXER issue. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Maven SCM 1.5
+1 Vincent 2011/3/28 Olivier Lamy ol...@apache.org: Hi, I'd like to release Apache Maven SCM 1.5. We solved 32 issues : http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10527version=16688 Staging repo: https://repository.apache.org/content/repositories/maven-051/ Staging sites : Scm : http://maven.apache.org/scm-1.5 Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 Thanks, -- Olivier Lamy http://twitter.com/olamy http://www.linkedin.com/in/olamy - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Maven ANT Tasks version 2.1.2
work here +1 Vincent 2011/3/28 Stephen Connolly stephen.alan.conno...@gmail.com: Hi, We solved N issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11533styleName=Htmlversion=16670 There are still a couple of issues left in JIRA: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=11533status=1 Staging repo: https://repository.apache.org/content/repositories/maven-052/ Staging site: (may still be syncing) http://maven.apache.org/ant-tasks-2.1.2/ Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 -Stephen - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Inject dependecies into the compileClasspath from a mojo at runtime
Hi, I'm trying to get our Eclipse RCP build plug-in for Maven 2 to work again. What our plug-in does for each Eclipse plug-in in our reactor build: It analyses the manifest file for dependencies and adds them at runtime to the POM dependencies. The dependencies have the system scope and point to the jar files of an eclipse target platform. Our plugin is bound to the initialize phase, so that the compiler plug-in has all dependencies in the compileClasspath. This used to work for a mvn clean package. We now want to run another plug-in before the compile. Something like mvn clean other:plugin package and with this call, it stops working, because the compileClasspath does not contain our injected dependencies anymore. With Maven 3 even the mvn clean package does not work. So my question is, what is the best way to augment the compileClasspath at runtime with a Maven 2 plug-in? Would be great, if it also worked with Maven 3, so that we can easily migrate to Maven 3 in the future. Any hints are appreciated. Thanks in advance, Henrik P.S.: I know, there is tycho to build Eclipse RCP applications with maven, but we are bound to Maven 2 and cannot use it. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Maven ANT Tasks version 2.1.2
+1 2011/3/29 Stephen Connolly stephen.alan.conno...@gmail.com: Hi, We solved N issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11533styleName=Htmlversion=16670 There are still a couple of issues left in JIRA: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=11533status=1 Staging repo: https://repository.apache.org/content/repositories/maven-052/ Staging site: (may still be syncing) http://maven.apache.org/ant-tasks-2.1.2/ Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 -Stephen - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Olivier Lamy http://twitter.com/olamy http://www.linkedin.com/in/olamy - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Maven ANT Tasks version 2.1.2
Here's my +1 just in case anyone was unsure ;-) On 28 March 2011 23:56, Stephen Connolly stephen.alan.conno...@gmail.com wrote: Hi, We solved N issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11533styleName=Htmlversion=16670 There are still a couple of issues left in JIRA: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=11533status=1 Staging repo: https://repository.apache.org/content/repositories/maven-052/ Staging site: (may still be syncing) http://maven.apache.org/ant-tasks-2.1.2/ Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 -Stephen - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
cobertura plugin
Dear Maven PMC, Is the maven-cobertura-plugin on Codehaus under the supervision and care of the Apache Maven PMC, or is it just the product of some folks who maintain it at codehaus? --benson - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: svn commit: r1086338 - /maven/plugins/trunk/maven-site-plugin/pom.xml
On 2011-03-30 03:46, Hervé BOUTEMY wrote: questions: - do we keep Doxia and Doxia Site Tools versions in sync? We have done so in the past, but Doxia was separated into two projects to be able to release and version them separately. - any objection to update to Java 5, see DOXIASITETOOLS-57? I would prefer to wait until the next version with that, as I imagine that it is a rather large operation. I'm hoping to start the release process soon, once the ITs are stabilized. Regards, Hervé Le lundi 28 mars 2011, Dennis Lundberg a écrit : On 2011-03-28 21:27, Lukas Theussl wrote: hmm, is there a special reason for this? I was under the impression that we were working on a point release before attacking a major new version. I'm not objecting, just wondering, if this is only for DOXIASITETOOLS-50? (note that we will also have to publish a new xsd just for that). Right, that was my impression as well, until I went through the solved issues in JIRA and found that we (or I) had already modified the schema [1] as well as added new features [2]. So I figured that we should reflect those changes in the version number. [1] http://jira.codehaus.org/browse/DOXIASITETOOLS-41 [2] http://jira.codehaus.org/browse/DOXIASITETOOLS-40 -Lukas denn...@apache.org wrote: Author: dennisl Date: Mon Mar 28 18:57:17 2011 New Revision: 1086338 URL: http://svn.apache.org/viewvc?rev=1086338view=rev Log: o The next version of Doxia Sitetools will be 1.2. Modified: maven/plugins/trunk/maven-site-plugin/pom.xml Modified: maven/plugins/trunk/maven-site-plugin/pom.xml URL: http://svn.apache.org/viewvc/maven/plugins/trunk/maven-site-plugin/pom.x ml?rev=1086338r1=1086337r2=1086338view=diff == --- maven/plugins/trunk/maven-site-plugin/pom.xml (original) +++ maven/plugins/trunk/maven-site-plugin/pom.xml Mon Mar 28 18:57:17 2011 @@ -178,7 +178,7 @@ under the License. properties doxiaVersion1.1.4/doxiaVersion -doxiaSitetoolsVersion1.1.5-SNAPSHOT/doxiaSitetoolsVersion +doxiaSitetoolsVersion1.2-SNAPSHOT/doxiaSitetoolsVersion mavenVersion2.2.0/mavenVersion wagonVersion1.0-beta-6/wagonVersion /properties - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Dennis Lundberg - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
RE: [VOTE] Release Maven SCM 1.5
+1 (non-binding) -Robert From: vsive...@apache.org Date: Wed, 30 Mar 2011 08:51:14 -0400 Subject: Re: [VOTE] Release Maven SCM 1.5 To: dev@maven.apache.org +1 Vincent 2011/3/28 Olivier Lamy ol...@apache.org: Hi, I'd like to release Apache Maven SCM 1.5. We solved 32 issues : http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10527version=16688 Staging repo: https://repository.apache.org/content/repositories/maven-051/ Staging sites : Scm : http://maven.apache.org/scm-1.5 Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 Thanks, -- Olivier Lamy http://twitter.com/olamy http://www.linkedin.com/in/olamy - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: cobertura plugin
maven-cobertura-plugin is at Mojo: http://mojo.codehaus.org/ see FAQ for more information: http://mojo.codehaus.org/faq.html Regards, Hervé Le mercredi 30 mars 2011, Benson Margulies a écrit : Dear Maven PMC, Is the maven-cobertura-plugin on Codehaus under the supervision and care of the Apache Maven PMC, or is it just the product of some folks who maintain it at codehaus? --benson - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: svn commit: r1086338 - /maven/plugins/trunk/maven-site-plugin/pom.xml
DOXIASITETOOLS-57 done, since the concern was only the delay it would add before releasing :) Regards, Hervé Le mercredi 30 mars 2011, Dennis Lundberg a écrit : On 2011-03-30 03:46, Hervé BOUTEMY wrote: questions: - do we keep Doxia and Doxia Site Tools versions in sync? We have done so in the past, but Doxia was separated into two projects to be able to release and version them separately. - any objection to update to Java 5, see DOXIASITETOOLS-57? I would prefer to wait until the next version with that, as I imagine that it is a rather large operation. I'm hoping to start the release process soon, once the ITs are stabilized. Regards, Hervé Le lundi 28 mars 2011, Dennis Lundberg a écrit : On 2011-03-28 21:27, Lukas Theussl wrote: hmm, is there a special reason for this? I was under the impression that we were working on a point release before attacking a major new version. I'm not objecting, just wondering, if this is only for DOXIASITETOOLS-50? (note that we will also have to publish a new xsd just for that). Right, that was my impression as well, until I went through the solved issues in JIRA and found that we (or I) had already modified the schema [1] as well as added new features [2]. So I figured that we should reflect those changes in the version number. [1] http://jira.codehaus.org/browse/DOXIASITETOOLS-41 [2] http://jira.codehaus.org/browse/DOXIASITETOOLS-40 -Lukas denn...@apache.org wrote: Author: dennisl Date: Mon Mar 28 18:57:17 2011 New Revision: 1086338 URL: http://svn.apache.org/viewvc?rev=1086338view=rev Log: o The next version of Doxia Sitetools will be 1.2. Modified: maven/plugins/trunk/maven-site-plugin/pom.xml Modified: maven/plugins/trunk/maven-site-plugin/pom.xml URL: http://svn.apache.org/viewvc/maven/plugins/trunk/maven-site-plugin/pom .x ml?rev=1086338r1=1086337r2=1086338view=diff == == == --- maven/plugins/trunk/maven-site-plugin/pom.xml (original) +++ maven/plugins/trunk/maven-site-plugin/pom.xml Mon Mar 28 18:57:17 2011 @@ -178,7 +178,7 @@ under the License. properties doxiaVersion1.1.4/doxiaVersion -doxiaSitetoolsVersion1.1.5-SNAPSHOT/doxiaSitetoolsVersion +doxiaSitetoolsVersion1.2-SNAPSHOT/doxiaSitetoolsVersion mavenVersion2.2.0/mavenVersion wagonVersion1.0-beta-6/wagonVersion /properties - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: svn commit: r1086889 - /maven/indexer/trunk/indexer-core/src/test/java/org/apache/maven/index/packer/NEXUS4149TransferFormatTest.java
Would it affect the git history if the svn logs were modified with the updated issue numbers now that it has already been pushed? On 30/03/2011, at 10:06 PM, Tamás Cservenák wrote: Hi, completely agreed, but let me explain -- not that it matters: I had a lot of accumulated changes in my github fork of maven-indexer, and initially did not wanted to disturb other forks of my repository. Hence, I started pushing changes _without_ changing commit messages first -- thinking it would change history, hence screw other forks. I was distracted with ASF SVN mirroring pain (dcommiting multiple commits from EU, --no-rebase was not helping, there was a lot of interlaving changes for same file), but solved luckily: http://twitter.com/#!/cstamas/status/53021178750701568 And then I realized: git-svn _also modifies_ history, but it was late then :( I already started pushing (and had to recover few times until I found out the dnsmasq fix), since there was a LOT of commits to be dcommited back to ASF SVN. To at least make it better, I linked the MINDEXER jira issues to the SVN revisions, so at least we have the JIRA-SVN direction, but SVN commit logs does not point back. http://jira.codehaus.org/browse/MINDEXER-15 http://jira.codehaus.org/browse/MINDEXER-16 http://jira.codehaus.org/browse/MINDEXER-17 http://jira.codehaus.org/browse/MINDEXER-18 Thanks, ~t~ On Wed, Mar 30, 2011 at 12:20 PM, Benjamin Bentmann benjamin.bentm...@udo.edu wrote: I think it would be more appropriate if those commits were mentioning the corresponding MINDEXER issue. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: cobertura plugin
Other people at Codehaus. There is some overlap, but I probably not for the last couple of years. On 31/03/2011, at 4:45 AM, Benson Margulies wrote: Dear Maven PMC, Is the maven-cobertura-plugin on Codehaus under the supervision and care of the Apache Maven PMC, or is it just the product of some folks who maintain it at codehaus? --benson - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
