Re: [VOTE] Release maven-shade-plugin 2.0 -- attempt 2
+1 2012/9/3 Benson Margulies bimargul...@gmail.com: We solved 4 issues: ** Bug * [MSHADE-103] - maven-shade-plugin does not resolve from user-defined repositories * [MSHADE-124] - Need better plan for getting dependency-reduced-pom.xml out of basedir * [MSHADE-130] - Mark mojo as threadSafe for parallel builds ** New Feature * [MSHADE-112] - New property to enable shading the java text inside the sources artifact (not just shading the java source file locations) There are still plenty more fish in this sea. Stating repo: https://repository.apache.org/content/repositories/maven-028/ https://repository.apache.org/content/repositories/maven-028/org/apache/maven/plugins/maven-shade-plugin/2.0/maven-shade-plugin-2.0-source-release.zip Staging site: http://maven.apache.org/plugins/maven-shade-plugin-2.0/ Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
[ANN] Maven EAR Plugin 2.8 Released
The Maven team is pleased to announce the release of the Maven EAR Plugin, version 2.8 The plugin generates a JavaEE Enterprise Archive (EAR) file. http://maven.apache.org/plugins/maven-ear-plugin/ You should specify the version in your project's plugin configuration: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-ear-plugin/artifactId version2.8/version /plugin Release Notes - Maven 2.x Ear Plugin - Version 2.8 ** Bug * [MEAR-147] - wrong DOCTPYE in jboss-app.xml for 4.2 * [MEAR-151] - Allow empty library-directory element in application.xml ** Improvement * [MEAR-141] - No way to configure generate env-entry elements in generated application.xml * [MEAR-145] - Add Maven version used to Created-By entry in manifest * [MEAR-146] - Expose parameter to not write library-directory element in application.xml ** New Feature * [MEAR-150] - Support new 'no-version-for-ejb' file name mapping ** Task * [MEAR-152] - use maven-plugin-tools' java 5 annotations Enjoy, -The Maven team - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release maven-shade-plugin 2.0 -- attempt 2
+1 LieGrue, strub - Original Message - From: Olivier Lamy ol...@apache.org To: Maven Developers List dev@maven.apache.org Cc: Sent: Tuesday, September 4, 2012 2:15 PM Subject: Re: [VOTE] Release maven-shade-plugin 2.0 -- attempt 2 +1 2012/9/3 Benson Margulies bimargul...@gmail.com: We solved 4 issues: ** Bug * [MSHADE-103] - maven-shade-plugin does not resolve from user-defined repositories * [MSHADE-124] - Need better plan for getting dependency-reduced-pom.xml out of basedir * [MSHADE-130] - Mark mojo as threadSafe for parallel builds ** New Feature * [MSHADE-112] - New property to enable shading the java text inside the sources artifact (not just shading the java source file locations) There are still plenty more fish in this sea. Stating repo: https://repository.apache.org/content/repositories/maven-028/ https://repository.apache.org/content/repositories/maven-028/org/apache/maven/plugins/maven-shade-plugin/2.0/maven-shade-plugin-2.0-source-release.zip Staging site: http://maven.apache.org/plugins/maven-shade-plugin-2.0/ Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://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-shade-plugin 2.0 -- attempt 2
+1 Dan On Sep 2, 2012, at 7:03 PM, Benson Margulies bimargul...@gmail.com wrote: We solved 4 issues: ** Bug * [MSHADE-103] - maven-shade-plugin does not resolve from user-defined repositories * [MSHADE-124] - Need better plan for getting dependency-reduced-pom.xml out of basedir * [MSHADE-130] - Mark mojo as threadSafe for parallel builds ** New Feature * [MSHADE-112] - New property to enable shading the java text inside the sources artifact (not just shading the java source file locations) There are still plenty more fish in this sea. Stating repo: https://repository.apache.org/content/repositories/maven-028/ https://repository.apache.org/content/repositories/maven-028/org/apache/maven/plugins/maven-shade-plugin/2.0/maven-shade-plugin-2.0-source-release.zip Staging site: http://maven.apache.org/plugins/maven-shade-plugin-2.0/ Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Daniel Kulp dk...@apache.org - http://dankulp.com/blog Talend Community Coder - http://coders.talend.com - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Git as the canonical SCM
How's Git doing at Apache these days? Anyone interested in pursuing putting Maven in Git as the canonical SCM? Thanks, Jason -- Jason van Zyl Founder CTO, Sonatype Founder, Apache Maven http://twitter.com/jvanzyl - To do two things at once is to do neither. -- Publilius Syrus, Roman slave, first century B.C.
Getting the maven-plugins-ITs-m* jobs back on track again...
Hi all I'd like to try to get the Jenkins jobs maven-plugins-ITs-m2 and maven-plugins-ITs-m3 back on track a gain, but I'm not sure how to. Perhaps we can crack it together. Here's a summary of the current problems: maven-plugins-ITs-m2 We only have one plugin failing here, Maven Repository Plugin. There are 2 ITs that fail: - BundleCreateIT - BundlePackIT Both of the claim [1] [2] that the currently building version of the plugin itself (maven-repository-plugin) is not available in any repository. I cannot reproduce this locally on either Widows 7 or Ubuntu. Also I cannot reproduce it in a local Jenkins instance running on Windows 7. Is there some weird setup in the ASF Jenkins instance that is causing these errors? maven-plugins-ITs-m3 There are 4 failing plugins here, Maven Compiler Plugin, Maven Javadoc Plugin, Maven Repository Plugin and Maven Remote Resources Plugin. Maven Repository Plugin has the same problem [3] [4] as the m2 build. Maven Compiler Plugin fails because it cannot use a Java 6 feature when built using Java 5. This is in an IT [5] for MCOMPILER-120. This builds fine for me locally on Windows 7. Can anyone confirm on other platforms? Is it not possible to exclude this IT if the build is running on Java 5 or earlier? Maven Javadoc Plugin fails [6] in one of the tests: testIsValidPackageList(org.apache.maven.plugin.javadoc.JavadocUtilTest): Connection reset I haven't examined this in detail. The problems in Maven Remote Resources Plugin looks similar to those in Maven Repository Plugin. With this plugin pretty much all of the ITs fail [7]. Any help on these would be much appreciated. [1] https://builds.apache.org/job/maven-plugins-ITs-m2/ws/maven-repository-plugin/target/surefire-reports/org.apache.maven.plugins.repository.it.BundleCreateIT.txt [2] https://builds.apache.org/job/maven-plugins-ITs-m2/ws/maven-repository-plugin/target/surefire-reports/org.apache.maven.plugins.repository.it.BundlePackIT.txt [3] https://builds.apache.org/job/maven-plugins-ITs-m3/ws/maven-repository-plugin/target/surefire-reports/org.apache.maven.plugins.repository.it.BundleCreateIT.txt [4] https://builds.apache.org/job/maven-plugins-ITs-m3/ws/maven-repository-plugin/target/surefire-reports/org.apache.maven.plugins.repository.it.BundlePackIT.txt [5] https://builds.apache.org/job/maven-plugins-ITs-m3/ws/maven-compiler-plugin/target/it/mcompiler-120/build.log [6] https://builds.apache.org/job/maven-plugins-ITs-m3/ws/maven-javadoc-plugin/target/surefire-reports/org.apache.maven.plugin.javadoc.JavadocUtilTest.txt [7] https://builds.apache.org/job/maven-plugins-ITs-m3/ws/maven-remote-resources-plugin/target/failsafe-reports/ -- Dennis Lundberg - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
RE: Git as the canonical SCM
-Original Message- From: Jason van Zyl Sent: Tuesday, September 04, 2012 15:55 How's Git doing at Apache these days? Anyone interested in pursuing putting Maven in Git as the canonical SCM? Comments from the peanut gallery: It would make it very nice to contribute back. Since I do not have a sandbox access I have thrown away fixes because there was no efficient way to track them until they were accepted as patches. (same problem in struts, commons, ...) We would be very happy here at PD Inc if that was done. -Jason Pyeron -- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- - - - Jason Pyeron PD Inc. http://www.pdinc.us - - Principal Consultant 10 West 24th Street #100- - +1 (443) 269-1555 x333Baltimore, Maryland 21218 - - - -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- This message is copyright PD Inc, subject to license 20080407P00. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Git as the canonical SCM
On 2012-09-04 21:55, Jason van Zyl wrote: How's Git doing at Apache these days? A pilot was started some time ago, with a few volunteering projects. I have heard anything about its progress in a while. I'll ask over @infra and report back here. Anyone interested in pursuing putting Maven in Git as the canonical SCM? Thanks, Jason -- Jason van Zyl Founder CTO, Sonatype Founder, Apache Maven http://twitter.com/jvanzyl - To do two things at once is to do neither. -- Publilius Syrus, Roman slave, first century B.C. -- Dennis Lundberg - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Git as the canonical SCM
The drools guys did a really nice move from Subversion a few years back. http://blog.athico.com/2010/12/drools-migrated-to-git.html One of the key things they did, was reorganize their poms and project structure. I'd be willing to help out. I think there could be a lot more to this move than just importing from subversion, but it depends on what you guys want to do. best wishes, Andrew On Sep 4, 2012, at 3:09 PM, Jason Pyeron jpye...@pdinc.us wrote: -Original Message- From: Jason van Zyl Sent: Tuesday, September 04, 2012 15:55 How's Git doing at Apache these days? Anyone interested in pursuing putting Maven in Git as the canonical SCM? Comments from the peanut gallery: It would make it very nice to contribute back. Since I do not have a sandbox access I have thrown away fixes because there was no efficient way to track them until they were accepted as patches. (same problem in struts, commons, ...) We would be very happy here at PD Inc if that was done. -Jason Pyeron -- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- - - - Jason Pyeron PD Inc. http://www.pdinc.us - - Principal Consultant 10 West 24th Street #100- - +1 (443) 269-1555 x333Baltimore, Maryland 21218 - - - -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- This message is copyright PD Inc, subject to license 20080407P00. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Git as the canonical SCM
2012/9/4 Andrew Waterman awate...@ecosur.mx: The drools guys did a really nice move from Subversion a few years back. http://blog.athico.com/2010/12/drools-migrated-to-git.html One of the key things they did, was reorganize their poms and project structure. I'd be willing to help out. I think there could be a lot more to this move than just importing from subversion, but it depends on what you guys want to do. Yup I agree. I use git on other oss projects (Apache: cloudstack and non Apache: jenkins ...) and git svn for some asf projects. Due to lack of support of sparse checkout in git, I (perso) don't want we have to create a git repo per plugin etc... IMHO That will be a pain to manage. best wishes, Andrew On Sep 4, 2012, at 3:09 PM, Jason Pyeron jpye...@pdinc.us wrote: -Original Message- From: Jason van Zyl Sent: Tuesday, September 04, 2012 15:55 How's Git doing at Apache these days? Anyone interested in pursuing putting Maven in Git as the canonical SCM? Comments from the peanut gallery: It would make it very nice to contribute back. Since I do not have a sandbox access I have thrown away fixes because there was no efficient way to track them until they were accepted as patches. (same problem in struts, commons, ...) We would be very happy here at PD Inc if that was done. -Jason Pyeron -- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- - - - Jason Pyeron PD Inc. http://www.pdinc.us - - Principal Consultant 10 West 24th Street #100- - +1 (443) 269-1555 x333Baltimore, Maryland 21218 - - - -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- This message is copyright PD Inc, subject to license 20080407P00. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Git as the canonical SCM
jenkins does it (1 plugin = 1 repo ) and I sincerely see no solution to avoid that. Each plugin or each lib has its own lifecycle and requires to have its own git repo to be clean That's why on jenkins we have the IRC bot to manage them But it is easier on github because they provide many APIs to do such remote management. On ASF side I don't think we'll have soon such tooling :( On the other hand the only annoying thing to do its the conversion itself and then to update projects (SCM ...). After that we could ask to sync them on github and we can easily provide some script to clone all repos from a given organisation. Unlike Jenkins we don't have a flow of repos creation really important on ASF side. My 2 cents. Arnaud On Tue, Sep 4, 2012 at 10:23 PM, Olivier Lamy ol...@apache.org wrote: 2012/9/4 Andrew Waterman awate...@ecosur.mx: The drools guys did a really nice move from Subversion a few years back. http://blog.athico.com/2010/12/drools-migrated-to-git.html One of the key things they did, was reorganize their poms and project structure. I'd be willing to help out. I think there could be a lot more to this move than just importing from subversion, but it depends on what you guys want to do. Yup I agree. I use git on other oss projects (Apache: cloudstack and non Apache: jenkins ...) and git svn for some asf projects. Due to lack of support of sparse checkout in git, I (perso) don't want we have to create a git repo per plugin etc... IMHO That will be a pain to manage. best wishes, Andrew On Sep 4, 2012, at 3:09 PM, Jason Pyeron jpye...@pdinc.us wrote: -Original Message- From: Jason van Zyl Sent: Tuesday, September 04, 2012 15:55 How's Git doing at Apache these days? Anyone interested in pursuing putting Maven in Git as the canonical SCM? Comments from the peanut gallery: It would make it very nice to contribute back. Since I do not have a sandbox access I have thrown away fixes because there was no efficient way to track them until they were accepted as patches. (same problem in struts, commons, ...) We would be very happy here at PD Inc if that was done. -Jason Pyeron -- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- - - - Jason Pyeron PD Inc. http://www.pdinc.us - - Principal Consultant 10 West 24th Street #100- - +1 (443) 269-1555 x333Baltimore, Maryland 21218 - - - -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- This message is copyright PD Inc, subject to license 20080407P00. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- - Arnaud Héritier 06-89-76-64-24 http://aheritier.net Mail/GTalk: aherit...@gmail.com Twitter/Skype : aheritier - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Git as the canonical SCM
On 2012-09-04 22:10, Dennis Lundberg wrote: On 2012-09-04 21:55, Jason van Zyl wrote: How's Git doing at Apache these days? A pilot was started some time ago, with a few volunteering projects. I have heard anything about its progress in a while. I'll ask over @infra and report back here. It seems that it's not yet ready [1] for prime time. [1] https://git-wip-us.apache.org/docs/switching-to-git.html Anyone interested in pursuing putting Maven in Git as the canonical SCM? Thanks, Jason -- Jason van Zyl Founder CTO, Sonatype Founder, Apache Maven http://twitter.com/jvanzyl - To do two things at once is to do neither. -- Publilius Syrus, Roman slave, first century B.C. -- Dennis Lundberg - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Git as the canonical SCM
And the Seam guys and a few others got pretty much stuck because the granularity level needs to be up front if you move to GIT. GIT is cool, but it is not as modular as SVN. git-submodules are still a farce and there is nothing else which allows modularisation. Don't get me wrong, I really like GIT (otherwise I would not have written the maven SCM provider for it) and it really fits pretty good for some kind of projects (we use it over at Apache DeltaSpike for example). But I think it would not be a good fit for Maven as it doesn't support modularity as well as SVN does. LieGrue, strub - Original Message - From: Andrew Waterman awate...@ecosur.mx To: Maven Developers List dev@maven.apache.org Cc: Sent: Tuesday, September 4, 2012 10:17 PM Subject: Re: Git as the canonical SCM T he drools guys did a really nice move from Subversion a few years back. http://blog.athico.com/2010/12/drools-migrated-to-git.html One of the key things they did, was reorganize their poms and project structure. I'd be willing to help out. I think there could be a lot more to this move than just importing from subversion, but it depends on what you guys want to do. best wishes, Andrew On Sep 4, 2012, at 3:09 PM, Jason Pyeron jpye...@pdinc.us wrote: -Original Message- From: Jason van Zyl Sent: Tuesday, September 04, 2012 15:55 How's Git doing at Apache these days? Anyone interested in pursuing putting Maven in Git as the canonical SCM? Comments from the peanut gallery: It would make it very nice to contribute back. Since I do not have a sandbox access I have thrown away fixes because there was no efficient way to track them until they were accepted as patches. (same problem in struts, commons, ...) We would be very happy here at PD Inc if that was done. -Jason Pyeron -- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- - - - Jason Pyeron PD Inc. http://www.pdinc.us - - Principal Consultant 10 West 24th Street #100 - - +1 (443) 269-1555 x333 Baltimore, Maryland 21218 - - - -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- This message is copyright PD Inc, subject to license 20080407P00. - 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: Getting the maven-plugins-ITs-m* jobs back on track again...
Op Tue, 04 Sep 2012 21:59:28 +0200 schreef Dennis Lundberg denn...@apache.org: Hi all I'd like to try to get the Jenkins jobs maven-plugins-ITs-m2 and maven-plugins-ITs-m3 back on track a gain, but I'm not sure how to. Perhaps we can crack it together. Here's a summary of the current problems: maven-plugins-ITs-m2 We only have one plugin failing here, Maven Repository Plugin. There are 2 ITs that fail: - BundleCreateIT - BundlePackIT Both of the claim [1] [2] that the currently building version of the plugin itself (maven-repository-plugin) is not available in any repository. I cannot reproduce this locally on either Widows 7 or Ubuntu. Also I cannot reproduce it in a local Jenkins instance running on Windows 7. Is there some weird setup in the ASF Jenkins instance that is causing these errors? maven-plugins-ITs-m3 There are 4 failing plugins here, Maven Compiler Plugin, Maven Javadoc Plugin, Maven Repository Plugin and Maven Remote Resources Plugin. Maven Repository Plugin has the same problem [3] [4] as the m2 build. Maven Compiler Plugin fails because it cannot use a Java 6 feature when built using Java 5. This is in an IT [5] for MCOMPILER-120. This builds fine for me locally on Windows 7. Can anyone confirm on other platforms? Is it not possible to exclude this IT if the build is running on Java 5 or earlier? The Plexus JavacCompiler confirms this, as this is the code responsible for constructing the arguments. I've adjusted the invoker.properties to run with java 1.6+ And I've added a verify script to confirm that the build fails for the right reason. Maven Javadoc Plugin fails [6] in one of the tests: testIsValidPackageList(org.apache.maven.plugin.javadoc.JavadocUtilTest): Connection reset I haven't examined this in detail. The problems in Maven Remote Resources Plugin looks similar to those in Maven Repository Plugin. With this plugin pretty much all of the ITs fail [7]. Any help on these would be much appreciated. [1] https://builds.apache.org/job/maven-plugins-ITs-m2/ws/maven-repository-plugin/target/surefire-reports/org.apache.maven.plugins.repository.it.BundleCreateIT.txt [2] https://builds.apache.org/job/maven-plugins-ITs-m2/ws/maven-repository-plugin/target/surefire-reports/org.apache.maven.plugins.repository.it.BundlePackIT.txt [3] https://builds.apache.org/job/maven-plugins-ITs-m3/ws/maven-repository-plugin/target/surefire-reports/org.apache.maven.plugins.repository.it.BundleCreateIT.txt [4] https://builds.apache.org/job/maven-plugins-ITs-m3/ws/maven-repository-plugin/target/surefire-reports/org.apache.maven.plugins.repository.it.BundlePackIT.txt [5] https://builds.apache.org/job/maven-plugins-ITs-m3/ws/maven-compiler-plugin/target/it/mcompiler-120/build.log [6] https://builds.apache.org/job/maven-plugins-ITs-m3/ws/maven-javadoc-plugin/target/surefire-reports/org.apache.maven.plugin.javadoc.JavadocUtilTest.txt [7] https://builds.apache.org/job/maven-plugins-ITs-m3/ws/maven-remote-resources-plugin/target/failsafe-reports/ - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Moving our distrib to svnpub
Back on this. I wonder about changing a bit the distrib directory tree ? The goal is to ease release. For voting period the candidate files can be committed to the correct tree here https://dist.apache.org/repos/dist/dev/ (instead of scp to people.a.o) Then once the vote has passed releasing is simple copy from https://dist.apache.org/repos/dist/dev/ to https://dist.apache.org/repos/dist/release (et voilà) For that we could use a per version model: http://www.eu.apache.org/dist/maven/maven-3/3.0.4 http://www.eu.apache.org/dist/maven/maven-2/2.2.1 http://www.eu.apache.org/dist/maven/ant-tasks/ WDYT ? Note: I have created the issue https://issues.apache.org/jira/browse/INFRA-5224 if you want to follow up. 2012/8/22 Hervé BOUTEMY herve.bout...@free.fr: IIUC, it's https, not http :) no objection here, just documentation to update [1] Regards, Hervé [1] http://maven.apache.org/developers/release/maven-core-release.html Le mercredi 22 août 2012 00:36:53 Olivier Lamy a écrit : Hi, Before the end of the year, all Apache projects must move their distrib to svnpub (instead of using scp to people.a.o) It's as simple as having content from http://www.us.apache.org/dist/maven/ available in http://dist.apache.org/repos/dist/release/maven/ This is for core distrib (maven 1,2.0,2.2.1,3 and ant task). No objections I do the stuff early next week ? - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Git as the canonical SCM
Mark, I disagree. Any group of modules that is released together can just have a git repo. What case do you have in mind where we'd need to fight with the git submodule madness? For others: if a project wants to move to git, the project must provide a delsacrificial victim/del volunteer to help with git infrastructure. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Git as the canonical SCM
just take as example that you like to checkout all maven core plugins in one go because you like to do some refactoring/checks/upgrade. That would require you to go into each plugin project and get the stuff from there. And where would you put the aggregator pom for CI and development builds? Same applies to all other projects which are kind of 'aggregator' like maven-core, shared, etc LieGrue, strub - Original Message - From: Benson Margulies bimargul...@gmail.com To: Maven Developers List dev@maven.apache.org; Mark Struberg strub...@yahoo.de Cc: Sent: Tuesday, September 4, 2012 11:18 PM Subject: Re: Git as the canonical SCM Mark, I disagree. Any group of modules that is released together can just have a git repo. What case do you have in mind where we'd need to fight with the git submodule madness? For others: if a project wants to move to git, the project must provide a delsacrificial victim/del volunteer to help with git infrastructure. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Git as the canonical SCM
On Tue, Sep 4, 2012 at 5:29 PM, Mark Struberg strub...@yahoo.de wrote: just take as example that you like to checkout all maven core plugins in one go because you like to do some refactoring/checks/upgrade. I see. So the fact that we have a single trunk in svn for all the plugins is the thing that isn't convenient in git. That would require you to go into each plugin project and get the stuff from there. And where would you put the aggregator pom for CI and development builds? Same applies to all other projects which are kind of 'aggregator' like maven-core, shared, etc LieGrue, strub - Original Message - From: Benson Margulies bimargul...@gmail.com To: Maven Developers List dev@maven.apache.org; Mark Struberg strub...@yahoo.de Cc: Sent: Tuesday, September 4, 2012 11:18 PM Subject: Re: Git as the canonical SCM Mark, I disagree. Any group of modules that is released together can just have a git repo. What case do you have in mind where we'd need to fight with the git submodule madness? For others: if a project wants to move to git, the project must provide a delsacrificial victim/del volunteer to help with git infrastructure. - 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: Git as the canonical SCM
it is possible to have them all in one git repo and still release separately, we do it in a toolchain repository in jetty and use maven release plugin for it as well so its not _required_ that you split it all up by choosing git jesse -- jesse mcconnell jesse.mcconn...@gmail.com On Tue, Sep 4, 2012 at 4:46 PM, Benson Margulies bimargul...@gmail.com wrote: On Tue, Sep 4, 2012 at 5:29 PM, Mark Struberg strub...@yahoo.de wrote: just take as example that you like to checkout all maven core plugins in one go because you like to do some refactoring/checks/upgrade. I see. So the fact that we have a single trunk in svn for all the plugins is the thing that isn't convenient in git. That would require you to go into each plugin project and get the stuff from there. And where would you put the aggregator pom for CI and development builds? Same applies to all other projects which are kind of 'aggregator' like maven-core, shared, etc LieGrue, strub - Original Message - From: Benson Margulies bimargul...@gmail.com To: Maven Developers List dev@maven.apache.org; Mark Struberg strub...@yahoo.de Cc: Sent: Tuesday, September 4, 2012 11:18 PM Subject: Re: Git as the canonical SCM Mark, I disagree. Any group of modules that is released together can just have a git repo. What case do you have in mind where we'd need to fight with the git submodule madness? For others: if a project wants to move to git, the project must provide a delsacrificial victim/del volunteer to help with git infrastructure. - 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: Git as the canonical SCM
On 4 September 2012 14:29, Mark Struberg strub...@yahoo.de wrote: just take as example that you like to checkout all maven core plugins in one go because you like to do some refactoring/checks/upgrade. That would require you to go into each plugin project and get the stuff from there. And where would you put the aggregator pom for CI and development builds? Same applies to all other projects which are kind of 'aggregator' like maven-core, shared, etc You might want to have a look at git subtree. While it's currently in contrib, it *is* distributed with Git (since 1.7.11). Having said that, nothing is stopping you from simply using a single Git repository. :-) - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Git as the canonical SCM
I have no desire to keep a copy of the entire repo locally. From what I can see, the current SVN is well managed and well understood. I see little value in changing, other than to pander to the current fad in scm. -Chris On Wed, Sep 5, 2012 at 5:55 AM, Jason van Zyl ja...@tesla.io wrote: How's Git doing at Apache these days? Anyone interested in pursuing putting Maven in Git as the canonical SCM? Thanks, Jason -- Jason van Zyl Founder CTO, Sonatype Founder, Apache Maven http://twitter.com/jvanzyl - To do two things at once is to do neither. -- Publilius Syrus, Roman slave, first century B.C.
