Re: [VOTE] Release Maven SCM 1.5
+1 - Fabrice belling...@apache.org fabrice.belling...@sonarsource.com On Tue, Mar 29, 2011 at 12:30 AM, Olivier Lamy ol...@apache.org wrote: Hi, I'd like to release Apache Maven SCM 1.5. We solved 32 issues : http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10527version=16688 Staging repo: https://repository.apache.org/content/repositories/maven-051/ Staging sites : Scm : http://maven.apache.org/scm-1.5 Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 Thanks, -- Olivier Lamy http://twitter.com/olamy http://www.linkedin.com/in/olamy - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Apache Maven 3.0.3
+1 Thanks, - Fabrice belling...@apache.org fabrice.belling...@sonarsource.com On Mon, Feb 28, 2011 at 6:58 PM, Benjamin Bentmann benjamin.bentm...@udo.edu wrote: Hi, Thanks to those who tested the RC, I think we can move on to the real thing now. We solved 29 issues since 3.0.2: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500version=17061 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-065/ Staged source and binary distros: https://repository.apache.org/content/repositories/maven-065/org/apache/maven/apache-maven/3.0.3/ 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: Invite Evgeny Mandrikov to join Maven committers
+1! (non-binding) ;-) - Fabrice belling...@apache.org fabrice.belling...@sonarsource.com On Wed, Jan 26, 2011 at 7:30 AM, Olivier Lamy ol...@apache.org wrote: Hello, I propose Evgeny Mandrikov as a new committer. He as done a lot of patches for Maven SCM, he is a Mojo and Sonar contributor @codehaus. Vote is open for 72H. Here my +1. Thanks, -- Olivier Lamy http://twitter.com/olamy http://www.linkedin.com/in/olamy - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Apache Maven 3.0.2
Tested and no problem so far. So here's my +1 - Fabrice belling...@apache.org fabrice.belling...@sonarsource.com On Sun, Jan 9, 2011 at 2:20 AM, Benjamin Bentmann benjamin.bentm...@udo.edu wrote: Hi, We solved 25 issues since 3.0.1: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500version=16952 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-011/ Staged source and binary distros: https://repository.apache.org/content/repositories/maven-011/org/apache/maven/apache-maven/3.0.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: [VOTE] Release Apache Maven 3.0
+1 Used to build Sonar, no problem. - Fabrice belling...@apache.org On Mon, Oct 4, 2010 at 2:16 PM, Benjamin Bentmann benjamin.bentm...@udo.edu wrote: Hi, feedback on the RCs seems to be decreasing and I am currently not aware of any major regression so let's try and cross the finishing line of this marathon. We solved 31 issues since 3.0-beta-3: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500version=13142 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-004/ Staged source and binary distros: https://repository.apache.org/content/repositories/maven-004/org/apache/maven/apache-maven/3.0/ 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: [VOTE] Release Maven PDF plugin version 1.1
+1! :-) - Fabrice belling...@apache.org On Thu, Dec 10, 2009 at 10:14 AM, Lukas Theussl ltheu...@apache.org wrote: +1 Thanks! -Lukas Vincent Siveton wrote: Hi, We solved around 10 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11932version=15414styleName=Html There are still a couple of issues left in JIRA: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=11932status=1 Staging repo: https://repository.apache.org/content/repositories/maven-044 Staging site (need to sync) http://maven.apache.org/plugins/maven-pdf-plugin-1.1/ 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 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [vote] Invite Stephen Connolly to join Maven committers
+1 - Fabrice belling...@apache.org On Mon, Sep 7, 2009 at 1:24 AM, Arnaud HERITIER arnaud.herit...@exoplatform.com wrote: Hi all, I'd like to propose giving commit access to Stephen Connolly. He is already a committer @ Mojo for many monthes and did a great work on several plugins. He is the author of the very useful versions plugin. He is working on several others plugins like animal-sniffer. He's doing a job of quality (with unit and integration tests) and follows our best practices. He's participating on our mailing lists for a least 2 years. I helped him several time to apply some patches on our plugins and shared components. Now he would like to help on toolchains and adding its support in enforcer. I think we need more people as involved as Stephen has been. Please vote. 72h +1/+0/-1 Here is my +1. Cheers, Arnaud # Arnaud Héritier # Software Factory Manager # eXo Platform # http://www.exoplatform.com # http://blog.aheritier.net
Re: Adding a Looking for Code Quality Managers section into the Maven web site ?
I committed the new page and updated the home page as well. See r811294. The changes will be visible the next time the site will be generated. Cheers, - Fabrice belling...@apache.org On Thu, Sep 3, 2009 at 9:49 PM, Arnaud HERITIER arnaud.herit...@exoplatform.com wrote: +1 it's a really good idea. Cheers arnaud On Thursday, September 3, 2009, Freddy Mallet freddy.mal...@gmail.com wrote: Oups Fabrice, I'm really sorry and of course Squale must join this list. If you can handle this modification by yourself, that's perfect ! cheers Freddy Mallet http://www.SonarSource.com http://Sonar.codehaus.org http://twitter.com/FreddyMallet On Wed, Sep 2, 2009 at 11:45 PM, Fabrice Bellingard belling...@gmail.comwrote: Hi Freddy, +1 for me as well, excellent idea. And I will also add Squale - the OSS project I'm leading [1] - to this already nice list. :-) Olivier, I can handle that if you want - if there's no objection with this idea, of course. Cheers, - Fabrice belling...@apache.org [1] http://www.squale.org On Wed, Sep 2, 2009 at 11:19 PM, Freddy Mallet freddy.mal...@gmail.com wrote: Hi all, This proposal is submitted by Romain Pelisse, leader of XRadar Khosuke Kawaguchi, leader of a well known CI server David Vincente, leader of the Maven Dashboard plugin and myself, co-leader of Sonar The idea is simply to add a new Looking for Code Quality Managers section into the right sidebar of the Maven web site homepage bellow Looking for Repository Managers and Looking for CI Servers. This section would contain a short text Take a look at the Code Quality Management platforms available from the community. Clicking on Take a look would display a list of tools with XRadar, Sonar, Maven Dashboard and Hudson (as it contains on the shelf quality reports). It has never been so easy with those tools to monitor source code's health and beginning to combine metrics. Good part of software development departments, which are using Maven, are progressively adopting such quality platforms. We think the Maven ecosystem would be reinforced if it welcomed those quality platforms which are highly based and fully integrated with Maven. Any feedback, bad or good, is welcome. Thanks Romain, Khosuke, David and Freddy -- Cheers, Arnaud # Arnaud Héritier # Software Factory Manager # eXo Platform # http://www.exoplatform.com # http://blog.aheritier.net - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Adding a Looking for Code Quality Managers section into the Maven web site ?
Hi Freddy, +1 for me as well, excellent idea. And I will also add Squale - the OSS project I'm leading [1] - to this already nice list. :-) Olivier, I can handle that if you want - if there's no objection with this idea, of course. Cheers, - Fabrice belling...@apache.org [1] http://www.squale.org On Wed, Sep 2, 2009 at 11:19 PM, Freddy Mallet freddy.mal...@gmail.comwrote: Hi all, This proposal is submitted by Romain Pelisse, leader of XRadar Khosuke Kawaguchi, leader of a well known CI server David Vincente, leader of the Maven Dashboard plugin and myself, co-leader of Sonar The idea is simply to add a new Looking for Code Quality Managers section into the right sidebar of the Maven web site homepage bellow Looking for Repository Managers and Looking for CI Servers. This section would contain a short text Take a look at the Code Quality Management platforms available from the community. Clicking on Take a look would display a list of tools with XRadar, Sonar, Maven Dashboard and Hudson (as it contains on the shelf quality reports). It has never been so easy with those tools to monitor source code's health and beginning to combine metrics. Good part of software development departments, which are using Maven, are progressively adopting such quality platforms. We think the Maven ecosystem would be reinforced if it welcomed those quality platforms which are highly based and fully integrated with Maven. Any feedback, bad or good, is welcome. Thanks Romain, Khosuke, David and Freddy
Re: [VOTE] Release Doxia-1.1.1 and Doxia-Sitetools-1.1.1
+1 - Fabrice belling...@apache.org On Thu, May 14, 2009 at 9:59 AM, Lukas Theussl ltheu...@apache.org wrote: Hi, We solved 27 (Doxia) and 3 (Sitetools) issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10780styleName=Htmlversion=15073 http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11624styleName=Htmlversion=15075 There are still a couple of issues left in JIRA: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=10780status=1 http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=11624status=1 Staging repo: https://repository.apache.org/content/repositories/maven-staging-020/ Staging site: http://maven.apache.org/doxia/ Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Note 1: the most convenient way to test these (I think) is to use site-plugin-2.1-SNAPSHOT and/or pdf-plugin-1.0-SNAPSHOT, which both use the latest doxia snaps. Note 2: I noticed after deploying the site that there was a wrong link to the document xsd in the javadocs. I have corrected that in the release tag and on trunk. This only affects the site docs, not the binary so I think it should be ok. Vote open for 72 hours. [x] +1 [ ] +0 [ ] -1 Thanks, -Lukas - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Maven eclipse plugin version 2.6
+1 - Fabrice belling...@apache.org On Tue, Mar 24, 2009 at 1:05 AM, Barrie Treloar baerr...@gmail.com wrote: Hi, We solved 35 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?version=14163styleName=HtmlprojectId=11133 There remaining issues left in JIRA: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=11133status=1 Staging repo: https://repository.apache.org/content/repositories/maven-staging-52acfb2f215fcf/ Staging site: http://maven.apache.org/plugins/maven-eclipse-plugin-2.6/ 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] Maven 2.1.0
Yeahhh, let's go! +1! :-) - Fabrice belling...@apache.org On Thu, Mar 19, 2009 at 1:12 AM, John Casey jdca...@commonjava.org wrote: Hi everyone, It looks like Maven 2.1.0 is ready to release. You can try the binaries here: http://tinyurl.com/maven-2-1-0-vote ( https://repository.apache.org/content/repositories/maven-staging-511ea882714d8b/org/apache/maven/apache-maven/2.1.0/ ) We've resolved 85 issues for this release (enumerated at the end of this message): http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500styleName=Htmlversion=14587 Vote's open for 72 hours. Please cast your vote: [ ] +1 [ ] +0 [ ] -1 Here's my +1. Thanks, -john === Release Notes - Maven 2 - Version 2.1.0 ** Sub-task * [MNG-4025] - Prominently document opt-out setting for parallel artifact resolution for users * [MNG-4042] - Use plexus-sec-dispatcher 1.0 in Maven core when it is released ** Bug * [MNG-1349] - openssl checksums are not accepted by maven * [MNG-1585] - debug logging from wagon not shown in debug mode * [MNG-1992] - CLI -D should override properties in settings.xml * [MNG-1999] - Reporting inheritance does not work properly * [MNG-2432] - Apache and Mojo plugins take precendence over plugins in the pom. * [MNG-2433] - Maven looks for snapshots in offline mode * [MNG-2605] - Profiles in profiles.xml are active by default * [MNG-2668] - Plugin dependencies should be considered when the reactor creates the build order list * [MNG-2690] - DefaultPluginManager.getConfiguredMojo() doesn't handle NoClassDefFoundError correctly * [MNG-2695] - -o makes build fail for snapshot plugins * [MNG-2720] - Multiproject dependencies not accurate for project.compileClasspathElements when run from root project * [MNG-3023] - Reactor projects should be included in dependency resolution * [MNG-3057] - properties not expanded in generated POMs when building A/B/C nested projects * [MNG-3139] - The skin does not exist: Unable to determine the release version * [MNG-3217] - a plugin's dependencies can influence other plugins in a build * [MNG-3228] - Maven profile activation does not work when profile is defined in inherited 'parent' pom * [MNG-3271] - excludeDefaults does not seem to work * [MNG-3284] - Cached plugins are used, even when the specifically declared * [MNG-3314] - offline build not running, when having SNAPSHOT dependencies * [MNG-3621] - site url inheritance broken for UNC paths * [MNG-3628] - When running offline, snapshot artifcats cannot be resolved even if they have previously be dowloaded from a repository * [MNG-3641] - Lack of error checks on profiles * [MNG-3645] - Maven doesn't do strict model validation for POMs in the current reactor * [MNG-3719] - [regression] plugin execution ordering no longer POM ordered in 2.0.9 * [MNG-3757] - Setting M2_HOME to nothing and running ant delets contents of the current folder * [MNG-3769] - [regression] Excluding relocated transitive dependencies does not work * [MNG-3776] - Namespace misspelled in settings.xml * [MNG-3808] - Execution order of report plugins is arbitrary if inheritance is involved * [MNG-3810] - [regression] Null Pointer Exception when Activation Profile Property is Empty * [MNG-3811] - Report plugins don't inherit configuration * [MNG-3899] - Inheritance does not merge extensions with same gid and aid * [MNG-3906] - Project-level plugin dependencies are in random order after merging * [MNG-3920] - Problem using velocity component * [MNG-3930] - mvn.bat doesn't handle ampersand in Windows user name properly * [MNG-3933] - Profiles.xml does not pickup OS family * [MNG-3940] - Interpolation of environment variables is not case-insensitive on Windows * [MNG-3948] - Remote repos defined by profiles outside of settings.xml are not used to resolve parent POMs * [MNG-3974] - New mirror syntax is not stopping on first match * [MNG-4016] - Properties with the prefix project/pom are not interpolated from the properties section * [MNG-4023] - Profiles from parent POM are injected multiple times if parent is part of reactor build * [MNG-4026] - [regression] Order of project class path does not match POM order during reactor build * [MNG-4032] - Test jar dependency not available for for main classes in multi module builds * [MNG-4043] - Resolve or rollback WebDAV wagon deployment issue where hostname is improperly extracted from URL * [MNG-4074] - cyclic reference with 2.1.0-RC1 that doesn't occur with 2.0.10 * [MNG-4079] - Duplicate error messages * [MNG-4084] - Unnecessary Warning for an activate profile in child project * [MNG-4086] - [regression] Explicitly using plugin metaversions crashes plugin manager * [MNG-4087] - Percent encoded characters in file URLs are not decoded upon deployment
Re: [VOTE] Release Maven Site Plugin version 2.0
+1 - Fabrice belling...@apache.org On Sun, Mar 8, 2009 at 3:25 PM, Dennis Lundberg denn...@apache.org wrote: Hi, We solved 24 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11146styleName=Htmlversion=13362 There are still a couple of issues left in JIRA: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=11146status=1 Staging repo: https://repository.apache.org/content/repositories/maven-staging-4dfc6c642b1c81/ Staging site: http://maven.apache.org/plugins/maven-site-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 -- Dennis Lundberg - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [PLEASE TEST] Maven 2.1.0-RC1
Hi John, everything's building fine here! Great :-) - Fabrice belling...@apache.org On Mon, Mar 9, 2009 at 5:00 PM, John Casey jdca...@commonjava.org wrote: Hi everyone, I've rolled the first release candidate for Maven 2.1.0. It's available at: http://tinyurl.com/maven-2-1-0-RC1 ( https://repository.apache.org/content/repositories/maven-staging-4e4fa48c70323f/org/apache/maven/apache-maven/2.1.0/ ) The staging repository root is at: https://repository.apache.org/content/repositories/maven-staging-4e4fa48c70323f If you have time, please take a look and see if you can break it! BTW, the JIRA version notes for this release are at: http://tinyurl.com/maven-2-1-0-jira ( http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500styleName=Htmlversion=14587 ) If we can't find anything wrong with this release candidate after maybe four or five days at most, I'll call the vote for a release. Hopefully we can coast in on the effort we put forth in the last release, at least to some extent! :-) Thanks, -john - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Maven Stylus Skin version 1.1
+1 - Fabrice belling...@apache.org On Wed, Jan 7, 2009 at 5:05 PM, Vincent Siveton vincent.sive...@gmail.comwrote: Hi, We solved 1 issue, to comply with the board resolution about Privacy policy page. http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11430styleName=Htmlversion=14872 There are no issue left in JIRA. Staging repo: http://people.apache.org/~vsiveton/staging-repo/http://people.apache.org/%7Evsiveton/staging-repo/ Staging site (need to sync): http://maven.apache.org/skins/maven-stylus-skin-1.1 Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 Cheers, Vincent - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Maven 3.0-alpha-1
+1 - Fabrice belling...@apache.org On Mon, Jan 5, 2009 at 1:32 AM, Jason van Zyl jvan...@sonatype.com wrote: Hi, This is really to get the ball rolling for Maven 3.x. While I have some gracious guinea pigs who are arduously pummeling this code base I wouldn't recommend anyone use this in production. If you want to try it and give feedback that's great, but we have a lot of work we know ourselves that needs to be done. Not trying to discourage anyone from trying it but I honestly wouldn't expect much for a at least a couple more weeks. Over the next few alphas the work will be dominated by bug fixing, regression fixing, general alignment with Maven 2.x so that all known requirements to run Maven 2.x plugins are satisfied, and refactoring to prepare the codebase for the fun stuff of adding new features. There is still a lot of work todo, but by the end of January I think I'll have a good enough idea to layout some tentative beta dates and for GA. I know this by guestimating based on myself, Shane, and Oleg working on this full-time and Benjamin working part-time. We are trying extremely hard to make everything accessible by producing tons of ITs, a specification for POM construction and builds coming off the grid at a very high frequency. I hope that fairly soon into the alpha cycle we can attract Ralph into the mix and soon after that more developers. My hope is that by the time the betas rolls around we have 4-5 people who know the core as well as Shane and I do now, and 7-8 by the time we hit GA. I think from this point I would like to try and eject and alpha every week or two with builds coming off the grid many times a day. Please don't expect too much from the distribution if you happen to download it as we know there are problems and we haven't started optimizing at all yet. Shane and I had to do a release before we went batty so we needed to get the process going. I don't think we are going to attempt to integrate newer build of Maven 3.x into m2e for a couple more alphas so anyone doing embedding work I can tell you that it's not time to integrate yet. So without fanfare, here are the standard bits you're looking for: Issues resolved: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truefixfor=13143pid=10500sorter/field=issuekeysorter/order=DESC Staging repo: http://people.apache.org/builds/maven/3.0-alpha-1/ Distributions: http://people.apache.org/builds/maven/3.0-alpha-1/staging-repo/org/apache/maven/maven-distribution/3.0-alpha-1/ Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 Thanks, Jason -- Jason van Zyl Founder, Apache Maven jason at sonatype dot com -- In short, man creates for himself a new religion of a rational and technical order to justify his work and to be justified in it. -- Jacques Ellul, The Technological Society - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Maven Changes plugin version 2.1
+1! - Fabrice [EMAIL PROTECTED] On Tue, Nov 18, 2008 at 10:57 PM, Olivier Lamy [EMAIL PROTECTED] wrote: Hi, I'd like to release maven-changes-plugin version 2.1. We solved 27 issues : http://jira.codehaus.org/secure/ReleaseNote.jspa?version=14064styleName=HtmlprojectId=11212Create=Create Staging repo: http://people.apache.org/~olamy/staging-repo/http://people.apache.org/%7Eolamy/staging-repo/ Staging site: http://maven.apache.org/plugins/maven-changes-plugin-2.1 (wait sync) 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. -- Olivier - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [vote] Release Maven 2.1.0-M1
+1! - Fabrice [EMAIL PROTECTED] On Mon, Sep 15, 2008 at 11:12 PM, John Casey [EMAIL PROTECTED] wrote: Hi everyone, After fixing 70 issues and spending about 2 months going through release candidate after release candidate, we finally have a stable codebase! To that end, I'd like to put Maven 2.1.0-M1 up for a vote. The release notes are here: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500styleName=Htmlversion=14503 and the staged binary is here: http://people.apache.org/~jdcasey/stage/apache-maven/2.1.0-M1/org/apache/maven/apache-maven/2.1.0-M1http://people.apache.org/%7Ejdcasey/stage/apache-maven/2.1.0-M1/org/apache/maven/apache-maven/2.1.0-M1 This vote will be open for 72h. Please vote +1/+0/-1. Here's my +1. Thanks, -john --- John Casey Developer and PMC Member, Apache Maven (http://maven.apache.org) Member, Apache Software Foundation Blog: http://www.ejlife.net/blogs/buildchimp - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [PLEASE TEST] Maven 2.1.0-M1-RC17
Still works fine for my builds :-) - Fabrice [EMAIL PROTECTED] On Wed, Sep 10, 2008 at 5:32 AM, John Casey [EMAIL PROTECTED] wrote: Hi, I've fixed MNG-3748, where illegal elements in the settings.xml were not triggering build failure. Anyway, this release candidate includes a fix for that issue: http://people.apache.org/~jdcasey/stage/current-maven-RC/http://people.apache.org/%7Ejdcasey/stage/current-maven-RC/ Enjoy, and let me know if you have problems. Thanks, -john --- John Casey Developer and PMC Member, Apache Maven (http://maven.apache.org) Member, Apache Software Foundation Blog: http://www.ejlife.net/blogs/buildchimp - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven 2.0.10-RC4
No more problem - builds fine on my projects. :-) - Fabrice [EMAIL PROTECTED] On Thu, Jul 31, 2008 at 10:50 PM, John Casey [EMAIL PROTECTED] wrote: Hi, I've got a new release candidate for people to try out: http://people.apache.org/~jdcasey/stage/apache-maven/2.0.10-RC4/org/apache/maven/apache-maven/2.0.10-RC4/http://people.apache.org/%7Ejdcasey/stage/apache-maven/2.0.10-RC4/org/apache/maven/apache-maven/2.0.10-RC4/ Major changes: - Bumped wagon version to 1.0-beta-4 - Improved handling of mirror definitions without an id/ element The only outstanding potential issue has something to do with the MJAVADOC-172 and MJAVADOC-194 integration tests, in the maven-javadoc-plugin. I'm unable to even build this plugin on my localhost due to unit test failures (even using Maven 2.0.9), so unfortunately I can't even attempt to figure out what the specific failure is in these cases. Hopefully, RC4 will make it possible to distill a failing test case I can use to fix the issue in the core (if it's in the core). Enjoy. -john -- John Casey Developer, PMC Member - Apache Maven (http://maven.apache.org) Blog: http://www.ejlife.net/blogs/buildchimp/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Release Maven Filtering version 1.0-alpha-1
Yes, +1 ! - Fabrice [EMAIL PROTECTED] On Wed, Jul 30, 2008 at 12:35 AM, Olivier Lamy [EMAIL PROTECTED] wrote: Hi, In preparation of the maven-war-plugin, I'd like to release and promote out of the sandbox the maven-filtering component version 1.0-alpha-1. The goal of this component is to provide a common tool for maven plugins to filtering resources. Staging repo : http://people.apache.org/~olamy/staging-repo/http://people.apache.org/%7Eolamy/staging-repo/ Staging site : http://people.apache.org/~olamy/staging-sites/maven-filtering-1.0-alpha-1/http://people.apache.org/%7Eolamy/staging-sites/maven-filtering-1.0-alpha-1/ Svn tag : https://svn.apache.org/repos/asf/maven/shared/tags/maven-filtering-1.0-alpha-1/ Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 Here my +1. -- Olivier - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Release Maven Project Info Reports Plugin version 2.1 (take 2)
+1 - Fabrice [EMAIL PROTECTED] On Fri, Jul 25, 2008 at 7:45 PM, Vincent Siveton [EMAIL PROTECTED] wrote: Hi, We solved less than 70 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11142styleName=Htmlversion=12621 There are still a couple of issues left in JIRA: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=11142status=1 Staging repo: http://people.apache.org/~vsiveton/staging-repo/http://people.apache.org/%7Evsiveton/staging-repo/ Staging site: http://maven.apache.org/plugins/maven-project-info-reports-plugin-2.1/ Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 Cheers, - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [PLEASE TEST] Maven 2.0.10-RC2
Hi, well, a couple of things: 1- I also had the stack trace issue (but Brett apparently just fixed it in SVN) 2- the following output appears several times in the build log of one of my projects (which I don't have with 2.0.9): [WARNING] POM for 'bcel:bcel:pom:5.1:compile' is invalid. It will be ignored for artifact resolution. Reason: Parse error reading POM. Reason: Unrecognised association: 'groupId' (position: START_TAG seen ...dependencies\ngroupId... @7:14) for project bcel:bcel at C:\JIP\home\.m2\repository\bcel\bcel\5.1\bcel-5.1.pom It is actually printed: - twice in [resources:resources] phase - 4 times in [resources:testResources] phase - 4 times in [compiler:testCompile] phase - 4 times in [surefire:test] phase - 4 times in [assembly:attached] phase, in which I also get: [WARNING] Attempting to build MavenProject instance for Artifact (bcel:bcel:5.1) of type: jar; constructing POM artifact instead. The POM for BCEL 5.1 is indeed invalid on Maven repo, which I had never noticed before. So this is a good point (I created MEV-592). However, printing this log 18 times is a bit violent, isn't it? :-) Appart from that, all my projects build fine. - Fabrice [EMAIL PROTECTED] On Wed, Jul 23, 2008 at 11:03 PM, John Casey [EMAIL PROTECTED] wrote: Hello everyone, Okay, I think we've got all of the problems with RC1 sorted out, and the integration tests are finally passing again. So, without further ado, let's get RC2 out there for testing! You can find the distribution here: http://people.apache.org/~jdcasey/stage/apache-maven/2.0.10-RC2http://people.apache.org/%7Ejdcasey/stage/apache-maven/2.0.10-RC2 (In fact, the tarballs/zipfile are here: http://people.apache.org/~jdcasey/stage/apache-maven/2.0.10-RC2/org/apache/maven/apache-maven/2.0.10-RC2/http://people.apache.org/%7Ejdcasey/stage/apache-maven/2.0.10-RC2/org/apache/maven/apache-maven/2.0.10-RC2/ ) Happy testing! Again, please let me know if you find any problems, and I'll get them fixed ASAP. Thanks, -john -- John Casey Developer, PMC Member - Apache Maven (http://maven.apache.org) Blog: http://www.ejlife.net/blogs/buildchimp/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Commit privs for Shane Isbell
+1 - Fabrice [EMAIL PROTECTED] On Thu, Jul 24, 2008 at 7:41 PM, Hervé BOUTEMY [EMAIL PROTECTED] wrote: +1 Hervé Le mercredi 23 juillet 2008, Jason van Zyl a écrit : Hi, Shane has been been working on NMaven for a couple years now, he's worked on the new maven-toolchain, has recently done a huge amount of work on cleaning up the project builder in the sandbox, and has some PGP tools that he would like to contribute. So overall given the time he's been around in the community and the the massive amount of work he's done lately I propose that we give him commit privs. Primarily because I don't want to merge his branch of 2.1 :-) +1 Thanks, Jason -- Jason van Zyl Founder, Apache Maven jason at sonatype dot com -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Commit Privs for Oleg Gusakov
+1 - Fabrice [EMAIL PROTECTED] On Fri, Jun 13, 2008 at 2:20 AM, Jason van Zyl [EMAIL PROTECTED] wrote: Hi, Oleg has been contributing patches to the artifact mechanism for well over 6 months and has gone through some steps to look at graph-based resolution, and subsequently moved on to the boolean solver method of performing version selection in artifact resolution. This is the method that p2 is using in Eclipse, and Daniel Le Berre (the author of the SAT4J library we are using) has been kind enough to introduce us to some of the Linux distro folks who are using the same methods to resolve ranges in their package managers which is not an easy problem. Oleg has been studying the math and working with Daniel and I believe has provided us with a path to world-class artifact resolution. We need to get rid of what we have because there is simply no way to do ranges correctly without some form of solver, it's just impossible and this is generally accepted by the community of people dealing with dependency and packaging problems. I've been applying Oleg's patches for a long time, and I would like to give him commit access to continue his work which I believe is part of the future for Maven's artifact resolution mechanism. +1 Thanks, Jason -- Jason van Zyl Founder, Apache Maven jason at sonatype dot com -- We know what we are, but know not what we may be. -- Shakespeare - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Release Maven Checkstyle plugin version 2.2
+1! Thanks, :-) -- Fabrice [EMAIL PROTECTED] On Sun, Jun 1, 2008 at 12:17 AM, Dennis Lundberg [EMAIL PROTECTED] wrote: Hi, It's been over two years since the last release, so let's do this :-) We solved 31 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11127styleName=Htmlversion=12489 There are still a couple of issues left in JIRA: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=11127status=1 Staging repo: http://people.apache.org/~dennisl/staging-repository/http://people.apache.org/%7Edennisl/staging-repository/ Staging site: http://maven.apache.org/plugins/maven-checkstyle-plugin-2.2/ Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 -- Dennis Lundberg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[OT] Coloring diffs in GMail with GreaseMonkey
Hi guys, I've developed a GreaseMonkey script that colors the mails sent by SVN to make it easier to read the diff format (inspired by a Thunderbird extension: http://code.google.com/p/colorediffs/). As I know some of you use GMail and potentially Firefox as well, I thought you might like trying it :-) It's here: http://userscripts.org/scripts/show/26684 It's a first shot but it works well for me - at least for Maven and Archiva commits, and other OSS projects I work on. I noticed that it does not work properly with MOJO commits though... Feel free to give any feedback! Cheers! -- Fabrice - [EMAIL PROTECTED] -
Re: [VOTE] Release Maven Changes Plugin version 2.0
+1 -- Fabrice - [EMAIL PROTECTED] - On Sun, Apr 13, 2008 at 5:59 PM, Dennis Lundberg [EMAIL PROTECTED] wrote: Hi, We solved 17 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11212styleName=Htmlversion=13722 There are still a couple of issues left in JIRA: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=11212status=1 Staging repo: http://people.apache.org/~dennisl/staging-repository/http://people.apache.org/%7Edennisl/staging-repository/ Staging site (when it has synced): http://maven.apache.org/plugins/maven-changes-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 -- Dennis Lundberg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Maven 2.0.9
Just built my projects with this fresh 2.0.9, and everything went fine, so
here's my +1
Thanks Brian!
Cheers
--
Fabrice
- [EMAIL PROTECTED] -
On Mon, Apr 7, 2008 at 6:42 PM, Brian E. Fox [EMAIL PROTECTED]
wrote:
Time to vote on the final Maven 2.0.9 Release. We went through 8 Release
Candidates and fixed all know regressions from 2.0.8 to 2.0.9 during
that time. Note that there were no source changes between RC8 and this
final build.
Release is staged at:
http://people.apache.org/~brianf/stage-2.0.9http://people.apache.org/%7Ebrianf/stage-2.0.9
Binaries are here:
http://people.apache.org/~brianf/stage-2.0.9/org/apache/maven/apache-mav
en/2.0.9/http://people.apache.org/%7Ebrianf/stage-2.0.9/org/apache/maven/apache-maven/2.0.9/
List of issues fixed:
Release Notes - Maven 2 - Version 2.0.9
** Bug
* [MNG-1412] - dependency sorting in classpath
* [MNG-1914] - Wrong url in error message when using a mirror
* [MNG-2123] - NullPointerException when a dependency uses version
range and another uses an actual version incompatible with that range
* [MNG-2145] - Plugins' dependencies are not always checked
* [MNG-2178] - incorrect M2_HOME guess in mvn.bat
* [MNG-2234] - activeProfile in ~/.m2/settings.xml is ignored when
profiles section is missing or empty
* [MNG-2339] - ${project.*} are interpreted in the wrong place
* [MNG-2744] - checksum comparison should be case-insensitive
* [MNG-2809] - Can't activate a profile by checking for the presence
of a file in ${user.home}
* [MNG-2848] - Environment variables in profile activation not
working
* [MNG-2861] - NullPointerException in DefaultArtifactCollector for
relocated resolvedArtifacts with different version ranges and available
versions.
* [MNG-2925] - NullPointerException in PluginDescriptor.getMojo() if
there's no mojo in pom.xml
* [MNG-2928] - Null pointer exeception when introducing version
range [major.minor.build-SNAPSHOT,)
* [MNG-2972] - Ignores version of plugin dependency specified in my
pom
* [MNG-3086] - NullPointerException in
ResolutionNode.getTrail(ResolutionNode.java:136)
* [MNG-3099] - Profiles ignored when working with non-projects (such
as archetype:create)
* [MNG-3111] - Classpath order incorrect
* [MNG-3156] - NullPointerException with mvn dependency:sources
* [MNG-3221] - Infinite loop in DefaultLifecycleExecutor
* [MNG-3259] - Regression: Maven drops dependencies in multi-module
build
* [MNG-3286] - execution.inherited field is ignored
* [MNG-3288] - Invalid systemPath allows build to continue--failing
in later phase.
* [MNG-3296] - mvn.bat looses error code on windows NT type
platforms
* [MNG-3310] - JAVACMD set incorrectly when JAVA_HOME is not set
* [MNG-3316] - Barfs at attribues named .*encoding
* [MNG-3354] - mvn.bat incorrectly detects OS on Windows NT or XP
with Novell login
* [MNG-3355] - CLONE -${pom.build.sourceDirectory} and
${pom.build.testSourceDirectory} no longer recognized
* [MNG-3365] - Remove trailing-backslashes from M2_HOME in mvn.bat
* [MNG-3394] - Plugin versions inherited via pluginManagement
cannot be overriden by build.plugins section of sub modules
* [MNG-3396] - Managed versions dont affect over constrained ranges
* [MNG-3400] - MavenProject is not extensible
* [MNG-3405] - Checking for updates from repository logging should
not display if WagonManager is offline
* [MNG-3410] - Managed versions in plugins are not considered when
using them
* [MNG-3415] - Transfer errors cause junk metadata in the local repo
* [MNG-3426] - regression : dependency in plugin configuration
doesn't override plugin classpath
* [MNG-3430] - Toolchain doesn't match Toolchain extensions
* [MNG-3431] - Pom Extensions not supported for Toolchains
* [MNG-3439] - incorrect child dependency selected when parent is
not selected
* [MNG-3441] - Maven should always retrieve metadata to be updated
from the deployment repository
* [MNG-3460] - org.apache.maven.profiles.DefaultProfileManagerTest
fails if you use a different local repo
* [MNG-3464] - maven-toolchains missing from final binary.. need to
update the assembly
* [MNG-3473] - site generation with 2.0.9 and plugin:report (2.4
ONLY) is broken
* [MNG-3484] - INT_MAVEN_OPTS are not quoted in mvnDebug which
causes issues on some shells
* [MNG-3485] - unable to override wagons that are bundled with a
different version via extensions
* [MNG-3494] - local pom dependencies should get injected before
inherited dependencies
* [MNG-3495] - NPE at
org.apache.maven.wagon.repository.Repository.hashCode(Repository.java:24
1)
** Improvement
* [MNG-428] - Japanese message resource
* [MNG-2881] - Improve logging when downloading snapshots in offline
mode
* [MNG-3279] - Support Exception Chaining for
Re: [vote] Release Archiva 1.0.2
+1, everything's fine. Thx Brett! -- Fabrice - [EMAIL PROTECTED] - On Thu, Apr 3, 2008 at 7:23 PM, Brett Porter [EMAIL PROTECTED] wrote: Hi The Archiva 1.0.2 release candidate has been staged. This release includes 41 fixes. You can take a look at the release notes here: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10980styleName=Htmlversion=14052 or http://people.apache.org/~brett/staged-sites/archiva/1.0.2/release-notes.htmlhttp://people.apache.org/%7Ebrett/staged-sites/archiva/1.0.2/release-notes.html The whole staged site is here: http://people.apache.org/~brett/staged-sites/archiva/1.0.2/http://people.apache.org/%7Ebrett/staged-sites/archiva/1.0.2/ While the binaries, including the sources, signatures and checksums, can be downloaded here: http://people.apache.org/builds/maven/archiva/1.0.2/ Everyone is encouraged to vote and give their feedback. [ ] +1 Release it! [ ] 0 [ ] -1 Don't release it, because... The vote will be open for 72 hours. Thanks, Brett -- Brett Porter [EMAIL PROTECTED] http://blogs.exist.com/bporter/
Re: proposed structural change to the source repo
Nice, +1 :-) -- Fabrice - [EMAIL PROTECTED] - On Thu, Mar 27, 2008 at 9:36 PM, Brett Porter [EMAIL PROTECTED] wrote: Since we're moving tomorrow anyway, I'd like to propose making the following change subsequently: /archiva /archiva-docs /archiva-jetty /archiva-modules .. current structure under here This means we can retain the one release, one build - but all the Java code sites under -modules. This allows us to put all the Java code reporting in there, and not pollute the -docs and the distro with it. I think more changes can be made to the structure of -modules, but that can be done at a later time. Any objections? - Brett -- Brett Porter [EMAIL PROTECTED] http://blogs.exist.com/bporter/
Re: [pre vote take 3] 2.0.9-RC3
Tested on my projects, works fine. Here's my +1 for RC4. -- Fabrice - [EMAIL PROTECTED] - On Thu, Mar 27, 2008 at 4:26 AM, Brian E. Fox [EMAIL PROTECTED] wrote: Sejal, James, could you try with this informal RC? http://people.apache.org/~brianf/2.0.9/http://people.apache.org/%7Ebrianf/2.0.9/(still uploading, give a few mins) This should get you past MNG-3119 so we can see if everything else is good before cutting the RC4 for real. Thanks for testing. --Brian
Re: Developing Archiva in Eclipse with Q4E
Nice, I'll try this asap. Thx! -- Fabrice - [EMAIL PROTECTED] - On Thu, Mar 20, 2008 at 2:29 AM, Brett Porter [EMAIL PROTECTED] wrote: I thought this might be of interest to some people here: http://cwiki.apache.org/confluence/display/ARCHIVA/Setting+up+Archiva+in+Eclipse+with+Q4E Cheers, Brett -- Brett Porter [EMAIL PROTECTED] http://blogs.exist.com/bporter/
Re: [VOTE] Release Maven Eclipse plugin version 2.5
I've been using the snapshot for quite a while, and it works very well. So here's my +1! Thanks Arnaud :-) -- Fabrice - [EMAIL PROTECTED] - On Sat, Mar 15, 2008 at 1:30 AM, Arnaud HERITIER [EMAIL PROTECTED] wrote: Hi, We solved more than 50 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?version=13593styleName=HtmlprojectId=11133 Important changes are : - Add support for WTP 2.0 - Add support for MyEclipse - Improve RAD6 support - Posibility to discover projects in the eclipse workspace And I certainly forgot several others. There are still a lot of issues left in JIRA but we applied all patches which were usable : http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=11133status=1 Staging repo: http://people.apache.org/~aheritier/stage/repo/http://people.apache.org/%7Eaheritier/stage/repo/ Staging site: Not yet deployed. I'm looking for a sftp client for leopard Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 -- .. Arnaud HERITIER .. OCTO Technology - aheritier AT octo DOT com www.octo.com | blog.octo.com .. ASF - aheritier AT apache DOT org www.apache.org | maven.apache.org ... - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Vote] Release maven-javadoc-plugin 2.4
Same here, +1! -- Fabrice - [EMAIL PROTECTED] - On Sun, Mar 9, 2008 at 9:54 AM, Dan Tran [EMAIL PROTECTED] wrote: +1, have been using 2.4 SNAPSHOT for a long time now Thanks for pushing this out. -D On Sat, Mar 8, 2008 at 3:13 PM, Brian E. Fox [EMAIL PROTECTED] wrote: I consider 2.3 totally and horribly broken, thus it is urgent to get 2.4 out asap. After that we can move to 2.5 as soon as someone has time to apply the patches, test and release. -Original Message- From: Benjamin Bentmann [mailto:[EMAIL PROTECTED] Sent: Saturday, March 08, 2008 5:52 PM To: Maven Developers List Subject: Re: [Vote] Release maven-javadoc-plugin 2.4 [MJAVADOC-154] - Bump to plexus-utils:1.4.6 Hm, this task is linked to an issue about a defect in BourneShell. Another BourneShell defect has been fixed in PLXUTILS-54 for plexus-utils:1.4.9. Maybe worth to update once again to latest version? Also, maven-javadoc-plugin:2.4 is known to ignore generated sources in contrast to previous versions (MJAVADOC-168). Really bump fix to next version and break now? If the release is rolled back, the patch from MJAVADOC-162 might be added as well. Benjamin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [vote] Release Maven Shade plugin 1.0
+1 Fabrice On Sun, Mar 2, 2008 at 4:20 AM, Brett Porter [EMAIL PROTECTED] wrote: Hi, The Shade plugin is ready to be released. This is needed for the 2.0.9 release as well. We solved 6 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11540styleName=Htmlversion=13994 The remaining issues in JIRA are feature requests. Staging repo: http://people.apache.org/~brett/staged-releases/org/apache/maven/plugins/maven-shade-plugin/1.0/http://people.apache.org/%7Ebrett/staged-releases/org/apache/maven/plugins/maven-shade-plugin/1.0/ Staging site: http://maven.apache.org/plugins/maven-shade-plugin/staging/ Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 -- Brett Porter [EMAIL PROTECTED] http://blogs.exist.com/bporter/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Fabrice - [EMAIL PROTECTED] -
Re: [VOTE] Request Archiva graduation to a TLP
+1 -- Fabrice - [EMAIL PROTECTED] - On Thu, Feb 28, 2008 at 11:11 AM, Maria Odea Ching [EMAIL PROTECTED] wrote: Hi Everyone, As discussed in the Archiva dev list, below is the proposal for the Archiva TLP. Please vote on whether to make this proposal a formal request to the Maven PMC to apply for graduation. [ ] +1 [ ] 0 [ ] -1 Thanks, Deng Establish the Apache Archiva Project WHEREAS, the Board of Directors deems it to be in the best interests of the Foundation and consistent with the Foundation's purpose to establish a Project Management Committee charged with the creation and maintenance of open-source software related to the management of build repositories and to the storage and retrieval of the build system artifacts residing in them. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the Apache Archiva PMC, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Archiva PMC be and hereby is responsible for the creation and maintenance of software related to the management of build repositories and to the storage and retrieval of the build system artifacts residing in them based on software licensed to the Foundation; and be it further RESOLVED, that the office of Vice President, Apache Archiva be and hereby is created, the person holding such office to serve at the direction of the Board of Directors as the chair of the Apache Archiva PMC, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Archiva PMC; and be it further RESOLVED, that the persons listed immediately below be and hereby are appointed to serve as the initial members of the Apache Archiva PMC: Fabrice Bellingard ([EMAIL PROTECTED]) Maria Odea Ching ([EMAIL PROTECTED]) Nicolas de Loof ([EMAIL PROTECTED]) Joakim Erdfelt ([EMAIL PROTECTED]) Arnaud Heritier ([EMAIL PROTECTED]) Dennis Lundberg ([EMAIL PROTECTED]) Jesse McConnell ([EMAIL PROTECTED]) Brett Porter ([EMAIL PROTECTED]) Edwin Punzalan ([EMAIL PROTECTED]) Carlos Sanchez ([EMAIL PROTECTED]) Wendy Smoak ([EMAIL PROTECTED]) John Tolentino ([EMAIL PROTECTED]) Emmanuel Venisse ([EMAIL PROTECTED]) NOW, THEREFORE, BE IT FURTHER RESOLVED, that Maria Odea Ching be appointed to the office of Vice President, Apache Archiva, to serve in accordance with and subject to the direction of the Board of Directors and the Bylaws of the Foundation until death, resignation, retirement, removal or disqualification, or until a successor is appointed; and be it further RESOLVED, that the initial Apache Archiva PMC be and hereby is tasked with the creation of a set of bylaws intended to encourage open development and increased participation in the Apache Archiva Project; and be it further RESOLVED, that the initial Apache Archiva PMC be and hereby is tasked with the migration and rationalization of the Apache Maven PMC Archiva subproject; and be it further RESOLVED, that all responsibility pertaining to the Maven Archiva sub-project and encumbered upon the Apache Maven PMC are hereafter discharged.
Re: [discuss] Archiva TLP proposal
On Wed, Feb 27, 2008 at 9:46 AM, Brett Porter [EMAIL PROTECTED] wrote: I think this is a great description for the front page - want to update the site? :) Ok :-) I reworked it a bit, and updated the xdoc front page on SVN. Cheers, Fabrice For the charter - it is really about a broad objective rather than a feature list. I like Deng's description (for the inclusion of the word repository). Cheers, Brett -- Brett Porter [EMAIL PROTECTED] http://blogs.exist.com/bporter/ -- Fabrice - [EMAIL PROTECTED] -
Re: [vote] Paul Gier as Maven committer
+1 -- Fabrice - [EMAIL PROTECTED] - On Thu, Feb 28, 2008 at 8:21 PM, John Casey [EMAIL PROTECTED] wrote: I'd like to propose giving commit access to Paul Gier. He's been instrumental in the recent push to release the assembly plugin, and I see his work (debugging some issues, patches for other issues) all over JIRA. Not to mention he's pretty active on IRC, and he's helping people out on the users list as well. IMO, we need more people as involved as Paul has been, to keep Maven humming along. Please vote. 72h +1/+0/-1 Here's my +1. -john --- John Casey Committer and PMC Member, Apache Maven mail: jdcasey at commonjava dot org blog: http://www.ejlife.net/blogs/john rss: http://feeds.feedburner.com/ejlife/john
Re: [discuss] Archiva TLP proposal
On Mon, Feb 25, 2008 at 3:04 AM, Brett Porter [EMAIL PROTECTED] wrote: Ok, seems there is some interest in putting together a proposal. I'm going to follow the same format we used at Continuum last month. Before we continue to vote on a proposal to send to the board, we need to: 1) Decide on a charter for the project. the creation and maintenance of open-source software related to ... Here's my try :-) The Apache Archiva project is an extensible repository management software that helps taking care of your own personal or enterprise-wide artifact repository. It offers several capabilities, amongst which remote repository proxying, build artifacts storage, delivery and indexing, extensible scanning functionality, and many more. 2) Nominate a chair to put in the proposal I would like to nominate Deng as the chair of the project. I think the work she has done in making sure releases happened consistently, answering users questions, and following up contributions has contributed a lot to the growth of the project recently. Are there any other nominations or seconds? Agree, Deng has done a really good job around Archiva, which makes her an excellent candidate for the chair of the projet. :-) Joakim has also been involved a lot, and could therefore also be a good candidate, IMO. 3) Agree on the initial committers and PMC list I have the current committers list as: Maria Odea Ching ([EMAIL PROTECTED]) Fabrice Bellingard ([EMAIL PROTECTED]) Nicolas de Loof ([EMAIL PROTECTED]) Joakim Erdfelt ([EMAIL PROTECTED]) Arnaud Heritier ([EMAIL PROTECTED]) Dennis Lundberg ([EMAIL PROTECTED]) Jesse McConnell ([EMAIL PROTECTED]) Brett Porter ([EMAIL PROTECTED]) Edwin Punzalan ([EMAIL PROTECTED]) Carlos Sanchez ([EMAIL PROTECTED]) Wendy Smoak ([EMAIL PROTECTED]) John Tolentino ([EMAIL PROTECTED]) Emmanuel Venisse ([EMAIL PROTECTED]) +1 Cheers, Brett Thanks for starting this, Brett. Fabrice
Re: [vote] Release maven-assembly-plugin 2.2-beta-2 and maven-repository-builder 1.0-alpha-2
On Fri, Feb 22, 2008 at 11:46 AM, Fabrice Bellingard [EMAIL PROTECTED]
wrote:
+1
I still have some critical bugs with the filtering, but let's release this
one. I'll try to look into that this w-e, and see how to use the shared
filtering component that Olivier Lamy has started to develop.
Well, I spoke too fast... I've tested your staged version and it seems that
everything works fine, even with the filtering I'm doing on my projects.
So definitely a big +1!
Fabrice
Fabrice
On Thu, Feb 21, 2008 at 8:01 PM, John Casey [EMAIL PROTECTED]
wrote:
Hi all,
I'd like to propose that we release both the assembly plugin and one of
its shared-component dependencies: maven-repository-builder. See below for
more information on what's included in these releases. I have two staging
repositories for these projects:
maven-assembly-plugin:
http://people.apache.org/~jdcasey/stage/maven-assembly-plugin/2.2-beta-2/http://people.apache.org/%7Ejdcasey/stage/maven-assembly-plugin/2.2-beta-2/
maven-repository-builder:
http://people.apache.org/~jdcasey/stage/maven-repository-builder/1.0-alpha-2/http://people.apache.org/%7Ejdcasey/stage/maven-repository-builder/1.0-alpha-2/
You can try them out using the following settings.xml snippet:
profiles
profile
idmaven-assembly-plugin.stage/id
repositories
repository
idmrb.stage/id
url
http://people.apache.org/~jdcasey/stage/maven-repository-builder/1.0-alpha-2http://people.apache.org/%7Ejdcasey/stage/maven-repository-builder/1.0-alpha-2
/url
snapshots
enabledfalse/enabled
/snapshots
/repository
repository
idmap.stage/id
url
http://people.apache.org/~jdcasey/stage/maven-assembly-plugin/2.2-beta-2http://people.apache.org/%7Ejdcasey/stage/maven-assembly-plugin/2.2-beta-2
/url
snapshots
enabledfalse/enabled
/snapshots
/repository
/repositories
pluginRepositories
pluginRepository
idmap.stage/id
url
http://people.apache.org/~jdcasey/stage/maven-assembly-plugin/2.2-beta-2http://people.apache.org/%7Ejdcasey/stage/maven-assembly-plugin/2.2-beta-2
/url
snapshots
enabledfalse/enabled
/snapshots
/pluginRepository
/pluginRepositories
/profile
/profiles
activeProfiles
activeProfilemaven-assembly-plugin.stage/activeProfile
/activeProfiles
Let the voting begin! +1/+0/-1, 72 hrs.
Thanks,
John
--
The main improvement in the repository builder is inclusion of parent
POMs, and some improvements to snapshot handling (though this may not be
complete yet). I'm attaching the SVN log for more information about these
changes.
As for the assembly plugin, there have been quite a few changes in the
last nine months or so:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11126styleName=Htmlversion=14027
Release Notes - Maven 2.x Assembly Plugin - Version 2.2-beta-2
** Bug
* [MASSEMBLY-121] - Custom manifest attributres are ignored.
* [MASSEMBLY-129] - BaseDirectory Ignored When Including a
Repository
* [MASSEMBLY-156] - appendAssemblyId cannot be false
* [MASSEMBLY-162] - In a multiproject environment, assembly takes
wrong dependencies
* [MASSEMBLY-163] - In a multiproject environment Assembly causes
many unneded rebuilds
* [MASSEMBLY-178] - filtering doesn't read filter files
* [MASSEMBLY-179] - Assembled jar includes artifact names in path
* [MASSEMBLY-180] - A bug in artifact filtering (
maven-common-artifact-filters )
* [MASSEMBLY-183] - assembly:attached does not work with filter-
ERROR: Cannot override read-only parameter
* [MASSEMBLY-184] - components are not interpolated - i.e.,
${params} are not substituted
* [MASSEMBLY-188] - manifestEntries are not set in resulting jar
* [MASSEMBLY-189] - plugin not correctly interpolating POM variables
like project.build.directory
* [MASSEMBLY-194] - unnecessary dependency expansion regression
* [MASSEMBLY-195] - unpackOptions ignored
* [MASSEMBLY-197] - 2.2-beta-1 regression, project artifact no
longer included in
* [MASSEMBLY-208] - Assembly plugin does not resolve version ranges
correctly
* [MASSEMBLY-210] - repository does not include the parent pom
* [MASSEMBLY-212] - Assembly Descriptor Schemas (XSD) have wrong
targetNamespace
* [MASSEMBLY-214] - java.lang.NullPointerException: version was null
for junit:junit
* [MASSEMBLY-221] - Filtering doesn't work when a file matches both
a fileSet and a file
* [MASSEMBLY-222] - 2.2-beta-1 regression in assembly descriptor
interpolation
* [MASSEMBLY-223] - 2-nd exclude element of
dependencySets:excludes doesn't work
Re: [Result] [vote] Benjamin Bentmann as Maven committer
Welcome on board Benjamin :-) Fabrice On Fri, Feb 22, 2008 at 11:12 AM, Lukas Theussl [EMAIL PROTECTED] wrote: 72h have passed, lots of votes, I hope I won't miss anybody: PMC: J. van Zyl, V. Siveton, O. Lamy, J. Casey, B. Porter, B. Fox, D. Lundberg, A. Heritier, L. Theussl Committers: R. Goers, M. Kleint, R. Pieroni, D. Fabulich, R. Thakur, F. Bellingard, N. de Loof, M. Talevi, A. Williams Welcome Benjamin! -Lukas Lukas Theussl wrote: I'd like to propose giving commit access to Benjamin. During the last few months, he has provided patches in so many areas of Maven that I can't list them all here (various plugins, surefire, doxia,...), including documentation and translations, and he has not been afraid to actively discuss things on the dev list. I think he would make a great addition to our team. +1 -Lukas - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [vote] Release maven-assembly-plugin 2.2-beta-2 and maven-repository-builder 1.0-alpha-2
+1
I still have some critical bugs with the filtering, but let's release this
one. I'll try to look into that this w-e, and see how to use the shared
filtering component that Olivier Lamy has started to develop.
Fabrice
On Thu, Feb 21, 2008 at 8:01 PM, John Casey [EMAIL PROTECTED] wrote:
Hi all,
I'd like to propose that we release both the assembly plugin and one of
its shared-component dependencies: maven-repository-builder. See below for
more information on what's included in these releases. I have two staging
repositories for these projects:
maven-assembly-plugin:
http://people.apache.org/~jdcasey/stage/maven-assembly-plugin/2.2-beta-2/http://people.apache.org/%7Ejdcasey/stage/maven-assembly-plugin/2.2-beta-2/
maven-repository-builder:
http://people.apache.org/~jdcasey/stage/maven-repository-builder/1.0-alpha-2/http://people.apache.org/%7Ejdcasey/stage/maven-repository-builder/1.0-alpha-2/
You can try them out using the following settings.xml snippet:
profiles
profile
idmaven-assembly-plugin.stage/id
repositories
repository
idmrb.stage/id
url
http://people.apache.org/~jdcasey/stage/maven-repository-builder/1.0-alpha-2http://people.apache.org/%7Ejdcasey/stage/maven-repository-builder/1.0-alpha-2
/url
snapshots
enabledfalse/enabled
/snapshots
/repository
repository
idmap.stage/id
url
http://people.apache.org/~jdcasey/stage/maven-assembly-plugin/2.2-beta-2http://people.apache.org/%7Ejdcasey/stage/maven-assembly-plugin/2.2-beta-2
/url
snapshots
enabledfalse/enabled
/snapshots
/repository
/repositories
pluginRepositories
pluginRepository
idmap.stage/id
url
http://people.apache.org/~jdcasey/stage/maven-assembly-plugin/2.2-beta-2http://people.apache.org/%7Ejdcasey/stage/maven-assembly-plugin/2.2-beta-2
/url
snapshots
enabledfalse/enabled
/snapshots
/pluginRepository
/pluginRepositories
/profile
/profiles
activeProfiles
activeProfilemaven-assembly-plugin.stage/activeProfile
/activeProfiles
Let the voting begin! +1/+0/-1, 72 hrs.
Thanks,
John
--
The main improvement in the repository builder is inclusion of parent
POMs, and some improvements to snapshot handling (though this may not be
complete yet). I'm attaching the SVN log for more information about these
changes.
As for the assembly plugin, there have been quite a few changes in the
last nine months or so:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11126styleName=Htmlversion=14027
Release Notes - Maven 2.x Assembly Plugin - Version 2.2-beta-2
** Bug
* [MASSEMBLY-121] - Custom manifest attributres are ignored.
* [MASSEMBLY-129] - BaseDirectory Ignored When Including a Repository
* [MASSEMBLY-156] - appendAssemblyId cannot be false
* [MASSEMBLY-162] - In a multiproject environment, assembly takes
wrong dependencies
* [MASSEMBLY-163] - In a multiproject environment Assembly causes many
unneded rebuilds
* [MASSEMBLY-178] - filtering doesn't read filter files
* [MASSEMBLY-179] - Assembled jar includes artifact names in path
* [MASSEMBLY-180] - A bug in artifact filtering (
maven-common-artifact-filters )
* [MASSEMBLY-183] - assembly:attached does not work with filter-
ERROR: Cannot override read-only parameter
* [MASSEMBLY-184] - components are not interpolated - i.e., ${params}
are not substituted
* [MASSEMBLY-188] - manifestEntries are not set in resulting jar
* [MASSEMBLY-189] - plugin not correctly interpolating POM variables
like project.build.directory
* [MASSEMBLY-194] - unnecessary dependency expansion regression
* [MASSEMBLY-195] - unpackOptions ignored
* [MASSEMBLY-197] - 2.2-beta-1 regression, project artifact no longer
included in
* [MASSEMBLY-208] - Assembly plugin does not resolve version ranges
correctly
* [MASSEMBLY-210] - repository does not include the parent pom
* [MASSEMBLY-212] - Assembly Descriptor Schemas (XSD) have wrong
targetNamespace
* [MASSEMBLY-214] - java.lang.NullPointerException: version was null
for junit:junit
* [MASSEMBLY-221] - Filtering doesn't work when a file matches both a
fileSet and a file
* [MASSEMBLY-222] - 2.2-beta-1 regression in assembly descriptor
interpolation
* [MASSEMBLY-223] - 2-nd exclude element of
dependencySets:excludes doesn't work
* [MASSEMBLY-225] - Not a v4.0.0 POM
* [MASSEMBLY-226] - Filters as read-only parameter can break the
assembly build of a multi-module project
* [MASSEMBLY-232] - NPE - MASSEMBLY-222 fix broken?
* [MASSEMBLY-233] - Custom ContainerDescriptorHandler integration
tests don't work in Maven 2.0.7
* [MASSEMBLY-234] - Artifacts not deployed
* [MASSEMBLY-235] - dependencySet
Re: Maven Filtering component
Hi Olivier, Sounds good! I'll try to look into that this w-e, to see how to use it in the assembly plugin, which suffers from lots of filtering issues. Fabrice On Tue, Feb 19, 2008 at 10:17 AM, Olivier Lamy [EMAIL PROTECTED] wrote: Hi, As you know some plugins made some filtering base on the code coming from the maven-resources-plugin. This means there are some copy and paste from the resources plugin source to other plugins. To prevent this, the code from the resources plugin has been put in a plexus component (currently in shared sandbox [1]). A documentation has been started [2]. It has been integrated in the maven-war-plugin trunk. Before calling a vote on a first alpha-1 release, I'd like to have some comments/thoughts on it. The final goal of this component should be : using it in all plugins which need filtering. Thanks, -- Olivier [1] : https://svn.apache.org/repos/asf/maven/sandbox/trunk/shared/maven-filtering/ [2] : http://people.apache.org/~olamy/staging-sites/maven-filtering/http://people.apache.org/%7Eolamy/staging-sites/maven-filtering/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Plan to migrate towards Spring?
On Feb 19, 2008 8:52 AM, nicolas de loof [EMAIL PROTECTED] wrote: 2008/2/18, Joakim Erdfelt [EMAIL PROTECTED]: +1000 : I was never very confortable with plexus and lack of documentation on available components. Definitely the same. Moving towards Spring will help new comers to get started faster with developing Archiva. So here's my +1 for moving toward Spring and any other component/techno that is easier to use for developing (like the commons-*, quartz, ...) or that makes Archiva easier to maintain in the long term (JPA, ...). Concerning the web UI, IMHO, moving to Struts 2 would be a good option and a wiser decision, as getting rid of Plexus will already require quite some efforts. Fabrice
Re: [vote] Benjamin Bentmann as Maven committer
+1 Fabrice On Feb 18, 2008 6:38 PM, Lukas Theussl [EMAIL PROTECTED] wrote: I'd like to propose giving commit access to Benjamin. During the last few months, he has provided patches in so many areas of Maven that I can't list them all here (various plugins, surefire, doxia,...), including documentation and translations, and he has not been afraid to actively discuss things on the dev list. I think he would make a great addition to our team. +1 -Lukas - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Release Maven Surefire version 2.4.2
+1 Fabrice On Feb 16, 2008 12:51 AM, Dan Fabulich [EMAIL PROTECTED] wrote: As you might expect, all the good bugs were found in 2.4.1 [looks like some folks were waiting for SP1 to start testing... ;-)] We solved 5 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10541styleName=Htmlversion=14062 There are still 44 issues left in JIRA: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=10541status=1 Staging repo: http://people.apache.org/~dfabulich/staging-repo/http://people.apache.org/%7Edfabulich/staging-repo/ Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Archiva 1.1 Roadmap
Nicolas, concerning your maven managed repository: are you currently really doing that with archiva? It seems indeed interesting, as it simplifies the configuration of the settings.xml file. However, I have a couple of questions: - this means that this maven repository duplicates every artifact handled in your other managed repositories, right? So when you browse artifacts in Archiva, you see managed artifacts twice, don't you? - do you use the same principle for snapshots repositories? I mean, metadata files would conflict with release repositories, so you need another virtual repository for snapshots. Fabrice On Feb 4, 2008 9:38 AM, nicolas de loof [EMAIL PROTECTED] wrote: Early version of archiva had on admin menu a sync repository entry. Not sure if the original idea was to manage a classical rsync-like miror or to isolate local cache for remote proxied repositories. I would suggest some virtual repository A simple example is my corporate use case : many user don't know maven well and have no idea what a repository is (and how to configure), so we have configured settings.xml to mirror all common repositories to the archiva instance : http://server/archiva/repository/maven The maven managed repository is an aggregate of proxied (central, java.net, jboss, ...) and managed ones : corporate builds, restricted jars (SUN apis, oracle driver) and sources bundles (missing in public repos) This repository, declared in archiva configuration as managed is NOT the one we have to manage ! It only is a facade to other managed and proxied repositories. Nico. One item I wanted to single out is the separation between managed repositories used for publishing and those used for caching artifacts from remote repositories. I don't think it makes much sense to have a managed repository that can do both. a big +1 here :) a lot of people has been confused over this especially when there are quite a handful of repositories being managed. This separation would allow us to have: * Provide indexing, browsing and search only for publishing (See foot note) * RSS feeds for new artifacts in published repositories. Foot note: Allowing to search proxied data is a broken idea - its an incomplete view of a remote repositories and when your dealing with tens of gigabytes of metadata and artifacts this becomes painful and slow. Anyway, I look forward to your comments. Thanks, James Dumay Thanks, Deng
Re: Archiva 1.1 Roadmap
Yes, agreed. +1 for this functionnality, which could, IMO, be implemented rapidely. Fabrice On Feb 5, 2008 8:40 AM, Maria Odea Ching [EMAIL PROTECTED] wrote: Hi Nicolas, I believe what you were pertaining in your scenario is like the repository grouping? Where in a number of managed repositories can be grouped together with that group having only one url. So you only need to specify that url in your settings.xml file and when Archiva receives a request via that url, it would look for that artifact from the repositories belonging to that group. This functionality is really handy especially if the users are not very familiar with Maven as in your corporate use-case.. Thanks, Deng On Feb 4, 2008 6:58 PM, nicolas de loof [EMAIL PROTECTED] wrote: My managed repository are on another windows Box (for corporate reason) and are proxied as file:// URLs. I have to manage them by hand as the DAV server doesn't support windows SMB file format \\server\path (that gets normalized to \server\path). That's not an issue for me as there is nothing to manage (only sometime deploy new artifacts). My maven managed repository duplicates those corporate repos, and also mirors public internet ones. I only use archiva as a proxy and cache, so don't care about scanner-based features on my corporate repos. Hand based management is enough for me on those one. If I configure them as managed repos, I may get artifact twice on browse ... to be honest I also don't use the browse feature ! For my use case, archiva is just a replacement of the good old maven-proxy I used for maven1, with the HUGE benefict I can manage a single maven2 repository and still have my old m1 projects (I still have lots) get the required artifacts. I have a second managed repository for snapshots as http://server/archiva/repository/snapshot with the required mirror in settings.xml for apache.snapshots codehaus.snapshots This configuration is simple for user but not very clean on server side. I can't take advantage of archiva features on my managed repos (even I don't need/use them now, they still are interesting). The virtual repository concept would solve the configuration issue but not my unsuported samba share filesystem issue :-( Nico. 2008/2/4, Fabrice Bellingard [EMAIL PROTECTED]: Nicolas, concerning your maven managed repository: are you currently really doing that with archiva? It seems indeed interesting, as it simplifies the configuration of the settings.xml file. However, I have a couple of questions: - this means that this maven repository duplicates every artifact handled in your other managed repositories, right? So when you browse artifacts in Archiva, you see managed artifacts twice, don't you? - do you use the same principle for snapshots repositories? I mean, metadata files would conflict with release repositories, so you need another virtual repository for snapshots. Fabrice On Feb 4, 2008 9:38 AM, nicolas de loof [EMAIL PROTECTED] wrote: Early version of archiva had on admin menu a sync repository entry. Not sure if the original idea was to manage a classical rsync-like miror or to isolate local cache for remote proxied repositories. I would suggest some virtual repository A simple example is my corporate use case : many user don't know maven well and have no idea what a repository is (and how to configure), so we have configured settings.xml to mirror all common repositories to the archiva instance : http://server/archiva/repository/maven The maven managed repository is an aggregate of proxied (central, java.net, jboss, ...) and managed ones : corporate builds, restricted jars (SUN apis, oracle driver) and sources bundles (missing in public repos) This repository, declared in archiva configuration as managed is NOT the one we have to manage ! It only is a facade to other managed and proxied repositories. Nico. One item I wanted to single out is the separation between managed repositories used for publishing and those used for caching artifacts from remote repositories. I don't think it makes much sense to have a managed repository that can do both. a big +1 here :) a lot of people has been confused over this especially when there are quite a handful of repositories being managed. This separation would allow us to have: * Provide indexing, browsing and search only for publishing (See foot note) * RSS feeds for new artifacts in published repositories. Foot note: Allowing to search proxied data is a broken idea - its an incomplete view of a remote repositories and when your dealing with tens
Re: [VOTE] Release Archiva 1.0.1
+1! Fabrice On 1/17/08, Maria Odea Ching [EMAIL PROTECTED] wrote: Hi Everyone, The Archiva 1.0.1 release candidate has been prepared. JPOX was upgraded from 1.1.7 to 1.1.9 to fix an issue that results for Archiva to hang. Other changes for this release include an improvement for maven 1 artifact resolution and revisions in the documentation. You can take a look at the release notes for Archiva 1.0.1 here: http://jira.codehaus.org/secure/ReleaseNote.jspa?version=13925styleName=TextprojectId=10980Create=Create While the binaries, including the sources, signatures and checksums, can be downloaded here: http://people.apache.org/builds/maven/archiva/1.0.1/ Everyone is encouraged to vote and give their feedback. Please make sure to test it before voting ;-) [ ] +1 Release it! [ ] 0 [ ] -1 Don't release it, because... The vote will be open for 72 hours. So, cast your votes now.. Here's my +1 Thanks, Deng
Re: [vote] separate issues@ list
+1 Fabrice On Dec 5, 2007 1:58 AM, Brett Porter [EMAIL PROTECTED] wrote: per the thread on [EMAIL PROTECTED] - should Archiva have it's own [EMAIL PROTECTED] list? [ ] +1 [ ] 0 [ ] -1 Cheers, Brett
Re: [Vote] Release Maven Clean Plugin 2.2 (take 2)
+1 Fabrice On Nov 30, 2007 12:43 AM, Vincent Siveton [EMAIL PROTECTED] wrote: Hi, I'd like to release (again) maven-clean-plugin 2.2. All artifacts respect the Apache release rules (Thanks Dan). This release fixes some bugs and makes some improvements. The last release was made over 1 year ago. Release Notes: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11128styleName=Htmlversion=13042 Staging repo: http://people.apache.org/~vsiveton/staging-repo/http://people.apache.org/%7Evsiveton/staging-repo/ Tag: https://svn.apache.org/repos/asf/maven/plugins/tags/maven-clean-plugin-2.2/ Vote open for 72 hours. Here is my +1 [ ] +1 [ ] +0 [ ] -1 Cheers, Vincent - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [vote] Alexandru Popescu as a committer
+1 Fabrice On Nov 23, 2007 12:52 PM, Brett Porter [EMAIL PROTECTED] wrote: Alex did the work to make TestNG support pretty much fully functional on Surefire trunk some months back and he and Dan Fabulich are now discussing this on the surefire-dev list and looking to complete the work. Alex is already a committer on Struts at Apache and one of the founders of TestNG itself. +1 from me Cheers, Brett -- Brett Porter - [EMAIL PROTECTED] Blog: http://www.devzuz.org/blogs/bporter/
Re: [vote] [take 2] release maven 2.0.8
+1 Fabrice On Nov 22, 2007 5:07 PM, Brian E. Fox [EMAIL PROTECTED] wrote: It's that time again, finally. The RC's have been floating for a few weeks now and no new issues have surfaced. (the packaging issues with the uber jar have been resolved since the last vote) The release is staged at: http://people.apache.org/~brianf/staging-repositoryhttp://people.apache.org/%7Ebrianf/staging-repository The binary packages are here: http://people.apache.org/~brianf/2.0.8/http://people.apache.org/%7Ebrianf/2.0.8/ Release Notes - Maven 2 - Version 2.0.8 ** Bug * [MNG-2025] - POM is still not read using the right encoding * [MNG-2045] - Maven can't compile against sibling test-jar dependency in multiproject (Test Attached) * [MNG-2061] - DistributionManagement properties don't get copied in cloned executionProject while lifecycle fork * [MNG-2254] - the encoding parameter in xml declaration of POM is ignored * [MNG-2277] - aggregating plugins in submodules of the reactor return all projects causing a chicken/egg issue * [MNG-2593] - Maven 2 stumbels upon non ASCII characters in the value of a localRepository value in the $HOME/.m2/settings.xml * [MNG-2685] - mvn.bat detection of 4NT syntax error * [MNG-2932] - Encoding chaos * [MNG-2961] - DefaultArtifact getBaseVersion is changed to -SNAPSHOT only if you first call isSnapshot() * [MNG-3046] - DefaultArtifactVersion compareTo misbehaves regarding buildNumber 0 * [MNG-3077] - NullPointerException, if MojoExecutionException has no message * [MNG-3084] - mvn.bat in maven 2.0.7 does not return the correct error code. * [MNG-3095] - maven-plugin-testing-tools causes bad version in deployed artifacts after tests are run * [MNG-3134] - DefaultModelInheritence::assembleDistributionInheritence should be childPathAdjustment aware * [MNG-3141] - Build not working if pom.xml is a symbolic link * [MNG-3215] - Missing rar artifact handler descriptor * [MNG-3240] - maven-model RepositoryBase.equals() causes ClassCastException * [MNG-3245] - Maven Reporting API is binary incompatible in 2.0.8-SNAPSHOT by r579987 * [MNG-3254] - artifactId is not appended any more in distributionManagement.site.url in multi modules when it's not defined in a child ** Improvement * [MNG-2188] - Report mojos should check canGenerateReport() when called directly * [MNG-2290] - Generated URLs in POMs of child modules * [MNG-3024] - Missing artifact error text improvement * [MNG-3047] - DefaultArtifactVersion compareTo inconsistent with equals * [MNG-3062] - Allow access to mojoExecution from within plugin. * [MNG-3118] - Test-classes should come before classes in the classpath * [MNG-3152] - Change to plugin testing harness to allow the setting of ArtifactRepository on the ArtifactStub * [MNG-3201] - org.apache.maven.project.MavenProject needs a toString() ** New Feature * [MNG-2105] - Enable remote debugging command line option (+ docs) * [MNG-2166] - Provide the help listing as default when no arguments are provided ** Task * [MNG-3088] - update the assembly name ** Wish * [MNG-3207] - Order of repositories for download should be inverted if Archiva is used. Vote is open for 72hrs +1
Re: [vote] Nicolas de Loof as a committer
Yes, Nicolas has been around for quite some time now +1 ! On Nov 21, 2007 10:08 AM, Brett Porter [EMAIL PROTECTED] wrote: I'd like to call a vote for Nicolas de Loof as a committer, based primarily on his work for Archiva, but also from being active in the general Maven community for quite some time. He has been relentlessly testing and identifying issues and providing patches recently. +1 from me - Brett -- Brett Porter - [EMAIL PROTECTED] Blog: http://www.devzuz.org/blogs/bporter/
Re: [VOTE] Release Archiva 1.0-beta-4
+1! :-) Fabrice. On Nov 9, 2007 11:17 AM, Maria Odea Ching [EMAIL PROTECTED] wrote: Hi Everyone, Archiva 1.0-beta-4 is now ready for release. The highlights of this release are: - security applied in repository browse and search (only those repositories where the user has permissions are accessible to that user) - fixes in repository purge - improved logging - additional fixes in proxy connectors configuration You can take a look at the release notes for Archiva 1.0-beta-4 here: http://jira.codehaus.org/secure/ReleaseNote.jspa?version=13818styleName=TextprojectId=10980Create=Create And the binaries, including the sources, signatures and checksums, can be downloaded here: http://people.apache.org/builds/maven/archiva/1.0-beta-4/ Everyone is encouraged to vote and give their feedback. [ ] +1 Release it! [ ] 0 [ ] -1 Don't release it, because... The vote will be open for 72 hours. So, cast your votes now ;-) Here's my +1 Thanks, Deng
Re: [VOTE] Release Archiva-1.0-beta-3 (Take 2)
Still +1! :-) Fabrice On 10/30/07, Maria Odea Ching [EMAIL PROTECTED] wrote: Hi Everyone, Take 2.. :) Archiva 1.0-beta-3 is now ready for release. The highlights of this release are: - major fixes in path resolution of artifacts (for proxying and consumers) - fixes in updating of metadata files - fixes in proxying - fixes in proxy connectors configuration - tomcat deployment issues - form validations in webapp The bugs that were found from the previously prepared 1.0-beta-3 has also been fixed. You can take a look at the release notes for Archiva 1.0-beta-3 here: http://jira.codehaus.org/secure/ReleaseNote.jspa?version=13660styleName=TextprojectId=10980Create=Create And the binaries, including the sources, signatures and checksums, can be downloaded here: http://people.apache.org/builds/maven/archiva/1.0-beta-3/ Everyone is encouraged to vote and give their feedback. [ ] +1 Release it! [ ] 0 [ ] -1 Don't release it, because... The vote will be open for 72 hours. So, cast your votes now ;-) Thanks, Deng
Re: [VOTE] Release Archiva 1.0-beta-3
Of course +1! :-) Fabrice On 10/22/07, Maria Odea Ching [EMAIL PROTECTED] wrote: Hi All, Archiva 1.0-beta-3 is now ready for release. The highlights of this release are: - major fixes in path resolution of artifacts (for proxying and consumers) - fixes in updating of metadata files - fixes in proxy connectors configuration - tomcat deployment issues - additional fixes in proxying - form validations in webapp The release notes for Archiva 1.0-beta-3 is available here: http://jira.codehaus.org/secure/ReleaseNote.jspa?version=13660styleName=TextprojectId=10980Create=Create http://jira.codehaus.org/secure/ReleaseNote.jspa?version=13660styleName=TextprojectId=10980Create=Create While the binaries including the sources, checksums and signatures can be found in: http://people.apache.org/builds/maven/archiva/1.0-beta-3/ http://people.apache.org/builds/maven/archiva/1.0-beta-2/ Everyone is encouraged to vote and give their feedback. [ ] +1 Release it! [ ] 0 [ ] -1 Don't release it, because... The vote will be open for 72 hours. So, cast your votes now ;-) Here's my +1 Thanks, Deng
Javadoc plugin and default Plexus Commandline
Hi guys, I've just updated some projects that now use Maven 2.0.7 along with the Javadoc plugin 2.3, and now my build fails because the UNIX platform where the integrations happen doesn't have bash. The reason is the following: the Javadoc plugin creates a default Commandline object to run the javadoc process, but with the last versions of Plexus Utils, the default constructor sets /bin/bash as the default shell. For what I've found in the code of both the Javadoc plugin and Plexus Utils, it seems to me that there is no way to specify another shell for UNIX systems. Do you have any idea of how I could handle that? The problem is that I don't have root privileges on the UNIX server... :-( Thanks in advance for any anwser! Cheers, Fabrice.
Re: Javadoc plugin and default Plexus Commandline
Hi Vincent, in Maven 2.0.x, it is not possible to add a dependency to a plugin in the reporting section. And if you put it in the pluginManagement section, this doesn't work either. (see bug MNG-1931) So that's why I don't see a solution to that... :-( Cheers, Fabrice. On 9/19/07, Vincent Siveton [EMAIL PROTECTED] wrote: Hi Fabrice, PLXUTILS-34 is included in p-u:1.4.6, so try to add it as dependency in the javadoc-plugin. Cheers, Vincent 2007/9/19, Fabrice Bellingard [EMAIL PROTECTED]: Hi guys, I've just updated some projects that now use Maven 2.0.7 along with the Javadoc plugin 2.3, and now my build fails because the UNIX platform where the integrations happen doesn't have bash. The reason is the following: the Javadoc plugin creates a default Commandline object to run the javadoc process, but with the last versions of Plexus Utils, the default constructor sets /bin/bash as the default shell. For what I've found in the code of both the Javadoc plugin and Plexus Utils, it seems to me that there is no way to specify another shell for UNIX systems. Do you have any idea of how I could handle that? The problem is that I don't have root privileges on the UNIX server... :-( Thanks in advance for any anwser! Cheers, Fabrice. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [vote] Mauro Talevi committer access
+1 Fabrice On 9/5/07, Brian E. Fox [EMAIL PROTECTED] wrote: Mauro is an existing Apache Committer on the Excalibur project (http://excalibur.apache.org/team-list.html) as well as the mojo project at Codehaus. He has recently been working on the shade plugin currently up for vote to be moved to Apache. As he has demonstrated ability and we can use the help maintaining shade and Maven in general, I'd like to call a vote to add Mauro as a Maven Committer. Vote will be open for 72 hrs. Adopted Project Conventions for new Committer votes: The vote duration should be specified in the mail, but must be a minimum of 72 hours (it may be made longer if there is a weekend or holiday in the middle). Votes on committers should be accepted from all committers on the project. There is no minimum number of votes needed for a vote to pass. The vote is decided by the majority (simply add all the +1's and -1's). Candidates can not be vetoed. Votes can be changed any time while the vote is still open and will supercede the previous vote by an individual. The vote should then be tallied, and if it has passed, the process for adding a new committer is followed. +1
Re: [proposal] Move Archiva's wiki to cwiki.apache.org
+1 Fabrice :) On 8/21/07, Brett Porter [EMAIL PROTECTED] wrote: Hi, Archiva currently has a subsection of the Maven user's wiki, which is a bit out of place. I'd like to propose we create two spaces on cwiki.apache.org: - ARCHIVADEV - for roadmap/proposals/etc. (edited by developers) - ARCHIVA - for knowledge-base/faq type content (edited by users) I will probably import the whole space into ARCHIVA, delete anything not related to Archiva, then move the development pages out. That will make it retain history, and should still be faster than copying individual pages. Both can use the template I already made to automatically be generated to static HTML and be inserted into a subsection of the Archiva site. Thoughts? - Brett
Re: [vote] Olivier Lamy as Continuum committer
+1 Fabrice On 8/13/07, Emmanuel Venisse [EMAIL PROTECTED] wrote: Hi, I'd like to give to Olivier commit access to Continuum. He provided lot of good patches, implemented new features (installations/profiles) and help users on the mailing lists here, my +1 Emmanuel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Archiva releases (Take 2)
Since I'm working on Archiva, I've always been testing it on Tomcat
5.5.23and I've never had a single problem (using the tips provided on
the Wiki:
http://docs.codehaus.org/display/MAVENUSER/Archiva+on+Tomcat)
I'll look at MRM-323 when I have some time (that is after my coming holidays
:-))
Fabrice.
On 8/2/07, Brett Porter [EMAIL PROTECTED] wrote:
I'd be happy to run some tests on Tomcat post beta-1 as well. I've
spent way too much time battling these things in a past life not to
have learned something that might be helpful :)
Anyone here deploying to something other than Tomcat? We have Jetty5
(via appserver) and 6 (via plugin) covered - I'm interested to know
if these issues are isolated to TC.
- Brett
On 02/08/2007, at 10:32 AM, Maria Odea Ching wrote:
Yep, we also expect users to deploy Archiva standalone in
production. So far, MRM-323 and all the other remaining Tomcat
issues are scheduled for 1.0.x since most of them needs to be
investigated further. I've looked at MRM-323 in jira and saw your
findings for this issue. I'll take a look at it later on and
maybe we could include this in beta-2 :)
Thanks,
Deng
Ludovic Maitre wrote:
Hi Maria, all,
Although i'm a new user of Archiva, i would like to know when in
the roadmap the team plan to fix issues related to running Archiva
inside Tomcat (issues like http://jira.codehaus.org/browse/
MRM-323 ) ? Is it something important for the team ? Did you
expect users to deploy Archiva standalone in production ?
Best regards,
Maria Odea Ching wrote:
Hi All,
We (Brett, Joakim and I) have segregated the issues in Jira to
prep for the upcoming 1.0 release (finally! :-) ). Anyway,
there'll be two beta releases first before 1.0.
So..here's the plan (excerpted from Brett):
- finish all issues for 1.0-beta-1
- then move on to 1.0-beta-2 issues for the next release
- do a big bug bash to find the problems in it
- decide on these found bugs for 1.0-beta-3 or 1.0.x (known issues)
Btw, I'll prepare 1.0-beta-1 for release on August 6 (that'll be
Monday my time), and this will include the following:
1. Resolved/Closed:
- MRM-290 (Ability to pre-configure the Jetty port in conf/
plexus.xml)
- MRM-326 (Adding/Editing repositories doesn't have validation)
- MRM-425 (Search and Browse do not work for snapshots)
- MRM-426 (Search does not work for snapshots because of
different version values in index and database when the snapshot
version is unique)
2. In Progress/Open:
- MRM-143 (Improve error reporting on corrupt jars, poms, etc)
- MRM-275 (add remove old snapshots Scheduler)
- MRM-294 (Repository purge feature for snapshots)
- MRM-329 (The Reports link gives an HTTP 500)
- MRM-347 (Undefined ${appserver.home} and ${appserver.base})
- MRM-373 (Unable to delete the pre-configured example network
proxy)
- MRM-412 (Add support for maven 1 (legacy) request to access a
maven2 (default layout) repo )
- MRM-428 (Managed and remote repositories with same name causes
problems)
- MRM-429 (Find artifact does not work when the applet is disabled)
- MRM-430 (Archiva always writes to ~/.m2/archiva.xml)
Everyone okay with this? :)
Thanks,
Deng
Re: Archiva releases (Take 2)
I've closed MRM-373 (Unable to delete the pre-configured example network
proxy), which was no longer valid.
Fabrice.
On 8/1/07, Maria Odea Ching [EMAIL PROTECTED] wrote:
Hi All,
We (Brett, Joakim and I) have segregated the issues in Jira to prep for
the upcoming 1.0 release (finally! :-) ). Anyway, there'll be two beta
releases first before 1.0.
So..here's the plan (excerpted from Brett):
- finish all issues for 1.0-beta-1
- then move on to 1.0-beta-2 issues for the next release
- do a big bug bash to find the problems in it
- decide on these found bugs for 1.0-beta-3 or 1.0.x (known issues)
Btw, I'll prepare 1.0-beta-1 for release on August 6 (that'll be Monday
my time), and this will include the following:
1. Resolved/Closed:
- MRM-290 (Ability to pre-configure the Jetty port in conf/plexus.xml)
- MRM-326 (Adding/Editing repositories doesn't have validation)
- MRM-425 (Search and Browse do not work for snapshots)
- MRM-426 (Search does not work for snapshots because of different
version values in index and database when the snapshot version is unique)
2. In Progress/Open:
- MRM-143 (Improve error reporting on corrupt jars, poms, etc)
- MRM-275 (add remove old snapshots Scheduler)
- MRM-294 (Repository purge feature for snapshots)
- MRM-329 (The Reports link gives an HTTP 500)
- MRM-347 (Undefined ${appserver.home} and ${appserver.base})
- MRM-373 (Unable to delete the pre-configured example network proxy)
- MRM-412 (Add support for maven 1 (legacy) request to access a maven2
(default layout) repo )
- MRM-428 (Managed and remote repositories with same name causes problems)
- MRM-429 (Find artifact does not work when the applet is disabled)
- MRM-430 (Archiva always writes to ~/.m2/archiva.xml)
Everyone okay with this? :)
Thanks,
Deng
Re: [VOTE] Release maven-changelog-plugin 2.1 (take 2)
+1 Fabrice On 7/19/07, Dennis Lundberg [EMAIL PROTECTED] wrote: Hi, This is a second try to release maven-changelog-plugin 2.1. All issues in JIRA have been closed, including MCHANGELOG-66 which came in during the last vote. Release Notes: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11211styleName=Htmlversion=12587 Tag: http://svn.apache.org/repos/asf/maven/plugins/tags/maven-changelog-plugin-2.1/ Staged at: http://people.apache.org/~dennisl/staging-repository-changelog-plugin/ Staged site at: http://people.apache.org/~dennisl/maven-changelog-plugin/index.html The vote will be open for 72 hours. Here is my +1 PS. I forgot to remove the staging repo from the last vote, before I did release:perform. So I did these steps, hope that is correct. If not please let me know. * Nuked the staging-repo on people.a.o * Went down into the directory target/checkout, that was just created * Ran mvn deploy -Prelease -DaltDeploymentRepository=same-as-in-settings.xml -- Dennis Lundberg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [vote] Release Maven Javadoc Plugin 2.3
+1 Fabrice On 7/16/07, Vincent Siveton [EMAIL PROTECTED] wrote: Hi, I would like to release the Maven Javadoc Plugin 2.3. The last release has been about 6 months ago. We solved around 30 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11138styleName=Htmlversion=13304 There are still a couple of issues left in JIRA: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=11138status=1 Tag: http://svn.apache.org/repos/asf/maven/plugins/tags/maven-javadoc-plugin-2.3/ Staging repo: http://people.apache.org/~vsiveton/staging-repo/ Site: http://maven.apache.org/plugins/maven-javadoc-plugin/ Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 Cheers, Vincent - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Release maven-changelog-plugin 2.1
+1 Fabrice On 7/17/07, Dennis Lundberg [EMAIL PROTECTED] wrote: Hi, I'd like to release maven-changelog-plugin 2.1. All issues in JIRA have been closed. Release Notes: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11211styleName=Htmlversion=12587 Tag: http://svn.apache.org/repos/asf/maven/plugins/tags/maven-changelog-plugin-2.1/ Staged at: http://people.apache.org/~dennisl/staging-repository-changelog-plugin/ Staged site at: http://people.apache.org/~dennisl/maven-changelog-plugin/index.html The vote will be open for 72 hours. Here is my +1 -- Dennis Lundberg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Can't commit because of a locked dir
Yop, it's OK now. Thx guys! :-) Fabrice. On 7/12/07, Richard van der Hoff [EMAIL PROTECTED] wrote: On Jul 12, 2007, at 10:36 AM, Fabrice Bellingard wrote: Today, I've tried several times to commit code in the maven-assembly-plugin, and I always get the same message: --- Attempted to lock an already-locked dir svn: Working copy 'C:\Maven\workspace\maven-assembly-plugin\src' locked --- That's a lock on the working copy, no? Try svn cleanup. -- Richard van der Hoff [EMAIL PROTECTED] Telephony Gateways Project Manager Tel: +44 (0) 845 666 7778 http://www.mxtelecom.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: new maven-loc-plugin, committer help required.
As Brett said, the codehaus JavaNCSS plugin already gives this information (and even more), so I'm not sure we want to add this to the JXR plugin... Fabrice. On 7/12/07, crowne [EMAIL PROTECTED] wrote: Hi All, A few days ago I was asked (yet again) for a count of the Lines of Code for a project that we have been working on. Needless to say that I got a bee in my bonnet and built a maven-loc-plugin-1.0-snapshot over the weekend. I started by copying the maven-jxr-plugin, and I had to make a few amendments to maven-jxr. This was done using maven2 mojos (not maven 1). Now how do I go about getting this stuff committed, or is it not wanted and should it be chucked? Regards, Neil. -- View this message in context: http://www.nabble.com/new-maven-loc-plugin%2C-committer-help-required.-tf4066829s177.html#a11555980 Sent from the Maven Developers mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Can't commit because of a locked dir
Today, I've tried several times to commit code in the maven-assembly-plugin, and I always get the same message: --- Attempted to lock an already-locked dir svn: Working copy 'C:\Maven\workspace\maven-assembly-plugin\src' locked --- Does anyone currently have a hook on the source directory of the assembly plugin? Cheers, Fabrice.
Re: Assembly plugin: readonly filters parameter can break a multimodule build
OK, I will work on this, then. Cheers Fabrice On 7/6/07, John Casey [EMAIL PROTECTED] wrote: That sounds like a fine idea to me. I commented on the issue, too, fwiw. Thanks, -john On Jul 6, 2007, at 5:55 AM, Fabrice Bellingard wrote: I got this problem while trying to make an assembly, with filtered files, from a root project. I created an issue on JIRA with an example: http://jira.codehaus.org/browse/MASSEMBLY-226 If the filters parameter would not be readonly, then this bug would be obsolete. Should I modify this? I ask the question because it seems that for some reason, this param became readonly whereas it didn't use to be at first. Cheers! Fabrice --- John Casey Committer and PMC Member, Apache Maven mail: jdcasey at commonjava dot org blog: http://www.ejlife.net/blogs/john
Assembly plugin: readonly filters parameter can break a multimodule build
I got this problem while trying to make an assembly, with filtered files, from a root project. I created an issue on JIRA with an example: http://jira.codehaus.org/browse/MASSEMBLY-226 If the filters parameter would not be readonly, then this bug would be obsolete. Should I modify this? I ask the question because it seems that for some reason, this param became readonly whereas it didn't use to be at first. Cheers! Fabrice
Maven site plugin and inheritance
Hi guys, I'm playing a bit with the maven site plugin to see what's left before it gets released. However, I have a problem with the site.xml inheritance when building multimodule projects: whether I define a site.xml file in submodules or not, the site plugin always uses the site.xml of the root project to generate the site of the submodules (when I run mvn site on the root project, of course). Is this the normal behaviour of inheritance for the site.xml? How should I do then if I want a cutom site for each submodule? Maybe http://docs.codehaus.org/display/MAVEN/Sites+and+Inheritence should be updated? Fabrice.
Re: [vote] Release Maven Shared JAR component 1.0
+1 Fabrice On 7/4/07, Brett Porter [EMAIL PROTECTED] wrote: This component is used in the project-info-reports plugin (and is a prereq to its next release) and analyses JAR files for Maven information and general Java class information. Tag: https://svn.apache.org/repos/asf/maven/shared/tags/maven-shared- jar-1.0 Staging Repo: http://people.apache.org/~brett/stage-repo/ Website/documentation: http://maven.apache.org/shared/maven-shared-jar/ [ ] +1 [ ] 0 [ ] -1 72 hours go! Cheers, Brett - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Release Archiva 1.0-alpha-2
Definitely +1 ! :-) Fabrice. On 6/24/07, Wendy Smoak [EMAIL PROTECTED] wrote: Archiva 1.0-alpha-2 was tagged and built on Saturday. The proposed files, including source and binary distributions, checksums, and signatures, can be found here: http://people.apache.org/builds/maven/archiva/1.0-alpha-2/ This release resolves several issues with proxying artifacts, and modifying the configuration through the web UI. The list of issues identified and closed with this release can be found below: Archiva 1.0-alpha-2 Release Notes: http://jira.codehaus.org/secure/ReleaseNote.jspa?version=13518styleName=TextprojectId=10980Create=Create (There were 16 issues still marked fix-for this version, which I moved to 1.0.x in JIRA.) Once you have had a chance to examine the distribution, please cast your vote. We welcome votes and feedback from all community members. [ ] +1 Release it! [ ] 0 [ ] -1 Don't release it, because... 72 hours ends Wednesday afternoon (GMT -7), but I probably won't have time to do anything else with it until Friday. -- Wendy
Re: Proxy connector whitelist/blacklist
Wendy, even without a whitelist entry of *, this proxy connector is working for me... Fabrice. On 6/23/07, Wendy Smoak [EMAIL PROTECTED] wrote: The proxy connector in the default configuration was apparently intended to proxy requests from internal to central, but it wasn't proxying anything. To get it to work, I added a whitelist entry of '*'. Is that working as designed, or should 'blank' (no whitelist or blacklist entries) mean 'proxy everything' (as seems to be implied by the original default config)? This needs to be documented so I don't have to guess. :) I see it in the list of Concepts on [1] but couldn't find anything else. [1] http://maven.apache.org/archiva/hacking/index.html -- Wendy
Re: Use of JDK 5 in Archiva
Still the same problem running a clean install with the following configuration: - Win2k - JDK 1.5.0_012 - Maven 2.0.7 No one else has the same issue? Fabrice. On 6/21/07, Brett Porter [EMAIL PROTECTED] wrote: No problems here, or on the solaris zone. You ran with clean as well? I'd suggest upgrading your JDK if it really is _01 - that's pretty old :) - Brett On 20/06/2007, at 8:42 PM, Fabrice Bellingard wrote: Hi Brett, I updated my workspace today and tried to build Archiva, and I get an error during JPOX enhancement, in the archiva-model module (UnsupportedClassVersionError, see at the end of the mail for the log). If I use the last revision of the Archiva's root POM (that is, with compiler set to 1.4), then Archiva builds fine. I'm using JDK 1.5.0_01 to run Maven. Any idea? Thanks, Fabrice. INFO [JPOX.Enhancer] - JPOX Enhancer : Input Files JPOX Enhancer : Input Files INFO [JPOX.Enhancer] - C:\Archiva\workspace\archiva\archiva-base\archiva-model\target \classes\org\apache\maven\archiva\model\package.jdo C:\Archiva\workspace\archiva\archiva-base\archiva-model\target \classes\org\apache\maven\archiva\model\package.jdo INFO [JPOX.Enhancer] - JPOX Enhancer : Using ClassEnhancer BCEL JPOX Enhancer : Using ClassEnhancer BCEL [ERROR] [ERROR] Standard error from the JPox enhancer tool: [ERROR] [ERROR] java.lang.UnsupportedClassVersionError: org/apache/maven/archiva/model/ArchivaRepositoryModel (Unsupported major.minor version 49.0) at java.lang.ClassLoader.defineClass0(Native Method) at java.lang.ClassLoader.defineClass(Unknown Source) at java.security.SecureClassLoader.defineClass(Unknown Source) at java.net.URLClassLoader.defineClass(Unknown Source) at java.net.URLClassLoader.access$100(Unknown Source) at java.net.URLClassLoader$1.run(Unknown Source) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(Unknown Source) at java.lang.ClassLoader.loadClass(Unknown Source) at sun.misc.Launcher$AppClassLoader.loadClass(Unknown Source) at java.lang.ClassLoader.loadClass(Unknown Source) at org.jpox.JDOClassLoaderResolver.classOrNull( JDOClassLoaderResolver.java:510) at org.jpox.JDOClassLoaderResolver.classForName( JDOClassLoaderResolver.java:196) at org.jpox.JDOClassLoaderResolver.classForName( JDOClassLoaderResolver.java:362) at org.jpox.metadata.AbstractClassMetaData.loadClass( AbstractClassMetaData.java:524) at org.jpox.metadata.ClassMetaData.populate(ClassMetaData.java:215) at org.jpox.metadata.MetaDataManager.populateFileMetaData( MetaDataManager.java:1060) at org.jpox.enhancer.bcel.metadata.BCELMetaDataManager.populateRegistered File( BCELMetaDataManager.java:241) at org.jpox.enhancer.bcel.BCELUtils.getMetaDataForInput (BCELUtils.java :175) at org.jpox.enhancer.JPOXEnhancer.main(JPOXEnhancer.java:512) Exception in thread main [ERROR] [INFO] -- -- [ERROR] BUILD ERROR [INFO] -- -- [INFO] The JPox enhancer tool exited with a non-null exit code. [INFO] -- -- On 6/19/07, Brett Porter [EMAIL PROTECTED] wrote: As in Continuum, I've made this change. I'm going with lazy consensus - so if there are any objections please holler before dependent code arrives :) On 19/06/2007, at 11:26 AM, [EMAIL PROTECTED] wrote: Author: brett Date: Mon Jun 18 18:26:34 2007 New Revision: 548544 URL: http://svn.apache.org/viewvc?view=revrev=548544 Log: allow use of JDK 5 in Archiva Modified: maven/archiva/trunk/pom.xml Modified: maven/archiva/trunk/pom.xml URL: http://svn.apache.org/viewvc/maven/archiva/trunk/pom.xml? view=diffrev=548544r1=548543r2=548544 = = --- maven/archiva/trunk/pom.xml (original) +++ maven/archiva/trunk/pom.xml Mon Jun 18 18:26:34 2007 @@ -95,11 +95,31 @@ /execution /executions /plugin +!-- Doesn't work on Mac with Java 6 yet + plugin +artifactIdmaven-enforcer-plugin/artifactId +executions + execution +idenforce-java/id +goals + goalenforce-once/goal +/goals +configuration + rules +requireJavaVersion + version1.5.0/version +/requireJavaVersion + /rules +/configuration + /execution +/executions + /plugin +-- plugin
Re: Use of JDK 5 in Archiva
I found the problem: for other purposes, I had modified the %PATH% variable to point to a 1.4.x JRE bin folder. So even if my JAVA_HOME was pointing to a 1.5 SDK, there was a problem with the JPOX plugin because it seems that it launches a java ... command in a new process... so JPOX was running on a 1.4 JVM. Now, everything works fine. Whew!! :-) Fabrice. On 6/21/07, Emmanuel Venisse [EMAIL PROTECTED] wrote: It works fine for me. The difference I see is the OS (WinXP and OSX) Emmanuel Fabrice Bellingard a écrit : Still the same problem running a clean install with the following configuration: - Win2k - JDK 1.5.0_012 - Maven 2.0.7 No one else has the same issue? Fabrice. On 6/21/07, Brett Porter [EMAIL PROTECTED] wrote: No problems here, or on the solaris zone. You ran with clean as well? I'd suggest upgrading your JDK if it really is _01 - that's pretty old :) - Brett On 20/06/2007, at 8:42 PM, Fabrice Bellingard wrote: Hi Brett, I updated my workspace today and tried to build Archiva, and I get an error during JPOX enhancement, in the archiva-model module (UnsupportedClassVersionError, see at the end of the mail for the log). If I use the last revision of the Archiva's root POM (that is, with compiler set to 1.4), then Archiva builds fine. I'm using JDK 1.5.0_01 to run Maven. Any idea? Thanks, Fabrice. INFO [JPOX.Enhancer] - JPOX Enhancer : Input Files JPOX Enhancer : Input Files INFO [JPOX.Enhancer] - C:\Archiva\workspace\archiva\archiva-base\archiva-model\target \classes\org\apache\maven\archiva\model\package.jdo C:\Archiva\workspace\archiva\archiva-base\archiva-model\target \classes\org\apache\maven\archiva\model\package.jdo INFO [JPOX.Enhancer] - JPOX Enhancer : Using ClassEnhancer BCEL JPOX Enhancer : Using ClassEnhancer BCEL [ERROR] [ERROR] Standard error from the JPox enhancer tool: [ERROR] [ERROR] java.lang.UnsupportedClassVersionError: org/apache/maven/archiva/model/ArchivaRepositoryModel (Unsupported major.minor version 49.0) at java.lang.ClassLoader.defineClass0(Native Method) at java.lang.ClassLoader.defineClass(Unknown Source) at java.security.SecureClassLoader.defineClass(Unknown Source) at java.net.URLClassLoader.defineClass(Unknown Source) at java.net.URLClassLoader.access$100(Unknown Source) at java.net.URLClassLoader$1.run(Unknown Source) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(Unknown Source) at java.lang.ClassLoader.loadClass(Unknown Source) at sun.misc.Launcher$AppClassLoader.loadClass(Unknown Source) at java.lang.ClassLoader.loadClass(Unknown Source) at org.jpox.JDOClassLoaderResolver.classOrNull( JDOClassLoaderResolver.java:510) at org.jpox.JDOClassLoaderResolver.classForName( JDOClassLoaderResolver.java:196) at org.jpox.JDOClassLoaderResolver.classForName( JDOClassLoaderResolver.java:362) at org.jpox.metadata.AbstractClassMetaData.loadClass( AbstractClassMetaData.java:524) at org.jpox.metadata.ClassMetaData.populate(ClassMetaData.java :215) at org.jpox.metadata.MetaDataManager.populateFileMetaData( MetaDataManager.java:1060) at org.jpox.enhancer.bcel.metadata.BCELMetaDataManager.populateRegistered File( BCELMetaDataManager.java:241) at org.jpox.enhancer.bcel.BCELUtils.getMetaDataForInput (BCELUtils.java :175) at org.jpox.enhancer.JPOXEnhancer.main(JPOXEnhancer.java:512) Exception in thread main [ERROR] [INFO] -- -- [ERROR] BUILD ERROR [INFO] -- -- [INFO] The JPox enhancer tool exited with a non-null exit code. [INFO] -- -- On 6/19/07, Brett Porter [EMAIL PROTECTED] wrote: As in Continuum, I've made this change. I'm going with lazy consensus - so if there are any objections please holler before dependent code arrives :) On 19/06/2007, at 11:26 AM, [EMAIL PROTECTED] wrote: Author: brett Date: Mon Jun 18 18:26:34 2007 New Revision: 548544 URL: http://svn.apache.org/viewvc?view=revrev=548544 Log: allow use of JDK 5 in Archiva Modified: maven/archiva/trunk/pom.xml Modified: maven/archiva/trunk/pom.xml URL: http://svn.apache.org/viewvc/maven/archiva/trunk/pom.xml? view=diffrev=548544r1=548543r2=548544 = = --- maven/archiva/trunk/pom.xml (original) +++ maven/archiva/trunk/pom.xml Mon Jun 18 18:26:34 2007 @@ -95,11 +95,31
Re: prepare to release eclipse 2.4
+1 Fabrice On 6/20/07, Brian E. Fox [EMAIL PROTECTED] wrote: It's been about 5 months since we last released eclipse. There are plenty of issues already fixed: http://jira.codehaus.org/secure/ReleaseNote.jspa?version=13001styleName =HtmlprojectId=11133Create=Create There are currently 24 remaining open. Any objections to cutting a release as is and bumping the rest to 2.5?
Re: Use of JDK 5 in Archiva
Hi Brett, I updated my workspace today and tried to build Archiva, and I get an error during JPOX enhancement, in the archiva-model module (UnsupportedClassVersionError, see at the end of the mail for the log). If I use the last revision of the Archiva's root POM (that is, with compiler set to 1.4), then Archiva builds fine. I'm using JDK 1.5.0_01 to run Maven. Any idea? Thanks, Fabrice. INFO [JPOX.Enhancer] - JPOX Enhancer : Input Files JPOX Enhancer : Input Files INFO [JPOX.Enhancer] - C:\Archiva\workspace\archiva\archiva-base\archiva-model\target\classes\org\apache\maven\archiva\model\package.jdo C:\Archiva\workspace\archiva\archiva-base\archiva-model\target\classes\org\apache\maven\archiva\model\package.jdo INFO [JPOX.Enhancer] - JPOX Enhancer : Using ClassEnhancer BCEL JPOX Enhancer : Using ClassEnhancer BCEL [ERROR] [ERROR] Standard error from the JPox enhancer tool: [ERROR] [ERROR] java.lang.UnsupportedClassVersionError: org/apache/maven/archiva/model/ArchivaRepositoryModel (Unsupported major.minor version 49.0) at java.lang.ClassLoader.defineClass0(Native Method) at java.lang.ClassLoader.defineClass(Unknown Source) at java.security.SecureClassLoader.defineClass(Unknown Source) at java.net.URLClassLoader.defineClass(Unknown Source) at java.net.URLClassLoader.access$100(Unknown Source) at java.net.URLClassLoader$1.run(Unknown Source) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(Unknown Source) at java.lang.ClassLoader.loadClass(Unknown Source) at sun.misc.Launcher$AppClassLoader.loadClass(Unknown Source) at java.lang.ClassLoader.loadClass(Unknown Source) at org.jpox.JDOClassLoaderResolver.classOrNull( JDOClassLoaderResolver.java:510) at org.jpox.JDOClassLoaderResolver.classForName( JDOClassLoaderResolver.java:196) at org.jpox.JDOClassLoaderResolver.classForName( JDOClassLoaderResolver.java:362) at org.jpox.metadata.AbstractClassMetaData.loadClass( AbstractClassMetaData.java:524) at org.jpox.metadata.ClassMetaData.populate(ClassMetaData.java:215) at org.jpox.metadata.MetaDataManager.populateFileMetaData( MetaDataManager.java:1060) at org.jpox.enhancer.bcel.metadata.BCELMetaDataManager.populateRegisteredFile( BCELMetaDataManager.java:241) at org.jpox.enhancer.bcel.BCELUtils.getMetaDataForInput(BCELUtils.java :175) at org.jpox.enhancer.JPOXEnhancer.main(JPOXEnhancer.java:512) Exception in thread main [ERROR] [INFO] [ERROR] BUILD ERROR [INFO] [INFO] The JPox enhancer tool exited with a non-null exit code. [INFO] On 6/19/07, Brett Porter [EMAIL PROTECTED] wrote: As in Continuum, I've made this change. I'm going with lazy consensus - so if there are any objections please holler before dependent code arrives :) On 19/06/2007, at 11:26 AM, [EMAIL PROTECTED] wrote: Author: brett Date: Mon Jun 18 18:26:34 2007 New Revision: 548544 URL: http://svn.apache.org/viewvc?view=revrev=548544 Log: allow use of JDK 5 in Archiva Modified: maven/archiva/trunk/pom.xml Modified: maven/archiva/trunk/pom.xml URL: http://svn.apache.org/viewvc/maven/archiva/trunk/pom.xml? view=diffrev=548544r1=548543r2=548544 == --- maven/archiva/trunk/pom.xml (original) +++ maven/archiva/trunk/pom.xml Mon Jun 18 18:26:34 2007 @@ -95,11 +95,31 @@ /execution /executions /plugin +!-- Doesn't work on Mac with Java 6 yet + plugin +artifactIdmaven-enforcer-plugin/artifactId +executions + execution +idenforce-java/id +goals + goalenforce-once/goal +/goals +configuration + rules +requireJavaVersion + version1.5.0/version +/requireJavaVersion + /rules +/configuration + /execution +/executions + /plugin +-- plugin artifactIdmaven-compiler-plugin/artifactId configuration - source1.4/source - target1.4/target + source1.5/source + target1.5/target /configuration /plugin plugin
Re: Planning for 1.0-alpha-2
Hi Joakim, which proxy related bugs do you think of? I've tested Archiva proxying for some days, and it works pretty good for me. I mean, if we'd have to release alpha-2, I wouldn't say no. :-) Fabrice. On 6/19/07, Joakim Erdfelt [EMAIL PROTECTED] wrote: There are a few proxy related bugs left to work out in 1.0-alpha-2, I'd like to get a functional proxying working for the 1.0-alpha-2 release. I think this weekend might be doable. But that depends on the help testing the bug fixes. - Joakim Wendy Smoak wrote: How does the weekend of June 23rd sound for another Archiva alpha release? Joakim, are you already planning to do one before then? Any thoughts on how many of the 110 issues marked for 1.0-alpha-2 in jira could actually make it in that two-week time frame? Thanks, Wendy
Re: Moderation on commit messages
I got the confirmation mail and answered it, this should be OK now. Thanks! Fabrice. On 6/6/07, Max Bowsher [EMAIL PROTECTED] wrote: Carlos Sanchez wrote: Fabrice commits are getting moderated, can I subscribe hime directly or he has to do it himself ? Fabrice can do it himself by sending an email from his Apache address, to: [EMAIL PROTECTED] and responding to the resultant confirmation email. Alternatively, if Fabrice uses his Apache address as a read-only alias, and it isn't convenient for him to send a message from it, he can send to this address instead: [EMAIL PROTECTED] which will result in a confirmation going to Fabrice as above. Alternatively, if an authorized list administrator uses the address above, the confirmation email will go to that list administrator, who can then acknowledge the confirmation without involving Fabrice. Max.
Re: [VOTE] Release Archiva 1.0-alpha-1
+1, I'm happy with it already. :-) Nicolas, getting artifacts from proxied remote repositories works fine for me (at least it used to 3 days ago...). If I can help... Fabrice. On 6/4/07, nicolas de loof [EMAIL PROTECTED] wrote: +1 as a new clean codebase for enhancements, based on 0.9 features set. My personnal feedback on current features : + Verry clean configuration UI - Getting artifacts from a proxied repository doesn't work - Lack of support for Maven 1 (requests are not converted to get artifacts from a maven2 managed repo) - wagon-provider-api 1.0 has a ConcurrentModificationException issue (WAGON-79) 2007/6/4, Maria Odea Ching [EMAIL PROTECTED]: +1 Everything on the release notes seems to be in place. Thanks Joakim :-) -Deng Joakim Erdfelt wrote: Archiva 1.0-alpha-1 was tagged and built this afternoon. The proposed distribution, including binary distributions, and signatures can be found here: http://people.apache.org/builds/maven/archiva/1.0-alpha-1/ To keep up with the trend started by Wendy Smoak (sorta): The 1.0-alpha-1 staged copy was setup and configured to point to a pre-built repository, and then used to build the next archiva snapshot (1.0-alpha-2-SNAPSHOT) in archiva/trunk. This will be Archiva's first release with a proper database, and is intended to get a testable baseline of the archiva feature set into the hands of all interested individuals. The list of issues identified and closed with this release can be found below: Archiva 1.0-alpha-1 Release Notes: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10980styleName=Htmlversion=13443 This is an alpha release, and as such, has bugs. Once people have a chance to kick the prototype tires, and look around, the most urgent jira tickets will be addressed quickly for a 1.0-alpha-2 release, with an expected release 1 to 2 weeks after this one. Known issues include documentation, problems with proxying, problems running the webapp on Tomcat, missing reporting, empty or inaccurate dependency tree information, and poor grammar. These and other issues can be tracked at the URL below: Archiva 1.0-alpha-2 Open Issues: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truemode=hidesorter/order=DESCsorter/field=priorityresolution=-1pid=10980fixfor=13518 Once you have had a chance to examine the distribution, please cast your vote. We welcome votes and feedback from all community members. [ ] +1 Release it! [ ] 0 [ ] -1 Don't release it, because... 72 hours ends Monday afternoon (GMT -5) If you need more time, just ask.
Remote repositories not displayed anymore
Hi, I've updated my local copy of Archiva this morning and built it, and it seems that Archiva has problems to load its configuration as I get a There are no remote repositories configured yet when I go to Administration - Repositories (whereas remote repositories do exist in archiva.xml). This was working properly yesterday. Do you have the same behaviour? Fabrice.
Re: [VOTE] Release jxr 2.1
+1 Fabrice. On 3/31/07, Dennis Lundberg [EMAIL PROTECTED] wrote: Hi, I'd like to release jxr 2.1. For this release the maven-jxr library and the maven-jxr-plugin has been put together in svn, similar to what has been done with release and surefire. They will be released simultaneously. I have also merged the issues in JIRA for this release into the JXR project and have created two components there. I'm not sure what to do with the MJXR project in JIRA. It should at least be made read-only if/when this release passes. How was this handled for release and surefire? Release Notes: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11085styleName=Htmlversion=12533 Tag: http://svn.apache.org/repos/asf/maven/jxr/tags/jxr-2.1/ Staged at: http://people.apache.org/~dennisl/staging-repository-jxr/ The vote will be open for 72 hours. Here is my +1 -- Dennis Lundberg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Release Maven 2.0.6
+1 Fabrice. On 3/27/07, Jason van Zyl [EMAIL PROTECTED] wrote: Hi, The roadmap is here: http://jira.codehaus.org/secure/IssueNavigator.jspa? reset=truepid=10500fixfor=13010 The tag is here: http://svn.apache.org/repos/asf/maven/components/tags/maven-2.0.6/ Staging repository: http://people.apache.org/~jvanzyl/staging-repository/maven-2.0.6/ And the distros you are interested in are here: http://people.apache.org/~jvanzyl/staging-repository/maven-2.0.6/org/ apache/maven/maven-core/2.0.6/ Thanks, Jason. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Commit Privs for Patrick Schneider
+1 Fabrice. On 3/16/07, Jason van Zyl [EMAIL PROTECTED] wrote: Hi, Patrick has, for at least a couple months, been working on MNG-1577, has written extensive tests, changed and altered patches for anything and everything that's been asked of him. He worked with Mike and Ralph discussing the problem, getting the patches prepared and in for this fix, ultimately arriving at a solution that makes Maven a far more reliable system. He's been great to work with and he never relented and patched and patched and patched. He is now intimately familiar with Maven's dependency mechanism and he would be a great addition to the team in helping us sort out more artifact related problems :-) +1 Thanks, Jason. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [vote] Release Maven Surefire 2.3
+1 Fabrice. On 2/23/07, Brett Porter [EMAIL PROTECTED] wrote: Please vote for the release of Surefire 2.3. This now includes the API, providers, plugin and report plugin. [ ] +1 [ ] 0 [ ] -1 Staged at: http://people.apache.org/~brett/release-staging-repo/ Vote is open for 72 hours. Release notes: ** Bug * [SUREFIRE-49] - Surefire leaves null/$TestNGGroupName directories after mvn test * [SUREFIRE-53] - context classloader not always reset to original values * [SUREFIRE-54] - Remove use of parent classloader in surefirebooter but keep TestNG support working * [SUREFIRE-99] - Surefire plugin fails if JUnit is not available * [SUREFIRE-101] - Plugin not longer sets system properties when forking is on and debugging information is not correct * [SUREFIRE-105] - Documentation link on website does not point to surefire parameter docs * [SUREFIRE-106] - Classloading problem for getting a resource * [SUREFIRE-113] - surefire-providers-2.0.pom contains strange dependencies which generate error * [SUREFIRE-114] - Surefire plugin throws NoSuchMethodException when errors occur during TestSetup decorator * [SUREFIRE-120] - When you include a JUnit TestSuite (with no test methods), no tests are run * [SUREFIRE-122] - With forkmode once, XML reports are cumulative * [SUREFIRE-123] - SurefireBooter can initialize classloader with badly formed URLs * [SUREFIRE-125] - Surefire finds test classes but ignores test methods and configuration methods with TestNG and includes tag * [SUREFIRE-127] - Wrong issue-site URL on website * [SUREFIRE-263] - Source repository information on the web site is out of date ** Improvement * [SUREFIRE-31] - support junit 4.0 * [SUREFIRE-134] - Display location of test failures/errors on summary * [SUREFIRE-135] - when fork is enabled, Surefire should use the same JVM running Maven (i.e. use java.home sysprop), rather than expecting java to be in the system PATH * [SUREFIRE-138] - Add option to redirect stdout from tests to a file ** New Feature * [SUREFIRE-129] - add a property to skip tests execution (but not tests compilation) ** Task * [SUREFIRE-133] - Review Plugin Documentation Note: a 2.4 release is being worked on immediately to resolve some issues with TestNG. This release is being made available to users having the above problems before that work begins. Cheers, Brett - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Release Maven 2.0.5 (take 2)
Hi Brian, Strange, hey?... Which OS are you running Maven on? Because Stephen's got the same error as me on Fedore Core 6... Fabrice. On 2/13/07, Brian E. Fox [EMAIL PROTECTED] wrote: Hi Fabrice, I'm doing exactly what you describe and from what I can see, the latest 2.0.5 is working ok. I did find an issue in one of the early 2.0.5 release candidates, but it was fixed. The method I use is attached to http://jira.codehaus.org/browse/MNG-2749. Thanks, Brian -Original Message- From: Fabrice Bellingard [mailto:[EMAIL PROTECTED] Sent: Monday, February 12, 2007 10:02 AM To: Maven Developers List Subject: Re: [VOTE] Release Maven 2.0.5 (take 2) Hi Jason, The issue http://jira.codehaus.org/browse/MNG-2795 (Classloader problem loading a resource from a build extension Jar) still breaks my integrations with this last build of Maven... :-( As you tried the test project successfully, I don't understand what can be specific to my environment . I've made a clean installation of Maven (no local repository and last build of 2.0.5), and still it breaks the test case I attached on JIRA. Is there someone here who develops Checkstyle custom Checks and bundles them in a JAR (along with the configuration file) which is specified in the build extensions of another project? Or at least someone else who could test the case I described on JIRA? (with a clean installation) I may sound insisting on this, but the fact is that we have developed custom Checks in my company, and tens of projects are using them to generate the checkstyle report. As 2.0.5 currently breaks our builds, they wouldn't be able to migrate to this new and awaited version of Maven. Which is sad because they're looking forward to using it... Apart from that, everything works fine. :-) Fabrice. On 2/12/07, Jason van Zyl [EMAIL PROTECTED] wrote: Hi, The assemblies that people are interested in are staged here: http://people.apache.org/~jvanzyl/staging-repository/org/apache/maven/h ttp://people.apache.org/%7Ejvanzyl/staging-repository/org/apache/maven/ maven-core/2.0.5/ Here is the JIRA roadmap: http://jira.codehaus.org/secure/IssueNavigator.jspa ? reset=truepid=10500fixfor=12294sorter/field=issuekeysorter/ order=DESC +1 Thanks, Jason. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: 2.0.5 and MNG-2794
Hi Jason, the aim of this particular test case I implemented was to reproduce the bug. I made it simple to show the issue, and I agree that if you use a class for compilation, you should specify it as a dependency in your POM. However, the problem I had when I found this issue was slightly different. My original code does not require commons-collections for compilation, but it relies on 2 components which require 2 different versions of this library. So commons-collections is actually required, but for runtime only (the build broke during the execution of the unit tests). As Brett said, this should be mentioned clearly in the release notes because lots of people may be surprised. Fabrice. On 2/11/07, Jason van Zyl [EMAIL PROTECTED] wrote: Hi, After looking at MNG-2794 I don't think it's something we should fix change. The 2.0.4 release was working in a way contrary to our documentation in that the nearest with 2.0.4 was not being selected and it is with 2.0.5. So we either fix it and then it conflicts with what we document, or leave it and have work as documented. That particular test case also requires commons-collections for compilation and you should always specify directly any dependencies you need to compile your project. The details are in the comment, but I say we leave the behavior that is present in 2.0.5 now. http://jira.codehaus.org/browse/MNG-2794#action_87295 Thanks, Jason. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Release Maven 2.0.5 (take 2)
Hi Jason, The issue http://jira.codehaus.org/browse/MNG-2795 (Classloader problem loading a resource from a build extension Jar) still breaks my integrations with this last build of Maven... :-( As you tried the test project successfully, I don't understand what can be specific to my environment . I've made a clean installation of Maven (no local repository and last build of 2.0.5), and still it breaks the test case I attached on JIRA. Is there someone here who develops Checkstyle custom Checks and bundles them in a JAR (along with the configuration file) which is specified in the build extensions of another project? Or at least someone else who could test the case I described on JIRA? (with a clean installation) I may sound insisting on this, but the fact is that we have developed custom Checks in my company, and tens of projects are using them to generate the checkstyle report. As 2.0.5 currently breaks our builds, they wouldn't be able to migrate to this new and awaited version of Maven. Which is sad because they're looking forward to using it... Apart from that, everything works fine. :-) Fabrice. On 2/12/07, Jason van Zyl [EMAIL PROTECTED] wrote: Hi, The assemblies that people are interested in are staged here: http://people.apache.org/~jvanzyl/staging-repository/org/apache/maven/http://people.apache.org/%7Ejvanzyl/staging-repository/org/apache/maven/ maven-core/2.0.5/ Here is the JIRA roadmap: http://jira.codehaus.org/secure/IssueNavigator.jspa ? reset=truepid=10500fixfor=12294sorter/field=issuekeysorter/ order=DESC +1 Thanks, Jason. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Release Maven 2.0.5 (take 2)
Thanks for the hint, Dan, this actually works perfectly! I wasn't aware of this way to specify the JAR. It would be worth updating the documentation of the Checkstyle plugin. I will create a JIRA issue for this. FYI, Jason, yes, I've executed the test project on the bane of your existence ;-) - Windows XP with Java 1.5.0_06 - Windows 2k with Java 1.4.2_02 So even if this way of using the build extension is deprecated, I think this remains a bug on Windows. Anyways, everything works fine now. So here is my (non-binding) +1 :-) Fabrice. On 2/12/07, Daniel Kulp [EMAIL PROTECTED] wrote: Just FYI: we (CXF team) put our checkstyle rules into a jar bundle and use that. However, we don't put it in the extensions. We put it as a direct dependency for the plugin: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-checkstyle-plugin/artifactId dependencies dependency groupIdorg.apache.cxf/groupId artifactIdcxf-buildtools/artifactId version. /version /dependency /dependencies .. plugin and that works fine with 2.0.5. Dan
Re: [PROPOSAL] Standard Reporting
Or in the Maven sandbox, that'd be a more appropriate place :-) (I'm only talking about the standardized report framework that Joakim introduced, of course) On 1/31/07, Garvin LeClaire [EMAIL PROTECTED] wrote: Let me fix my over zealeous typing ;-o) Why don't we put the code in the Plugin sandbox at Codehaus? This will give us and others time to test drive it and move on from there. I think I need to use the dashboard plugin a little more before we do merging. I could get some of my current users to give feedback also. -- Regards, Garvin LeClaire [EMAIL PROTECTED] On 1/31/07, Garvin LeClaire [EMAIL PROTECTED] wrote: Why don't we put the code in the Plugin sandbox at Codehaus? This will give us and other to test drive it and move on from there. I think i need to use the dashboard plugin a little more before we do merging. I could get some of my current users to give feedback. -- Regards, Garvin LeClaire [EMAIL PROTECTED] On 1/31/07, Joakim Erdfelt [EMAIL PROTECTED] wrote: The dashboard plugin is definitely within the scope of this proposal, but is still just 1 consumer of the datapoint data. The dashboard plugin would be definitely be affected dramatically by this concept, it would no longer need to know what the other reports are, how they are formatted, etc. Should we create a new maven top level project for this? Ala WAGON / SCM / ARCHIVA / CONTINUUM ? - Joakim Erdfelt dvicente wrote: why don't you join the common effort with dashboard project? see : http://jira.codehaus.org/browse/MSITE-189 (Coordinate the efforts of several users to write a Dashboard Plugin for Maven 2) or http://docs.codehaus.org/display/MAVEN/Maven+Dashboard I think that the same idea ? David bellingard wrote: Hi guys, it seems that this proposal arrives right on time! :-) I've just been hired by a company that has developed, for its own needs, an application that can store code metrics, consolidate them and show them in various ways. I haven't had the time to look more into it yet, but it looks very promising though. So I asked the CEO to open-source it, and he seems ready to go for it if I can find a good place for the project to start (I still need to see that point... I was thinking of proposing it to the Apache Incubator, but I need to dig more into this question). Maven is a build tool that already produces lots of data that is transformed into static reports. As you said Joakim, this would be *very* valuable to push this data into a data store. Maven could then generate more comprehensive reports from it. Good ! Then, let's say that the data store is the database of the application I just talked about: this would be even more powerful as we would benefit from what already exists in this application (dynamic views, consolidation engine, ...). With such a solution, any kind of complex report becomes easier to develop as long as you have the information (I'm referring to your wild dreaming idea ;-) ). So I'm 100% for encouraging to start designing and then implementing the appropriate hooks into maven 2.1! Cheers, Fabrice. On 1/31/07, Garvin LeClaire [EMAIL PROTECTED] wrote: Joakim, I think that is a good idea. I have thought about this also when I was working on the Findbugs plug-in. I think this would faciliate a more effective way to do dashboard type reports. I was thinking about developing a Doxia JDBCWriter for Plugins to use. I would like to have the ability to have more than one writer for a plug-in. This may be possible but I did not see it. I would think we would embed Derby for simplicity from the support standpoint. This would provide a good self contained reference for a user to get started. Do you have a suggested schema for the database yet? -- Regards, Garvin LeClaire [EMAIL PROTECTED] On 1/30/07, Joakim Erdfelt [EMAIL PROTECTED] wrote: There are many reports and plugins now that generate reports against the code. I'd like to see an entire framework built around the concept of Standardized Reporting. The components of this framework... maven-reporting-datapoint This would provide an API that various reporting plugins (checkstyle / pmd / findbugs / etc...) can utilize to issue a very generic datapoint DataPoint.report(Project project, File sourceFile, long line, int severity, String type, String message); This API in turn logs the information into a data store (derby / hsqldb / xmlstore) with a timestamp of its occurance. This library would also provide an abstract standard report generator to produce a report that is consistent for all plugins. maven-datapoint-report-plugin This would provide a report
Re: [PROPOSAL] Standard Reporting
Hi guys, it seems that this proposal arrives right on time! :-) I've just been hired by a company that has developed, for its own needs, an application that can store code metrics, consolidate them and show them in various ways. I haven't had the time to look more into it yet, but it looks very promising though. So I asked the CEO to open-source it, and he seems ready to go for it if I can find a good place for the project to start (I still need to see that point... I was thinking of proposing it to the Apache Incubator, but I need to dig more into this question). Maven is a build tool that already produces lots of data that is transformed into static reports. As you said Joakim, this would be *very* valuable to push this data into a data store. Maven could then generate more comprehensive reports from it. Good ! Then, let's say that the data store is the database of the application I just talked about: this would be even more powerful as we would benefit from what already exists in this application (dynamic views, consolidation engine, ...). With such a solution, any kind of complex report becomes easier to develop as long as you have the information (I'm referring to your wild dreaming idea ;-) ). So I'm 100% for encouraging to start designing and then implementing the appropriate hooks into maven 2.1! Cheers, Fabrice. On 1/31/07, Garvin LeClaire [EMAIL PROTECTED] wrote: Joakim, I think that is a good idea. I have thought about this also when I was working on the Findbugs plug-in. I think this would faciliate a more effective way to do dashboard type reports. I was thinking about developing a Doxia JDBCWriter for Plugins to use. I would like to have the ability to have more than one writer for a plug-in. This may be possible but I did not see it. I would think we would embed Derby for simplicity from the support standpoint. This would provide a good self contained reference for a user to get started. Do you have a suggested schema for the database yet? -- Regards, Garvin LeClaire [EMAIL PROTECTED] On 1/30/07, Joakim Erdfelt [EMAIL PROTECTED] wrote: There are many reports and plugins now that generate reports against the code. I'd like to see an entire framework built around the concept of Standardized Reporting. The components of this framework... maven-reporting-datapoint This would provide an API that various reporting plugins (checkstyle / pmd / findbugs / etc...) can utilize to issue a very generic datapoint DataPoint.report(Project project, File sourceFile, long line, int severity, String type, String message); This API in turn logs the information into a data store (derby / hsqldb / xmlstore) with a timestamp of its occurance. This library would also provide an abstract standard report generator to produce a report that is consistent for all plugins. maven-datapoint-report-plugin This would provide a report similar to JXR and Cobertura that lists the source files, complete with hits against each file from all reports that use the datapoint API. Inline messages and highlighting can be used to show the line and all problems associated with that line from each datapoint generator. This information should be produced on a per-module and aggregated perspective. A historical graph can be shown from this datapoint information for that module / project / file. (sparkline) What needs to be done is identify the reporting types, and attempt to define as few 'standard reports' views as possible. The needs of JDepend is different than PMD or even Cobertura. Heck, a standard report format might just be a pipe dream, but the rest of the datapoint proposal should still have merit. If this is a good idea, I think we should encourage the appropriate hooks into maven 2.1 for this functionality, and then work on this as a seperate concept. Wild dreaming ideas. Implement a standard Maven SCM Annotate method so that datapoints in the code can even be associated to the developer that created that line, producing historical charts for each developer too! - Joakim - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [PROPOSAL] Standard Reporting
Joakim is definitely right: the dashboard plugin would only be one consumer. What's more, Maven can generate only static pages while the application I'm talking about is a dynamical web application, with far more possibilities than just generated web pages. As for creating a new maven top level projet for the reporting framework that would be embeded in Maven, let's see what the PMCs think about all this! :-) On 1/31/07, Joakim Erdfelt [EMAIL PROTECTED] wrote: The dashboard plugin is definitely within the scope of this proposal, but is still just 1 consumer of the datapoint data. The dashboard plugin would be definitely be affected dramatically by this concept, it would no longer need to know what the other reports are, how they are formatted, etc. Should we create a new maven top level project for this? Ala WAGON / SCM / ARCHIVA / CONTINUUM ? - Joakim Erdfelt dvicente wrote: why don't you join the common effort with dashboard project? see : http://jira.codehaus.org/browse/MSITE-189 (Coordinate the efforts of several users to write a Dashboard Plugin for Maven 2) or http://docs.codehaus.org/display/MAVEN/Maven+Dashboard I think that the same idea ? David bellingard wrote: Hi guys, it seems that this proposal arrives right on time! :-) I've just been hired by a company that has developed, for its own needs, an application that can store code metrics, consolidate them and show them in various ways. I haven't had the time to look more into it yet, but it looks very promising though. So I asked the CEO to open-source it, and he seems ready to go for it if I can find a good place for the project to start (I still need to see that point... I was thinking of proposing it to the Apache Incubator, but I need to dig more into this question). Maven is a build tool that already produces lots of data that is transformed into static reports. As you said Joakim, this would be *very* valuable to push this data into a data store. Maven could then generate more comprehensive reports from it. Good ! Then, let's say that the data store is the database of the application I just talked about: this would be even more powerful as we would benefit from what already exists in this application (dynamic views, consolidation engine, ...). With such a solution, any kind of complex report becomes easier to develop as long as you have the information (I'm referring to your wild dreaming idea ;-) ). So I'm 100% for encouraging to start designing and then implementing the appropriate hooks into maven 2.1! Cheers, Fabrice. On 1/31/07, Garvin LeClaire [EMAIL PROTECTED] wrote: Joakim, I think that is a good idea. I have thought about this also when I was working on the Findbugs plug-in. I think this would faciliate a more effective way to do dashboard type reports. I was thinking about developing a Doxia JDBCWriter for Plugins to use. I would like to have the ability to have more than one writer for a plug-in. This may be possible but I did not see it. I would think we would embed Derby for simplicity from the support standpoint. This would provide a good self contained reference for a user to get started. Do you have a suggested schema for the database yet? -- Regards, Garvin LeClaire [EMAIL PROTECTED] On 1/30/07, Joakim Erdfelt [EMAIL PROTECTED] wrote: There are many reports and plugins now that generate reports against the code. I'd like to see an entire framework built around the concept of Standardized Reporting. The components of this framework... maven-reporting-datapoint This would provide an API that various reporting plugins (checkstyle / pmd / findbugs / etc...) can utilize to issue a very generic datapoint DataPoint.report(Project project, File sourceFile, long line, int severity, String type, String message); This API in turn logs the information into a data store (derby / hsqldb / xmlstore) with a timestamp of its occurance. This library would also provide an abstract standard report generator to produce a report that is consistent for all plugins. maven-datapoint-report-plugin This would provide a report similar to JXR and Cobertura that lists the source files, complete with hits against each file from all reports that use the datapoint API. Inline messages and highlighting can be used to show the line and all problems associated with that line from each datapoint generator. This information should be produced on a per-module and aggregated perspective. A historical graph can be shown from this datapoint information for that module / project / file. (sparkline) What needs to be done is identify the reporting types, and attempt to define as few 'standard reports' views as possible. The needs of JDepend is different than PMD or even Cobertura. Heck, a standard report format might just be a pipe dream, but the rest of the datapoint proposal should still have merit. If this is a good idea,
Re: Maven 2.0.5 - open bugs?
Yes, I should have done that sooner. Here are the issues: - http://jira.codehaus.org/browse/MNG-2794 - http://jira.codehaus.org/browse/MNG-2795 Feel free to contact me if you have any questions. Fabrice. On 1/26/07, Jason van Zyl [EMAIL PROTECTED] wrote: On 25 Jan 07, at 3:38 PM 25 Jan 07, Fabrice Bellingard wrote: Jason, what about the issues I had when testing version 2.0.5, and for which I sent you a project that reproduces one of the bug? (transitive dependency resolution problem and checkstyle plugin failure). Did you identify them as real issues and postponed them to 2.0.6? Or maybe found they weren't real problems? Did you assign the issue to 2.0.5 in JIRA. I can't keep track of requests in mail. I'm going to roll a stage of 2.0.5 again tomorrow so push it into 2.0.5. JIRA is my memory. Jason. Fabrice. On 1/25/07, Jason van Zyl [EMAIL PROTECTED] wrote: There is one issue which Trygve raised which I thought he assigned to 2.0.5. It is the issue where Maven is trying to continually try to find snapshots instead of only checking daily. I am done with my crunch at a client this week so I'll call the vote tomorrow afternoon. Jason. On 25 Jan 07, at 4:36 AM 25 Jan 07, Federico Yankelevich wrote: Hi, few days ago there was a lot of interest in a thread calling a vote for releasing maven 2.0.5 (http://www.nabble.com/-VOTE--Release-Maven-2.0.5- tf2966962s177.html) ... most of the vote were +1 and I thought it was going to be released soon. Also in JIRA (http://jira.codehaus.org/secure/IssueNavigator.jspa? reset=truepid=10500fixfor=12294) I don't see any open issue for Maven 2.0.5. What are you waiting to release maven 2.0.5?, have you found a critical bug that need to be fixed before release? if any, can you, please, list the open bugs in JIRA? Keep on doing the great work, thanks, Federico -- View this message in context: http://www.nabble.com/Maven-2.0.5--- open-bugs--tf3100600s177.html#a8605883 Sent from the Maven Developers mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven 2.0.5 - open bugs?
Jason, what about the issues I had when testing version 2.0.5, and for which I sent you a project that reproduces one of the bug? (transitive dependency resolution problem and checkstyle plugin failure). Did you identify them as real issues and postponed them to 2.0.6? Or maybe found they weren't real problems? Fabrice. On 1/25/07, Jason van Zyl [EMAIL PROTECTED] wrote: There is one issue which Trygve raised which I thought he assigned to 2.0.5. It is the issue where Maven is trying to continually try to find snapshots instead of only checking daily. I am done with my crunch at a client this week so I'll call the vote tomorrow afternoon. Jason. On 25 Jan 07, at 4:36 AM 25 Jan 07, Federico Yankelevich wrote: Hi, few days ago there was a lot of interest in a thread calling a vote for releasing maven 2.0.5 (http://www.nabble.com/-VOTE--Release-Maven-2.0.5- tf2966962s177.html) ... most of the vote were +1 and I thought it was going to be released soon. Also in JIRA (http://jira.codehaus.org/secure/IssueNavigator.jspa? reset=truepid=10500fixfor=12294) I don't see any open issue for Maven 2.0.5. What are you waiting to release maven 2.0.5?, have you found a critical bug that need to be fixed before release? if any, can you, please, list the open bugs in JIRA? Keep on doing the great work, thanks, Federico -- View this message in context: http://www.nabble.com/Maven-2.0.5--- open-bugs--tf3100600s177.html#a8605883 Sent from the Maven Developers mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Jira down ?
JIRA works fine for me, even if it's a bit slow... As for the repository, you can use the following URL: http://repo1.maven.org/maven2/ Fabrice. On 1/23/07, Julien HENRY [EMAIL PROTECTED] wrote: Hi everyone, I can't access Jira anymore (http://jira.codehaus.org/), nor ibiblio ( http://ibiblio.org/maven2). Do you know if something is broken? Thanks Julien ___ Découvrez une nouvelle façon d'obtenir des réponses à toutes vos questions ! Profitez des connaissances, des opinions et des expériences des internautes sur Yahoo! Questions/Réponses http://fr.answers.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Release Maven 2.0.5
Hi Jason, I've just tested Maven 2.0.5 on complex projects, and I've had 2 problems who broke the builds. The first is about dependency resolution. In the dependency tree of one of my projects, I have 2 versions of the same lib at the same depth: version 3.1 and 2.1. With Maven 2.0.4, version 3.1 is selected for compiling and testing, which is what I want. With Maven 2.0.5, version 2.1 is selected, which breaks my unit tests because the code requires version 3.1 to run. I'm not sure if this is a bug or not - maybe this resolution principle was to be the default behaviour, but the fact is that there's a difference between 2.0.4 and 2.0.5. I've looked (quickly) into JIRA roadmap, but haven't found any fixed issue related to that. I had the second problem when executing the Checkstyle plugin (version 2.1). So I dug a bit to see if this could be related to maven core or not, and here is what I found. I isolated the code that breaks the build in the checkstyle plugin: it happens when the plugin tries to load my Checkstyle configuration file, which is actually located in a JAR that is specified in the build extensions. The code lies in the Locator#resolveLocation() method: *// Attempt a Resource. * URL url = *this*.getClass().getClassLoader().getResource( location ); This code returns null for the url variable, which in turns breaks the plugin because it doesn't find any configuration file. I haven't had the time to dig more into it, but I found the following issue that might be related to this problem: MNG-2228 : Classloader problem loading jars from build extensionshttp://jira.codehaus.org/browse/MNG-2228. Brett and Carlos worked on it and fixed it, so maybe they could tell more about it. Apart from that, everything else works perfectly. Maybe some of us can tell a bit more about those problems? Cheers, Fabrice. On 1/12/07, Jason van Zyl [EMAIL PROTECTED] wrote: Hi, The entire release is staged here: http://people.apache.org/~jvanzyl/maven-2.0.5/ The assemblies that people are interested in are staged here: http://people.apache.org/~jvanzyl/maven-2.0.5/org/apache/maven/maven- core/2.0.5/ Here is the JIRA roadmap: http://jira.codehaus.org/secure/IssueNavigator.jspa? reset=truepid=10500fixfor=12294sorter/field=issuekeysorter/ order=DESC That's about it. Play around with it, if there are things wrong and I'll fix stuff. We haven't released in so long there very well may be some problems. We should probably let it sit until Tuesday as most folks won't try it out over the weekend. +1 Thanks, Jason. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
