Re: [VOTE] Release Maven Surefire Plugin version 2.7
On Wed, 15 Dec 2010 00:21:49 +0100 Kristian Rosenvold kristian.rosenv...@gmail.com wrote: +1 (none binding) Works fine on our project. Thanks! Highlights of the release: * Pluggable providers are now supported, as well as manual provider selection * 2.7 is significantly smaller and lighter than earlier 2.x versions (Only 30% of the download size) * A large chunk of the highest voted issues have been fixed. * Some performance optimizations for forkMode=always * Significant cleanup/simplification of the code-base We solved 22 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10541version=16691 There are still a couple of issues left in JIRA: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truemode=hidejqlQuery=project+%3D+SUREFIRE+AND+resolution+%3D+Unresolved+ORDER+BY+updated+DESC Staging repo: https://repository.apache.org/content/repositories/maven-023/ Staging site: (Sync pending) http://maven.apache.org/plugins/maven-surefire-plugin-2.7/ http://maven.apache.org/plugins/maven-failsafe-plugin-2.7/ http://maven.apache.org/plugins/maven-surefire-report-plugin-2.7/ http://maven.apache.org/surefire/staging/ Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 And here's my +1 Kristian - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Tony Chemit tél: +33 (0) 2 40 50 29 28 email: che...@codelutin.com http://www.codelutin.com - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
[VOTE] Release Maven Surefire Plugin version 2.7; regression
I seem to have run across at least one case where failsafe does not properly fail a build with test failures. I'm looking into the problem. Although I'm not cancelling the vote right now, you may consider postponing further testing until I have determined the exact circumstances. It smells like a no-go, unless it turns out to be some exotic corner case. Kristian on., 15.12.2010 kl. 09.01 +0100, skrev chemit: On Wed, 15 Dec 2010 00:21:49 +0100 Kristian Rosenvold kristian.rosenv...@gmail.com wrote: +1 (none binding) Works fine on our project. Thanks! Highlights of the release: * Pluggable providers are now supported, as well as manual provider selection * 2.7 is significantly smaller and lighter than earlier 2.x versions (Only 30% of the download size) * A large chunk of the highest voted issues have been fixed. * Some performance optimizations for forkMode=always * Significant cleanup/simplification of the code-base We solved 22 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10541version=16691 There are still a couple of issues left in JIRA: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truemode=hidejqlQuery=project+%3D+SUREFIRE+AND+resolution+%3D+Unresolved+ORDER+BY+updated+DESC Staging repo: https://repository.apache.org/content/repositories/maven-023/ Staging site: (Sync pending) http://maven.apache.org/plugins/maven-surefire-plugin-2.7/ http://maven.apache.org/plugins/maven-failsafe-plugin-2.7/ http://maven.apache.org/plugins/maven-surefire-report-plugin-2.7/ http://maven.apache.org/surefire/staging/ Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 And here's my +1 Kristian - 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
Regarding maven 3 integration with Hudson
Hi, I'm facing issues when using Maven 3 with latest build of Hudson. The maven plugin doesn't seem to be compatible with Maven 3. It throws errors as, C:\hudson1\home\plugins\maven-plugin\WEB-INF\lib\maven-interceptor-1.389.jar 52039 Exception in thread main java.lang.NoSuchMethodError: org.codehaus.classworlds.Launcher.getWorld()Lorg/codehaus/classworlds/ClassWorld; at hudson.maven.agent.Main.main(Main.java:115) at hudson.maven.agent.Main.main(Main.java:62) ERROR: Failed to launch Maven. Exit code = 1 I tried building a Free Style Project on the same but still facing issues. Do we have a solution, please help. Thanks, Amit Pugalia.
Re: Regarding maven 3 integration with Hudson
Artifactory plugin for Hudsonhttp://wiki.hudson-ci.org/display/HUDSON/Artifactory+Pluginsupports Maven 3 builds (as free style projects). You can use it even if you're not using Artifactory. Yossi On Wed, Dec 15, 2010 at 07:32, amit pugalia amit.puga...@gmail.com wrote: Hi, I'm facing issues when using Maven 3 with latest build of Hudson. The maven plugin doesn't seem to be compatible with Maven 3. It throws errors as, C:\hudson1\home\plugins\maven-plugin\WEB-INF\lib\maven-interceptor-1.389.jar 52039 Exception in thread main java.lang.NoSuchMethodError: org.codehaus.classworlds.Launcher.getWorld()Lorg/codehaus/classworlds/ClassWorld; at hudson.maven.agent.Main.main(Main.java:115) at hudson.maven.agent.Main.main(Main.java:62) ERROR: Failed to launch Maven. Exit code = 1 I tried building a Free Style Project on the same but still facing issues. Do we have a solution, please help. Thanks, Amit Pugalia.
Re: [VOTE] Release Maven Surefire Plugin version 2.7 - No problem found, vote is still on
PEBKAC of the slightly embarrasing sort on my end. So the vote is on; happy testing! Kristian - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Maven Surefire Plugin version 2.7
Sorry for chatting on the vote thread here, but fixing the TeeStream memory leak probably also has a noticeable performance impact for users with large numbers of tests and/or lots of console output; It turned out for test number N, any stdout/stderr output would be duplicated into N tee-streams, and they were'nt going away. That's a lot of memory going nowhere. Kristian on., 15.12.2010 kl. 08.g08 -0600, skrev Jeff Jensen: +1 (non-binding) We can finally run a full build with tests from the parent with this version (would OOM unless -Xmx was set to nearly 2G!). :-) On Wed, Dec 15, 2010 at 2:01 AM, chemit che...@codelutin.com wrote: On Wed, 15 Dec 2010 00:21:49 +0100 Kristian Rosenvold kristian.rosenv...@gmail.com wrote: +1 (none binding) Works fine on our project. Thanks! Highlights of the release: * Pluggable providers are now supported, as well as manual provider selection * 2.7 is significantly smaller and lighter than earlier 2.x versions (Only 30% of the download size) * A large chunk of the highest voted issues have been fixed. * Some performance optimizations for forkMode=always * Significant cleanup/simplification of the code-base We solved 22 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10541version=16691 There are still a couple of issues left in JIRA: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truemode=hidejqlQuery=project+%3D+SUREFIRE+AND+resolution+%3D+Unresolved+ORDER+BY+updated+DESC Staging repo: https://repository.apache.org/content/repositories/maven-023/ Staging site: (Sync pending) http://maven.apache.org/plugins/maven-surefire-plugin-2.7/ http://maven.apache.org/plugins/maven-failsafe-plugin-2.7/ http://maven.apache.org/plugins/maven-surefire-report-plugin-2.7/ http://maven.apache.org/surefire/staging/ Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 And here's my +1 Kristian - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Tony Chemit tél: +33 (0) 2 40 50 29 28 email: che...@codelutin.com http://www.codelutin.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 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Maven Surefire Plugin version 2.7
Which clearly explains why, if we reduced the logging output level from DEBUG to WARN, the OOM did not occur with smaller values of -Xmx. That was baffling at the time... Wonderful fix. Thanks! :-) (this problem was the worst for release via parent pom; not happy to -DskipTests on release or ignore uncommitted local changes!) On Wed, Dec 15, 2010 at 8:21 AM, Kristian Rosenvold kristian.rosenv...@gmail.com wrote: Sorry for chatting on the vote thread here, but fixing the TeeStream memory leak probably also has a noticeable performance impact for users with large numbers of tests and/or lots of console output; It turned out for test number N, any stdout/stderr output would be duplicated into N tee-streams, and they were'nt going away. That's a lot of memory going nowhere. Kristian on., 15.12.2010 kl. 08.g08 -0600, skrev Jeff Jensen: +1 (non-binding) We can finally run a full build with tests from the parent with this version (would OOM unless -Xmx was set to nearly 2G!). :-) On Wed, Dec 15, 2010 at 2:01 AM, chemit che...@codelutin.com wrote: On Wed, 15 Dec 2010 00:21:49 +0100 Kristian Rosenvold kristian.rosenv...@gmail.com wrote: +1 (none binding) Works fine on our project. Thanks! Highlights of the release: * Pluggable providers are now supported, as well as manual provider selection * 2.7 is significantly smaller and lighter than earlier 2.x versions (Only 30% of the download size) * A large chunk of the highest voted issues have been fixed. * Some performance optimizations for forkMode=always * Significant cleanup/simplification of the code-base We solved 22 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10541version=16691 There are still a couple of issues left in JIRA: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truemode=hidejqlQuery=project+%3D+SUREFIRE+AND+resolution+%3D+Unresolved+ORDER+BY+updated+DESC Staging repo: https://repository.apache.org/content/repositories/maven-023/ Staging site: (Sync pending) http://maven.apache.org/plugins/maven-surefire-plugin-2.7/ http://maven.apache.org/plugins/maven-failsafe-plugin-2.7/ http://maven.apache.org/plugins/maven-surefire-report-plugin-2.7/ http://maven.apache.org/surefire/staging/ Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 And here's my +1 Kristian - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Tony Chemit tél: +33 (0) 2 40 50 29 28 email: che...@codelutin.com http://www.codelutin.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 - 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
[VOTE] Move Maven Changes Plugin to Java 5
Hi I have some features I'd like to work on for the Changes Plugin. To simplify the work I would like to start using Java 5 features, such as generics for collections. The last release was version 2.3 and after that no issues have been fixed, so I don't see a reason to make a last Java 1.4 release of the current trunk. [ ] +1 Go for it [ ] -1 Don't do it -- Dennis Lundberg - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Move Maven Changes Plugin to Java 5
+1 Den 15. des. 2010 kl. 20:26 skrev Dennis Lundberg denn...@apache.org: Hi I have some features I'd like to work on for the Changes Plugin. To simplify the work I would like to start using Java 5 features, such as generics for collections. The last release was version 2.3 and after that no issues have been fixed, so I don't see a reason to make a last Java 1.4 release of the current trunk. [ ] +1 Go for it [ ] -1 Don't do it -- Dennis Lundberg - 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] Move Maven Changes Plugin to Java 5
Dennis Lundberg wrote: I have some features I'd like to work on for the Changes Plugin. To simplify the work I would like to start using Java 5 features [...] +1 Benjamin - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Maven mirror status/problem
Hi there, some people recommend to use a mirror for maven. Others are required to as their IP address has been blacklisted so they can not reach central (repo1.maven.org) anymore. From what I know mirrors are listed here: http://docs.codehaus.org/display/MAVENUSER/Mirrors+Repositories My feedback on this: 1. http://ftp.cica.es/mirrors/maven2 last_updated.txt: Sat Jan 9 20:15:40 CST 2010 That is pretty outdated... 2. http://repo1.sonatype.net/maven2 Does not work. I get always get 404. 3. http://repo.exist.com/maven2/ last_updated.txt: Tue Nov 23 22:30:45 CST 2010 Not up-to-date... 4. http://mirrors.ibiblio.org/pub/mirrors/maven2 last_updated.txt: Tue Nov 30 22:54:22 CST 2010 Not really up-to-date... 5. http://www.ibiblio.net/pub/packages/maven2 Is always redirecting to http://mirrors.ibiblio.org/pub/mirrors/maven2 6. http://mirrors.redv.com/maven2 I get 403 - maybe only visible in china... 7. http://mirrors.dotsrc.org/maven Does not work. I get always get 404. 8. http://mirrors.sunsite.dk/maven2 Does not work. I get always get 404. 9. http://mirror.netcologne.de/maven2 last_updated.txt: Tue Nov 30 22:54:22 CST 2010 Not really up-to-date... I do not know what you actually expect from a mirror, but in other universes (e.g. linux) a real mirror is usually never older than 2 days. Of course nobody owns the maven community anything and everybody can start his own mirror. However banning people from central in this case seems to be a hard punishment and there should be some process to get out of this again. I can perfectly access central but I have some friends that have been blacklisted. If someone can confirm the errors with the mirrors sending 404, we can at least remove them from the wiki page. Maybe also the sync of the outdated mirrors has been broken for some reason and someone can check this. Thanks Jörg - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Maven mirror status/problem
The two that will always work are: http://uk.maven.org/maven2/ and http://repo1.maven.org/maven2/ Scrapers will definitely get blocked and stay blocked. But no normal user stays blocked if they inadvertently hit the tripwires. Only takes a short conversation, proving that the activity which caused getting banned was accidental or unintentional. We, Sonatype, are looking at setting up a third mirror but it doesn't seem to be necessary at this point in time. On Dec 15, 2010, at 3:32 PM, Jörg Hohwiller wrote: Hi there, some people recommend to use a mirror for maven. Others are required to as their IP address has been blacklisted so they can not reach central (repo1.maven.org) anymore. From what I know mirrors are listed here: http://docs.codehaus.org/display/MAVENUSER/Mirrors+Repositories My feedback on this: 1. http://ftp.cica.es/mirrors/maven2 last_updated.txt: Sat Jan 9 20:15:40 CST 2010 That is pretty outdated... 2. http://repo1.sonatype.net/maven2 Does not work. I get always get 404. 3. http://repo.exist.com/maven2/ last_updated.txt: Tue Nov 23 22:30:45 CST 2010 Not up-to-date... 4. http://mirrors.ibiblio.org/pub/mirrors/maven2 last_updated.txt: Tue Nov 30 22:54:22 CST 2010 Not really up-to-date... 5. http://www.ibiblio.net/pub/packages/maven2 Is always redirecting to http://mirrors.ibiblio.org/pub/mirrors/maven2 6. http://mirrors.redv.com/maven2 I get 403 - maybe only visible in china... 7. http://mirrors.dotsrc.org/maven Does not work. I get always get 404. 8. http://mirrors.sunsite.dk/maven2 Does not work. I get always get 404. 9. http://mirror.netcologne.de/maven2 last_updated.txt: Tue Nov 30 22:54:22 CST 2010 Not really up-to-date... I do not know what you actually expect from a mirror, but in other universes (e.g. linux) a real mirror is usually never older than 2 days. Of course nobody owns the maven community anything and everybody can start his own mirror. However banning people from central in this case seems to be a hard punishment and there should be some process to get out of this again. I can perfectly access central but I have some friends that have been blacklisted. If someone can confirm the errors with the mirrors sending 404, we can at least remove them from the wiki page. Maybe also the sync of the outdated mirrors has been broken for some reason and someone can check this. Thanks Jörg - 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 - You are never dedicated to something you have complete confidence in. No one is fanatically shouting that the sun is going to rise tomorrow. They know it is going to rise tomorrow. When people are fanatically dedicated to political or religious faiths or any other kind of dogmas or goals, it's always because these dogmas or goals are in doubt. -- Robert Pirzig, Zen and the Art of Motorcycle Maintenance
Re: Maven mirror status/problem
Hi, I guess I am one of those scrapers. Could you please tell me how can I get all pom files stored in the central repository? (I just need them for research.) Should I setup a mirror? If so how can I do so? Thanks. On Wed, Dec 15, 2010 at 22:52, Jason van Zyl ja...@maven.org wrote: The two that will always work are: http://uk.maven.org/maven2/ and http://repo1.maven.org/maven2/ Scrapers will definitely get blocked and stay blocked. But no normal user stays blocked if they inadvertently hit the tripwires. Only takes a short conversation, proving that the activity which caused getting banned was accidental or unintentional. We, Sonatype, are looking at setting up a third mirror but it doesn't seem to be necessary at this point in time. On Dec 15, 2010, at 3:32 PM, Jörg Hohwiller wrote: Hi there, some people recommend to use a mirror for maven. Others are required to as their IP address has been blacklisted so they can not reach central (repo1.maven.org) anymore. From what I know mirrors are listed here: http://docs.codehaus.org/display/MAVENUSER/Mirrors+Repositories My feedback on this: 1. http://ftp.cica.es/mirrors/maven2 last_updated.txt: Sat Jan 9 20:15:40 CST 2010 That is pretty outdated... 2. http://repo1.sonatype.net/maven2 Does not work. I get always get 404. 3. http://repo.exist.com/maven2/ last_updated.txt: Tue Nov 23 22:30:45 CST 2010 Not up-to-date... 4. http://mirrors.ibiblio.org/pub/mirrors/maven2 last_updated.txt: Tue Nov 30 22:54:22 CST 2010 Not really up-to-date... 5. http://www.ibiblio.net/pub/packages/maven2 Is always redirecting to http://mirrors.ibiblio.org/pub/mirrors/maven2 6. http://mirrors.redv.com/maven2 I get 403 - maybe only visible in china... 7. http://mirrors.dotsrc.org/maven Does not work. I get always get 404. 8. http://mirrors.sunsite.dk/maven2 Does not work. I get always get 404. 9. http://mirror.netcologne.de/maven2 last_updated.txt: Tue Nov 30 22:54:22 CST 2010 Not really up-to-date... I do not know what you actually expect from a mirror, but in other universes (e.g. linux) a real mirror is usually never older than 2 days. Of course nobody owns the maven community anything and everybody can start his own mirror. However banning people from central in this case seems to be a hard punishment and there should be some process to get out of this again. I can perfectly access central but I have some friends that have been blacklisted. If someone can confirm the errors with the mirrors sending 404, we can at least remove them from the wiki page. Maybe also the sync of the outdated mirrors has been broken for some reason and someone can check this. Thanks Jörg - 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 - You are never dedicated to something you have complete confidence in. No one is fanatically shouting that the sun is going to rise tomorrow. They know it is going to rise tomorrow. When people are fanatically dedicated to political or religious faiths or any other kind of dogmas or goals, it's always because these dogmas or goals are in doubt. -- Robert Pirzig, Zen and the Art of Motorcycle Maintenance -- Ersin Er
Re: [VOTE] Move Maven Changes Plugin to Java 5
+1 (non-binding). Let's kill Merlin, HopperMantis in the same shoot! :-). Cheers 2010/12/15 Kristian Rosenvold kristian.rosenv...@gmail.com +1 Den 15. des. 2010 kl. 20:26 skrev Dennis Lundberg denn...@apache.org: Hi I have some features I'd like to work on for the Changes Plugin. To simplify the work I would like to start using Java 5 features, such as generics for collections. The last release was version 2.3 and after that no issues have been fixed, so I don't see a reason to make a last Java 1.4 release of the current trunk. [ ] +1 Go for it [ ] -1 Don't do it -- Dennis Lundberg - 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 -- Baptiste Batmat MATHUS - http://batmat.net Sauvez un arbre, Mangez un castor !
[VOTE] Establish a creation and retirement plan for plugins
Hi No one objected to the proposal I made on November 1. Jason and I have polished the proposal based on the comments that were made. The final (?) version can be found here: https://cwiki.apache.org/confluence/display/MAVEN/Proposal+--+A+creation+and+retirement+plan+for+plugins Please vote on whether we should make this proposal our policy. [ ] +1 Let's use it [ ] -1 No way If the vote succeeds I'll put it on the Maven site somewhere. Suggestions on where to put are welcome. -- Dennis Lundberg - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Establish a creation and retirement plan for plugins
Greetings, On Wed, Dec 15, 2010 at 4:52 PM, Dennis Lundberg denn...@apache.org wrote: https://cwiki.apache.org/confluence/display/MAVEN/Proposal+--+A+creation+and+retirement+plan+for+plugins From the proposal: 2. Make one final release of the plugin before it is retired. This allows us to make a clean break. The final release must change the POM so that SCM URLs are removed or changed to reflect the decision made in the vote. If the plugin is moved elsewhere a prominent notice must be placed on the front page of the plugin's site. The person who wants to retire a plugin is the one who does the final release. This seems wrong to me. Why would we make a final release from the official Maven forge and yet have an SCM which points somewhere else? This seems really misleading; certainly more-so than a future user going to the (now defunct) SCM and not finding the plugin and having to do some enlightenment work about where the release is now. I'm not even sure the m-release-p could technically handle such a thing. -Jesse -- There are 10 types of people in this world, those that can read binary and those that can not. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Establish a creation and retirement plan for plugins
2. Make one final release of the plugin before it is retired. This allows us to make a clean break. The final release must change the POM so that SCM URLs are removed or changed to reflect the decision made in the vote. If the plugin is moved elsewhere a prominent notice must be placed on the front page of the plugin's site. The person who wants to retire a plugin is the one who does the final release. This seems wrong to me. Why would we make a final release from the official Maven forge and yet have an SCM which points somewhere else? This seems really misleading; certainly more-so than a future user going to the (now defunct) SCM and not finding the plugin and having to do some enlightenment work about where the release is now. I'm not even sure the m-release-p could technically handle such a thing. Amplfication: The typical m-r-p-published POM points to the tag: the place in SCM to find the exact source that the release was built from. That still seems like exactly the right place for the final release scm tag to point. Perhaps putting an explanation in the description/ of the new home (if any) would be more helpful? - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Maven mirror status/problem
On 16/12/2010, at 7:32 AM, Jörg Hohwiller wrote: 3. http://repo.exist.com/maven2/ last_updated.txt: Tue Nov 23 22:30:45 CST 2010 Not up-to-date... 4. http://mirrors.ibiblio.org/pub/mirrors/maven2 last_updated.txt: Tue Nov 30 22:54:22 CST 2010 Not really up-to-date... These two were kept officially up to date before, being pushed from the main content box. I think the others pulled from ibiblio, but as you've seen most went out of service. Brian, can you tell me why the first sync is not working again (we fixed it just days before that)? I meant to set up a monitor afterwards... but can you make it email me whenever there's a failure? I'd turned that off, but since we no longer have any access I need to know why it's failing in case it's something I can still fix on the other end. - Brett -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ http://au.linkedin.com/in/brettporter - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Establish a creation and retirement plan for plugins
On 2010-12-15 23:03, Jesse Farinacci wrote: Greetings, On Wed, Dec 15, 2010 at 4:52 PM, Dennis Lundberg denn...@apache.org wrote: https://cwiki.apache.org/confluence/display/MAVEN/Proposal+--+A+creation+and+retirement+plan+for+plugins From the proposal: 2. Make one final release of the plugin before it is retired. This allows us to make a clean break. The final release must change the POM so that SCM URLs are removed or changed to reflect the decision made in the vote. If the plugin is moved elsewhere a prominent notice must be placed on the front page of the plugin's site. The person who wants to retire a plugin is the one who does the final release. This seems wrong to me. Why would we make a final release from the official Maven forge and yet have an SCM which points somewhere else? This seems really misleading; certainly more-so than a future user going to the (now defunct) SCM and not finding the plugin and having to do some enlightenment work about where the release is now. Right, removing the Source Repository *report* is probably the best way to go. I'm not even sure the m-release-p could technically handle such a thing. -Jesse -- Dennis Lundberg - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Maven mirror status/problem
That page is garbage and should be dumped. The official list is maintained in the repo itself: http://repo1.maven.org/maven2/.meta/repository-metadata.xml On Wed, Dec 15, 2010 at 3:32 PM, Jörg Hohwiller jo...@j-hohwiller.de wrote: Hi there, some people recommend to use a mirror for maven. Others are required to as their IP address has been blacklisted so they can not reach central (repo1.maven.org) anymore. From what I know mirrors are listed here: http://docs.codehaus.org/display/MAVENUSER/Mirrors+Repositories My feedback on this: 1. http://ftp.cica.es/mirrors/maven2 last_updated.txt: Sat Jan 9 20:15:40 CST 2010 That is pretty outdated... 2. http://repo1.sonatype.net/maven2 Does not work. I get always get 404. 3. http://repo.exist.com/maven2/ last_updated.txt: Tue Nov 23 22:30:45 CST 2010 Not up-to-date... 4. http://mirrors.ibiblio.org/pub/mirrors/maven2 last_updated.txt: Tue Nov 30 22:54:22 CST 2010 Not really up-to-date... 5. http://www.ibiblio.net/pub/packages/maven2 Is always redirecting to http://mirrors.ibiblio.org/pub/mirrors/maven2 6. http://mirrors.redv.com/maven2 I get 403 - maybe only visible in china... 7. http://mirrors.dotsrc.org/maven Does not work. I get always get 404. 8. http://mirrors.sunsite.dk/maven2 Does not work. I get always get 404. 9. http://mirror.netcologne.de/maven2 last_updated.txt: Tue Nov 30 22:54:22 CST 2010 Not really up-to-date... I do not know what you actually expect from a mirror, but in other universes (e.g. linux) a real mirror is usually never older than 2 days. Of course nobody owns the maven community anything and everybody can start his own mirror. However banning people from central in this case seems to be a hard punishment and there should be some process to get out of this again. I can perfectly access central but I have some friends that have been blacklisted. If someone can confirm the errors with the mirrors sending 404, we can at least remove them from the wiki page. Maybe also the sync of the outdated mirrors has been broken for some reason and someone can check this. Thanks Jörg - 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] Establish a creation and retirement plan for plugins
On 16/12/2010, at 10:00 AM, Dennis Lundberg wrote: On 2010-12-15 23:03, Jesse Farinacci wrote: Greetings, On Wed, Dec 15, 2010 at 4:52 PM, Dennis Lundberg denn...@apache.org wrote: https://cwiki.apache.org/confluence/display/MAVEN/Proposal+--+A+creation+and+retirement+plan+for+plugins From the proposal: 2. Make one final release of the plugin before it is retired. This allows us to make a clean break. The final release must change the POM so that SCM URLs are removed or changed to reflect the decision made in the vote. If the plugin is moved elsewhere a prominent notice must be placed on the front page of the plugin's site. The person who wants to retire a plugin is the one who does the final release. This seems wrong to me. Why would we make a final release from the official Maven forge and yet have an SCM which points somewhere else? This seems really misleading; certainly more-so than a future user going to the (now defunct) SCM and not finding the plugin and having to do some enlightenment work about where the release is now. Right, removing the Source Repository *report* is probably the best way to go. Agree. I'd also make the release preferred but optional - there's a good chance you won't get the energy to do that if there's not energy to continue. It probably is on a case by case basis of how many changes have been made on trunk since and if they are valuable to release. I think we can also now recommend apache-extras.org as a suitable forge along with mojo. I'm +1 to the proposal with or without those changes. - Brett -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ http://au.linkedin.com/in/brettporter - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Cleanup to SNAPSHOT version handling
Hi there, FYI: I use SNAPSHOT as version for internal artifacts (site-configurations with checkstyle, etc.) to denote that they will never get released. However in such case one typically does not need real SNAPSHOT support by maven. I could also name the version notversioned or 0.0. Regards Jörg If x-SNAPSHOT.release() = x then SNAPSHOT.release()= npe or divide by zero, take your pick :) I always made sure to point out this anti-pattern during all the maven training classes I did. --mobile On Dec 13, 2010, at 6:42 AM, Benjamin Bentmann benjamin.bentm...@udo.edu wrote: Brett Porter wrote: [...] SNAPSHOT (with no leading version) was valid, but that behaviour has long been (unofficially) deprecated. Do you have some more pointers for this deprecation handy? 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 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Maven mirror status/problem
Hi, Hi there, I guess I am one of those scrapers. Could you please tell me how can I get all pom files stored in the central repository? (I just need them for research.) Should I setup a mirror? If so how can I do so? You can simply use a maven repository server such as nexus, artifactory or archiva. However if you crawl the entire repository once it will not make a difference. Only if you download the same artifacts multiple time the repository server will act as proxy (like your local repo) to prevent repetitive downloads. But downloading all pom files should be avoided within a short time. Please use a delay to reduce the load and if possible use a mirror... Thanks. Thanks for taking care Jörg - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Maven mirror status/problem
Hi Brian, That page is garbage and should be dumped. The official list is maintained in the repo itself: http://repo1.maven.org/maven2/.meta/repository-metadata.xml thanks for clarification. I put the link on the wiki site as the wiki site itself is linked from various other sites. Regards Jörg - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Cleanup to SNAPSHOT version handling
Or, 1-SNAPSHOT. Or, DO-NOT-RELEASE-1-SNAPSHOT On Wed, Dec 15, 2010 at 6:33 PM, Jörg Hohwiller jo...@j-hohwiller.de wrote: Hi there, FYI: I use SNAPSHOT as version for internal artifacts (site-configurations with checkstyle, etc.) to denote that they will never get released. However in such case one typically does not need real SNAPSHOT support by maven. I could also name the version notversioned or 0.0. Regards Jörg If x-SNAPSHOT.release() = x then SNAPSHOT.release()= npe or divide by zero, take your pick :) I always made sure to point out this anti-pattern during all the maven training classes I did. --mobile On Dec 13, 2010, at 6:42 AM, Benjamin Bentmann benjamin.bentm...@udo.edu wrote: Brett Porter wrote: [...] SNAPSHOT (with no leading version) was valid, but that behaviour has long been (unofficially) deprecated. Do you have some more pointers for this deprecation handy? 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 - 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] Establish a creation and retirement plan for plugins
On Dec 15, 2010, at 4:52 PM, Dennis Lundberg wrote: Hi No one objected to the proposal I made on November 1. Jason and I have polished the proposal based on the comments that were made. The final (?) version can be found here: https://cwiki.apache.org/confluence/display/MAVEN/Proposal+--+A+creation+and+retirement+plan+for+plugins Please vote on whether we should make this proposal our policy. [ ] +1 Let's use it [ ] -1 No way +1 If the vote succeeds I'll put it on the Maven site somewhere. Suggestions on where to put are welcome. -- Dennis Lundberg - 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 - the course of true love never did run smooth ... -- Shakespeare
Re: [VOTE] Establish a creation and retirement plan for plugins
I agree that the final release should be optional. I would also add that the site must be updated to say the plugin is retired whether it is moved somewhere else or not. Ralph On Dec 15, 2010, at 3:17 PM, Brett Porter wrote: On 16/12/2010, at 10:00 AM, Dennis Lundberg wrote: On 2010-12-15 23:03, Jesse Farinacci wrote: Greetings, On Wed, Dec 15, 2010 at 4:52 PM, Dennis Lundberg denn...@apache.org wrote: https://cwiki.apache.org/confluence/display/MAVEN/Proposal+--+A+creation+and+retirement+plan+for+plugins From the proposal: 2. Make one final release of the plugin before it is retired. This allows us to make a clean break. The final release must change the POM so that SCM URLs are removed or changed to reflect the decision made in the vote. If the plugin is moved elsewhere a prominent notice must be placed on the front page of the plugin's site. The person who wants to retire a plugin is the one who does the final release. This seems wrong to me. Why would we make a final release from the official Maven forge and yet have an SCM which points somewhere else? This seems really misleading; certainly more-so than a future user going to the (now defunct) SCM and not finding the plugin and having to do some enlightenment work about where the release is now. Right, removing the Source Repository *report* is probably the best way to go. Agree. I'd also make the release preferred but optional - there's a good chance you won't get the energy to do that if there's not energy to continue. It probably is on a case by case basis of how many changes have been made on trunk since and if they are valuable to release. I think we can also now recommend apache-extras.org as a suitable forge along with mojo. I'm +1 to the proposal with or without those changes. - Brett -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ http://au.linkedin.com/in/brettporter - 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] Move Maven Changes Plugin to Java 5
On Wed, 15 Dec 2010 20:25:24 +0100 Dennis Lundberg denn...@apache.org wrote: Hi +1 (non binding) I have some features I'd like to work on for the Changes Plugin. To simplify the work I would like to start using Java 5 features, such as generics for collections. The last release was version 2.3 and after that no issues have been fixed, so I don't see a reason to make a last Java 1.4 release of the current trunk. [ ] +1 Go for it [ ] -1 Don't do it -- Tony Chemit tél: +33 (0) 2 40 50 29 28 email: che...@codelutin.com http://www.codelutin.com - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Maven Surefire Plugin version 2.7
+1 -Lukas Kristian Rosenvold wrote: Highlights of the release: * Pluggable providers are now supported, as well as manual provider selection * 2.7 is significantly smaller and lighter than earlier 2.x versions (Only 30% of the download size) * A large chunk of the highest voted issues have been fixed. * Some performance optimizations for forkMode=always * Significant cleanup/simplification of the code-base We solved 22 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10541version=16691 There are still a couple of issues left in JIRA: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truemode=hidejqlQuery=project+%3D+SUREFIRE+AND+resolution+%3D+Unresolved+ORDER+BY+updated+DESC Staging repo: https://repository.apache.org/content/repositories/maven-023/ Staging site: (Sync pending) http://maven.apache.org/plugins/maven-surefire-plugin-2.7/ http://maven.apache.org/plugins/maven-failsafe-plugin-2.7/ http://maven.apache.org/plugins/maven-surefire-report-plugin-2.7/ http://maven.apache.org/surefire/staging/ Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 And here's my +1 Kristian - 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] Move Maven Changes Plugin to Java 5
+1 -Lukas Dennis Lundberg wrote: Hi I have some features I'd like to work on for the Changes Plugin. To simplify the work I would like to start using Java 5 features, such as generics for collections. The last release was version 2.3 and after that no issues have been fixed, so I don't see a reason to make a last Java 1.4 release of the current trunk. [ ] +1 Go for it [ ] -1 Don't do it - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Establish a creation and retirement plan for plugins
+1 for the retirement part of the proposal but I'm a bit confused about icluding a creation plan (I haven't followed the discussion up to now though). The current procedure for adding new plugins IIRC is to first put it in the sandbox and then call a vote to promote it out of there. Is this meant to be made obsolete? -Lukas Dennis Lundberg wrote: Hi No one objected to the proposal I made on November 1. Jason and I have polished the proposal based on the comments that were made. The final (?) version can be found here: https://cwiki.apache.org/confluence/display/MAVEN/Proposal+--+A+creation+and+retirement+plan+for+plugins Please vote on whether we should make this proposal our policy. [ ] +1 Let's use it [ ] -1 No way If the vote succeeds I'll put it on the Maven site somewhere. Suggestions on where to put are welcome. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
