Re: 3.0 beta 2/3/4 roadmap was Re: Merging in our Aether and Guice changes to Maven 3.x
On Aug 7, 2010, at 1:44 AM, Brett Porter wrote: And doesn't that show that you could have done the same thing with Aether? :) Could happen with anything, it's only dependent on what people do. It is not an easily reversible step, and I want to ensure that anyone that wants to get an improvement into Maven doesn't have to navigate the different controls and infrastructure of another project. Unavoidable. We're not going to bring in everyone other dependency and any developer worth their salt can figure out how to pull in sources for dependent projects. Aether is all JIRA and Confluence it's not a big leap for anyone here. The barrier is not and never will be the infrastructure, it's people's time and willingness to contribute. I continue to disagree. Time/willingess is #1, but the pain of tracking two of everything takes away from the time and willingness one has. We've seen it too many times before. Then we can agree to disagree. It's not going to stop anyone who starts with doing and not talking and it's pretty much all avoided by spending 5 minutes talking to someone on IRC. It's not a big deal. I will always stand by the reasoning that good tooling is the only true solution to breaking down the barriers. Any contributor should be guided to do the right thing. I lived through the worst of it in Maven 2.0/Plexus/Modello/etc. and it drove me crazy. It's no different now. We still have Modello and now Guice which none of you have any control over. We are very fortunate to have Stuart working with us at Sonatype who is a committer but by your measure this is worse. Totally different infrastructure and no access. Guice is an improvement because it reduces our exposure. Guice itself is a fairly known quantity, so we may only have to deal with issues in the shim or the rare one in Guice, not having to maintain all of plexus. I went through exactly the same thing with the plexus-spring bridge in Archiva, and it made things much easier (and I hope we might consider using the guice bridge there too). I expect us to work at improving the Maven APIs to use Guice directly, but other than that the hard work has been done (thanks!). There's no reason for Maven to need to make significant enhancements to the underlying stuff in the future. Aether would be a completely different story. Any time an MNG issue could be filed that means I need to file an AETHER issue, I consider that a problem. Apart from the next few weeks, I think that'll be rare for the shim. It's probably 1/3rd of open MNG issues for Aether though. I think this is the nature of the old code, and Aether will be more like Guice. Aether and it will just fade into the background like anything else. Anyone can find an excuse not to do something. If there are 5 people contributing to Aether by the end of the year I'll be ecstatic. I don't think issue tracking systems are the barrier, it's just hard code to write. Moving on, it seems you've answered my technical concerns from a Maven3 PoV, so I'm not objecting to this landing on trunk as is. I'll repeat that I remain reluctant to see an important part of the project's scope heading out of its governance. I can't force it to happen, but I'd again strongly urge you to reconsider hosting the core part as a subproject here (and by all means bring Alin on board as the other main contributor to it so far). I would gladly help with that. Continue to use github and whatever else forked from that repo to work on improvements that aren't important to Maven with others. If in the future it starts to shape like something that is quite stable from Maven's point of view, and the scope outgrowing it, then graduate to a TLP, Eclipse, or wherever seems appropriate. I know the tone of this thread in parts hasn't been particularly helpful and maybe isn't conducive to wanting to do that. A lot of that is knee-jerk stuff that should die down moving forward as people get on with it. I could be wrong, but I still think that if you ran a poll of committers who have a stake in Maven3 development, you'd find a preference for hosting it here. If I'm right, I think that's worth taking into consideration. If it does not flourish outside of Apache, then I honestly won't have a preference. But I believe it will and just because some of you don't like it doesn't mean I should have to kill the experiment. One of the reasons I don't want it here is pure lack of involvement and I do not think that can all be dropped at my feet and what Sonatype has or hasn't done. If after six months it's all people from Maven contributing and no one else I will admit I thought wrong and happily push it back here. Hervé is already participating on the Aether dev list and I encourage others to do the same. Thanks, Brett -- Brett Porter br...@apache.org http://brettporter.wordpress.com/
[VOTE] Release Apache Maven 3.0-beta-2
Hi, We solved 28 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500version=16090 There are still a couple of issues left in JIRA: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=10500status=1 Staging repo: https://repository.apache.org/content/repositories/maven-069/ Staged source and binary distros: https://repository.apache.org/content/repositories/maven-069/org/apache/maven/apache-maven/3.0-beta-2/ Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 +1 from me Benjamin - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: guice memory usage was: (3.0 beta 2/3/4 roadmap was Re: Merging in our Aether and Guice changes to Maven 3.x)
On 07/08/2010, at 12:44 AM, Arnaud Héritier wrote: The advantage is to do what I did this morning in few minutes. I found a OOME on Aether/Guice branch (reported to benjamin but not in MNG because it's not yet integrated) and then I validated it wasn't here in current trunk. The problem is that I had to rebuild both of them hat users won't do. Without the beta2 release, each time you'll have to check if the problem reported comes from Guice/Aether or from changes done for now in beta2. It is more for you who'll work on it to easily ask a comparison. I ran this over one of my builds out of curiosity. Not sure if this is helpful, but maybe some datapoints. 3.0-benjamin = 73m / 252m 3.0-beta-1 = 63m / 159m 2.2.1 = 129m / 252m Then I checked just the following: 3.0-beta-2-SNAPSHOT + guice patch = 70m/218m 3.0-beta-2-SNAPSHOT = 74m/252m The numbers are quite consistent, so it looks like the problem might have been on trunk here, not the guice++ branch. Arnaud, is that also what you see with trunk? I quickly ran the first two with Yourkit and saw that in Benjamin's branch, the memory grows faster at a consistent rate, but is still released at the end. The retained memory is only the classrealms and JDK ZIP cache, which basically is the same for beta-1. So more usage, but not a leak. No OOME, but perhaps the project is not big enough to exhibit it. Nothing to particularly note on the garbage collection front. The non-heap memory looks to be identical. Basically the same results running with a clean repository to do more artifact operations. Scanning the allocations, there's quite deep trees of allocations for Guice the shim - but given the results for the other snapshots I'm not sure that's an issue itself. That's all I had time for, but I'll hold onto the snapshots in case they help. - Brett -- 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: 3.0 beta 2/3/4 roadmap was Re: Merging in our Aether and Guice changes to Maven 3.x
On Aug 7, 2010, at 1:44 AM, Brett Porter wrote: Unavoidable. We're not going to bring in everyone other dependency and any developer worth their salt can figure out how to pull in sources for dependent projects. Aether is all JIRA and Confluence it's not a big leap for anyone here. The barrier is not and never will be the infrastructure, it's people's time and willingness to contribute. I continue to disagree. Time/willingess is #1, but the pain of tracking two of everything takes away from the time and willingness one has. We've seen it too many times before. So I refute this with an act by Kristian today which was to sign the Sonatype CLA, sign up for the mailing list, asked for access to the wiki, already has access and has been working with Benjamin. You'll also notice he hasn't participated in this discussion at all he's just doing. So I completely disagree there is any real pain, just a general unwillingness to attempt anything different. So you can spend 15 minutes telling me how hard it is to get involved or spend 15 minutes getting involved like Kristian just did. Thanks, Brett -- 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 Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl - We know what we are, but know not what we may be. -- Shakespeare
Re: guice memory usage was: (3.0 beta 2/3/4 roadmap was Re: Merging in our Aether and Guice changes to Maven 3.x)
On Aug 7, 2010, at 7:26 AM, Brett Porter wrote: On 07/08/2010, at 12:44 AM, Arnaud Héritier wrote: The advantage is to do what I did this morning in few minutes. I found a OOME on Aether/Guice branch (reported to benjamin but not in MNG because it's not yet integrated) and then I validated it wasn't here in current trunk. The problem is that I had to rebuild both of them hat users won't do. Without the beta2 release, each time you'll have to check if the problem reported comes from Guice/Aether or from changes done for now in beta2. It is more for you who'll work on it to easily ask a comparison. I ran this over one of my builds out of curiosity. Not sure if this is helpful, but maybe some datapoints. 3.0-benjamin = 73m / 252m 3.0-beta-1 = 63m / 159m 2.2.1 = 129m / 252m Then I checked just the following: 3.0-beta-2-SNAPSHOT + guice patch = 70m/218m 3.0-beta-2-SNAPSHOT = 74m/252m The numbers are quite consistent, so it looks like the problem might have been on trunk here, not the guice++ branch. Arnaud, is that also what you see with trunk? I quickly ran the first two with Yourkit and saw that in Benjamin's branch, the memory grows faster at a consistent rate, but is still released at the end. The retained memory is only the classrealms and JDK ZIP cache, which basically is the same for beta-1. So more usage, but not a leak. No OOME, but perhaps the project is not big enough to exhibit it. Nothing to particularly note on the garbage collection front. The non-heap memory looks to be identical. Basically the same results running with a clean repository to do more artifact operations. Scanning the allocations, there's quite deep trees of allocations for Guice the shim - but given the results for the other snapshots I'm not sure that's an issue itself. Yes, we believe there are no GC or leakage issues with the Aether it is the dirty tree which is memory intensive and it's that structure we are trying to compact. The performance framework found the intense memory use instantly. It was reduced and now we're thinking of trying to use a graph structure for the dirty tree. We're not sure if this will work or not yet. That's all I had time for, but I'll hold onto the snapshots in case they help. - Brett -- 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 Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl - Three people can keep a secret provided two of them are dead. -- Unknown
Re: [VOTE] Release Apache Maven 3.0-beta-2
+1 On Aug 7, 2010, at 7:16 AM, Benjamin Bentmann wrote: Hi, We solved 28 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500version=16090 There are still a couple of issues left in JIRA: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=10500status=1 Staging repo: https://repository.apache.org/content/repositories/maven-069/ Staged source and binary distros: https://repository.apache.org/content/repositories/maven-069/org/apache/maven/apache-maven/3.0-beta-2/ Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 +1 from me Benjamin - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl - A party which is not afraid of letting culture, business, and welfare go to ruin completely can be omnipotent for a while. -- Jakob Burckhardt
Re: guice memory usage was: (3.0 beta 2/3/4 roadmap was Re: Merging in our Aether and Guice changes to Maven 3.x)
Results I had yesterday were : 3.0-benjamin (built yesterday) : 14M/2488M in 5:23.389s (It probably swapped a lot) 3.0-beta-2 (downloaded few minutes ago) : 9M/125M built in 23.723s 2.2.1 : 67M/136M built in 30s I only built one module : http://svn.exoplatform.org/projects/ecms/trunk/packaging/wcm/ear Its dependencies tree is horrible ! I used : MAVEN_OPTS = -Xshare:auto -Xms128M -Xmx4G -XX:MaxPermSize=256M (In theory Xmx = 1G but I increased it to 4G to fix the OOME) To build it and reproduce the issue you need this repo : http://repository.exoplatform.org/public/ (releases snapshots) I will try to open the debugger this WE if I find few minutes. On Aug 7, 2010, at 1:26 PM, Brett Porter wrote: On 07/08/2010, at 12:44 AM, Arnaud Héritier wrote: The advantage is to do what I did this morning in few minutes. I found a OOME on Aether/Guice branch (reported to benjamin but not in MNG because it's not yet integrated) and then I validated it wasn't here in current trunk. The problem is that I had to rebuild both of them hat users won't do. Without the beta2 release, each time you'll have to check if the problem reported comes from Guice/Aether or from changes done for now in beta2. It is more for you who'll work on it to easily ask a comparison. I ran this over one of my builds out of curiosity. Not sure if this is helpful, but maybe some datapoints. 3.0-benjamin = 73m / 252m 3.0-beta-1 = 63m / 159m 2.2.1 = 129m / 252m Then I checked just the following: 3.0-beta-2-SNAPSHOT + guice patch = 70m/218m 3.0-beta-2-SNAPSHOT = 74m/252m The numbers are quite consistent, so it looks like the problem might have been on trunk here, not the guice++ branch. Arnaud, is that also what you see with trunk? I quickly ran the first two with Yourkit and saw that in Benjamin's branch, the memory grows faster at a consistent rate, but is still released at the end. The retained memory is only the classrealms and JDK ZIP cache, which basically is the same for beta-1. So more usage, but not a leak. No OOME, but perhaps the project is not big enough to exhibit it. Nothing to particularly note on the garbage collection front. The non-heap memory looks to be identical. Basically the same results running with a clean repository to do more artifact operations. Scanning the allocations, there's quite deep trees of allocations for Guice the shim - but given the results for the other snapshots I'm not sure that's an issue itself. That's all I had time for, but I'll hold onto the snapshots in case they help. - Brett -- 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 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Apache Maven 3.0-beta-2
+1 (non-binding) Built and tried against all my current checked-out projects with no incidents. Christian On Aug 7, 2010, at 7:53 AM, Jason van Zyl wrote: +1 On Aug 7, 2010, at 7:16 AM, Benjamin Bentmann wrote: Hi, We solved 28 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500version=16090 There are still a couple of issues left in JIRA: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=10500status=1 Staging repo: https://repository.apache.org/content/repositories/maven-069/ Staged source and binary distros: https://repository.apache.org/content/repositories/maven-069/org/apache/maven/apache-maven/3.0-beta-2/ Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing- releases.html Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 +1 from me Benjamin - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl - A party which is not afraid of letting culture, business, and welfare go to ruin completely can be omnipotent for a while. -- Jakob Burckhardt - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Apache Maven 3.0-beta-2
+1 (Non-binding) Works good on my most important builds, within M2Eclipse as well as outside. On Sat, Aug 7, 2010 at 1:16 PM, Benjamin Bentmann benjamin.bentm...@udo.edu wrote: Hi, We solved 28 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500version=16090 There are still a couple of issues left in JIRA: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=10500status=1 Staging repo: https://repository.apache.org/content/repositories/maven-069/ Staged source and binary distros: https://repository.apache.org/content/repositories/maven-069/org/apache/maven/apache-maven/3.0-beta-2/ Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 +1 from me Benjamin - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Germanys national anthem is the most boring in the world - how telling! - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Apache Maven 3.0-beta-2
+1 (non-binding) Tested on all open-source Sonar projects (including projects based on Tycho). On Sat, Aug 7, 2010 at 17:43, Christian Edward Gruber christianedwardgru...@gmail.com wrote: +1 (non-binding) Built and tried against all my current checked-out projects with no incidents. Christian On Aug 7, 2010, at 7:53 AM, Jason van Zyl wrote: +1 On Aug 7, 2010, at 7:16 AM, Benjamin Bentmann wrote: Hi, We solved 28 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500version=16090 There are still a couple of issues left in JIRA: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=10500status=1 Staging repo: https://repository.apache.org/content/repositories/maven-069/ Staged source and binary distros: https://repository.apache.org/content/repositories/maven-069/org/apache/maven/apache-maven/3.0-beta-2/ Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 +1 from me Benjamin - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl - A party which is not afraid of letting culture, business, and welfare go to ruin completely can be omnipotent for a while. -- Jakob Burckhardt - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Best regards, Evgeny Mandrikov aka Godin http://godin.net.ru http://twitter.com/_godin_
Re: [VOTE] Release Apache Maven 3.0-beta-2
+1 from me. On Sat, Aug 7, 2010 at 10:07 AM, Evgeny Mandrikov mandri...@gmail.comwrote: +1 (non-binding) Tested on all open-source Sonar projects (including projects based on Tycho). On Sat, Aug 7, 2010 at 17:43, Christian Edward Gruber christianedwardgru...@gmail.com wrote: +1 (non-binding) Built and tried against all my current checked-out projects with no incidents. Christian On Aug 7, 2010, at 7:53 AM, Jason van Zyl wrote: +1 On Aug 7, 2010, at 7:16 AM, Benjamin Bentmann wrote: Hi, We solved 28 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500version=16090 There are still a couple of issues left in JIRA: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=10500status=1 Staging repo: https://repository.apache.org/content/repositories/maven-069/ Staged source and binary distros: https://repository.apache.org/content/repositories/maven-069/org/apache/maven/apache-maven/3.0-beta-2/ Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 +1 from me Benjamin - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl - A party which is not afraid of letting culture, business, and welfare go to ruin completely can be omnipotent for a while. -- Jakob Burckhardt - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Best regards, Evgeny Mandrikov aka Godin http://godin.net.ru http://twitter.com/_godin_
Re: [VOTE] Release Maven SCM 1.4 (Take 2)
Olivier Lamy wrote: Staging repo: https://repository.apache.org/content/repositories/maven-064/ Staging sites : Scm : http://maven.apache.org/scm-1.4 Scm Plugin : http://maven.apache.org/scm-1.4/maven-scm-plugin +1 The link Maven SCM Plugin in the Modules nav menu on the left of http://maven.apache.org/scm-1.4/index.html yields a 404. Not sure whether this is just a matter of configuration or a general Maven/Site issue. Benjamin - 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.4 (Take 2)
+1 Note that the aggregate site hasn't been staged: don't forget it in the release publish. Regards, Hervé Le jeudi 05 août 2010, Olivier Lamy a écrit : Hi, In preparation of the Release Plugin release, I'd like to release Maven Scm 1.4. Change since first try : fix for SCM-568 We solved 23 issues : http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10527version=16 128 Staging repo: https://repository.apache.org/content/repositories/maven-064/ Staging sites : Scm : http://maven.apache.org/scm-1.4 Scm Plugin : http://maven.apache.org/scm-1.4/maven-scm-plugin Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 Here my +1. Thanks, - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Maven Linkcheck Plugin version 1.0
+1 Hervé Le jeudi 05 août 2010, Dennis Lundberg a écrit : Hi, This is the first release of this plugin. There are no issues in JIRA. If you want to see it in action, it has been configured in a profile called linkcheck in the POM for the Maven site. Staging repo: https://repository.apache.org/content/repositories/maven-066/ Staging site: http://maven.apache.org/plugins/maven-linkcheck-plugin-1.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
Re: [VOTE] Release Apache Maven 3.0-beta-2
+1 Hervé Le samedi 07 août 2010, Benjamin Bentmann a écrit : Hi, We solved 28 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500version=16 090 There are still a couple of issues left in JIRA: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=10500st atus=1 Staging repo: https://repository.apache.org/content/repositories/maven-069/ Staged source and binary distros: https://repository.apache.org/content/repositories/maven-069/org/apache/mav en/apache-maven/3.0-beta-2/ Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 +1 from me Benjamin - 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 Apache Maven 3.0-beta-2
+1 2010/8/7 Benjamin Bentmann benjamin.bentm...@udo.edu: Hi, We solved 28 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500version=16090 There are still a couple of issues left in JIRA: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=10500status=1 Staging repo: https://repository.apache.org/content/repositories/maven-069/ Staged source and binary distros: https://repository.apache.org/content/repositories/maven-069/org/apache/maven/apache-maven/3.0-beta-2/ Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 +1 from me Benjamin - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Olivier http://twitter.com/olamy http://fr.linkedin.com/in/olamy http://www.viadeo.com/fr/profile/olivier.lamy7 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Maven Linkcheck Plugin version 1.0
+1 On Sat, Aug 7, 2010 at 11:42 AM, Hervé BOUTEMY herve.bout...@free.frwrote: +1 Hervé Le jeudi 05 août 2010, Dennis Lundberg a écrit : Hi, This is the first release of this plugin. There are no issues in JIRA. If you want to see it in action, it has been configured in a profile called linkcheck in the POM for the Maven site. Staging repo: https://repository.apache.org/content/repositories/maven-066/ Staging site: http://maven.apache.org/plugins/maven-linkcheck-plugin-1.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
Re: [VOTE] Release Apache Maven 3.0-beta-2
Hello, +1 (non-binding) Thanks for that great work... Kind regards Karl Heinz Marbaise -- SoftwareEntwicklung Beratung SchulungTel.: +49 (0) 2405 / 415 893 Dipl.Ing.(FH) Karl Heinz MarbaiseICQ#: 135949029 Hauptstrasse 177 USt.IdNr: DE191347579 52146 Würselen http://www.soebes.de - 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.4 (Take 2)
2010/8/7 Benjamin Bentmann benjamin.bentm...@udo.edu: Olivier Lamy wrote: Staging repo: https://repository.apache.org/content/repositories/maven-064/ Staging sites : Scm : http://maven.apache.org/scm-1.4 Scm Plugin : http://maven.apache.org/scm-1.4/maven-scm-plugin +1 The link Maven SCM Plugin in the Modules nav menu on the left of http://maven.apache.org/scm-1.4/index.html yields a 404. Not sure whether this is just a matter of configuration or a general Maven/Site issue. I have just discovered there is the same issue with the current released site : http://maven.apache.org/scm/. whereas it's here http://maven.apache.org/scm/maven-scm-plugin/. so I can add a .htaccess file in site under plugins folder. BTW sound weird. Benjamin - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Olivier http://twitter.com/olamy http://fr.linkedin.com/in/olamy http://www.viadeo.com/fr/profile/olivier.lamy7 - 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.4 (Take 2)
Thanks for review. I will 2010/8/7 Hervé BOUTEMY herve.bout...@free.fr: +1 Note that the aggregate site hasn't been staged: don't forget it in the release publish. Regards, Hervé Le jeudi 05 août 2010, Olivier Lamy a écrit : Hi, In preparation of the Release Plugin release, I'd like to release Maven Scm 1.4. Change since first try : fix for SCM-568 We solved 23 issues : http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10527version=16 128 Staging repo: https://repository.apache.org/content/repositories/maven-064/ Staging sites : Scm : http://maven.apache.org/scm-1.4 Scm Plugin : http://maven.apache.org/scm-1.4/maven-scm-plugin Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 Here my +1. Thanks, - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Olivier http://twitter.com/olamy http://fr.linkedin.com/in/olamy http://www.viadeo.com/fr/profile/olivier.lamy7 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
[VOTE] Release Maven Site Plugin 3.0-beta-1 for maven 3
Hi, In order to have a good companion to the coming Apache Maven 3.0-beta-2 release. I'd like to release Maven Site Plugin 3.0-beta-1 for maven 3. We solved 10 issues : http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11146version=15554 Staging repo: https://repository.apache.org/content/repositories/maven-070/ Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Notes : * this release has been build using the staged Apache Maven 3.0-beta-2 (so you must use the staged repository [1] ) * some informations can be found [2], specially how to configure your pom in order to be able to continue building site with both maven 2.x and maven 3. Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 +1 from me -- Olivier [1] https://repository.apache.org/content/repositories/maven-069/ [2] https://cwiki.apache.org/confluence/x/sokr - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Maven Site Plugin 3.0-beta-1 for maven 3
+1 Hervé Le samedi 07 août 2010, Olivier Lamy a écrit : Hi, In order to have a good companion to the coming Apache Maven 3.0-beta-2 release. I'd like to release Maven Site Plugin 3.0-beta-1 for maven 3. We solved 10 issues : http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11146version=15 554 Staging repo: https://repository.apache.org/content/repositories/maven-070/ Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Notes : * this release has been build using the staged Apache Maven 3.0-beta-2 (so you must use the staged repository [1] ) * some informations can be found [2], specially how to configure your pom in order to be able to continue building site with both maven 2.x and maven 3. Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 +1 from me 1 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Apache Maven 3.0-beta-2
+1 It doesn't seem to be any WORSE than beta-1. It still doesn't build CXF's distribution module, but I didn't report that with beta-1 yet so not really expected to be fixed. I haven't had the time to figure out if it's a Shade plugin issue or beta-1/2 issue. Dan On Saturday 07 August 2010 7:16:42 am Benjamin Bentmann wrote: Hi, We solved 28 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500version=16 090 There are still a couple of issues left in JIRA: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=10500st atus=1 Staging repo: https://repository.apache.org/content/repositories/maven-069/ Staged source and binary distros: https://repository.apache.org/content/repositories/maven-069/org/apache/mav en/apache-maven/3.0-beta-2/ Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 +1 from me Benjamin - 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 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Maven Site Plugin 3.0-beta-1 for maven 3
+1 (non binding) Nicolas 2010/8/7 Olivier Lamy ol...@apache.org Hi, In order to have a good companion to the coming Apache Maven 3.0-beta-2 release. I'd like to release Maven Site Plugin 3.0-beta-1 for maven 3. We solved 10 issues : http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11146version=15554 Staging repo: https://repository.apache.org/content/repositories/maven-070/ Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Notes : * this release has been build using the staged Apache Maven 3.0-beta-2 (so you must use the staged repository [1] ) * some informations can be found [2], specially how to configure your pom in order to be able to continue building site with both maven 2.x and maven 3. Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 +1 from me -- Olivier [1] https://repository.apache.org/content/repositories/maven-069/ [2] https://cwiki.apache.org/confluence/x/sokr - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
