Re: Setting goals for upcoming releases
On Fri, Sep 3, 2010 at 10:58 PM, Jason van Zyl wrote: > I write up a blog entry with the schedule and goals. > > i'll mention the construction if ITs and point to some examples. These will be greatly appreciated. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Maven 3 goals for release questions
On Fri, Sep 3, 2010 at 5:16 PM, Stephen Connolly wrote: > On 3 September 2010 01:38, Barrie Treloar wrote: >> Automatic Plugin Version Resolution >> >> Now that plugin versions are expected to be locked down in the pom >> has the documentation been updated to describe how to manage the >> version upgrades? >> For example there was a question on the list a while ago about a >> tool to check whether new versions of dependencies were available and >> to provide a report. >> > > mvn versions:display-dependency-updates > >> Something like that for plugins would also be needed. The benefit >> > > mvn versions:display-plugin-updates > Cheers, I guess I'm also asking is this documented somewhere, perhaps with some wisdom on why its important and the scenarios of how/when to upgrade. I know enough to be dangerous but I don't consider myself a build management expert, otherwise I'd write it. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Apache Maven 3.0-beta-3 (take 2)
+1 Vincent 2010/8/30 Benjamin Bentmann : > Hi, > > what's a better start for a week than a new fresh release :-) ? So here we > go! > > Apart from another few regression fixes, this release includes Guice and > Aether [0] and shall help to get some more community testing on these new > components. > > Overall, we solved 19 issues: > http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=16681 > > There are still a couple of issues left in JIRA: > http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=10500&status=1 > > Staging repo: > https://repository.apache.org/content/repositories/maven-157/ > > Staged source and binary distros: > https://repository.apache.org/content/repositories/maven-157/org/apache/maven/apache-maven/3.0-beta-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 > > > [0] http://github.com/sonatype/sonatype-aether > > - > 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: Setting goals for upcoming releases
What I meant was to release maven 3.0, the dev needs to iron up most of to backward compatibility blocking bugs. ( no work around ) The bug I mentioned sound like a feature that is accidentally take out of maven core which supports flat repository structure. -Dan On Fri, Sep 3, 2010 at 6:28 AM, Jason van Zyl wrote: > I write up a blog entry with the schedule and goals. > > i'll mention the construction if ITs and point to some examples. > > On Sep 3, 2010, at 9:10 AM, Brian Fox wrote: > >> On Thu, Sep 2, 2010 at 8:44 PM, Jason van Zyl wrote: >>> I think trying to release 3.0 sooner, and then sticking to 6 week release >>> cycles would be a better use of time. We're going to fix anything that >>> arises but I don't believe there will be widespread testing until 3.0 is >>> released, and I don't believe many will pick up 3.x in large-scale >>> production environments until 3.1. I think the faster we get 3.0 out the >>> better. >>> >>> Shoot for October 1st, and then have the 3.0.1 release with fixes for the >>> first wave of issues raised in mid-November. >>> >> >> Fine with me. Then lets announce that intention to the user list now >> and get the page updated to make it easy for people to find the betas. >> >> >>> On Sep 2, 2010, at 7:34 PM, Brian Fox wrote: >>> Now that Maven 3 beta 3 is out with Guice and Aether, we can pretty safely call it feature complete. I'd like to propose a few goals to get some things done. We have ApacheCon coming up the first week of November, and it would be great to set that as a target to get Maven 3.0 out the door. So far the feedback on the betas has been good but fairly limited. I think that without a clear plan, and our history with this mammoth release, people are probably reluctant to spend a lot of time testing each beta. In the past we've been successful pushing out release candidate builds and involving the user list. If we start that soonish, there should be plenty of time to uncover and fix regressions, especially if everyone pitches in. There's even time to cut another beta before we launch into the RCs if it's needed. So first of all, Benjamin, Herve, Kristian you've collectively done the majority of the work in M3 recently. Do you think the above is achievable and desirable? What does everyone else think? Secondly, For me personally, I'm going to commit to get the Maven Index code committed and to push updated releases of the dependency and enforcer plugins before ApacheCon. Anyone else want to ante up for some chunk of work and get things rolling? Thanks, Brian - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org >>> >>> Thanks, >>> >>> Jason >>> >>> -- >>> Jason van Zyl >>> Founder, Apache Maven >>> http://twitter.com/jvanzyl >>> - >>> >>> You are never dedicated to something you have complete confidence in. >>> No one is fanatically shouting that the sun is going to rise tomorrow. >>> They know it is going to rise tomorrow. When people are fanatically >>> dedicated to political or religious faiths or any other kind of >>> dogmas or goals, it's always because these dogmas or >>> goals are in doubt. >>> >>> -- Robert Pirzig, Zen and the Art of Motorcycle Maintenance >>> >>> >>> >>> >> >> - >> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org >> For additional commands, e-mail: dev-h...@maven.apache.org >> > > Thanks, > > Jason > > -- > Jason van Zyl > Founder, Apache Maven > http://twitter.com/jvanzyl > - > > We all have problems. How we deal with them is a measure of our worth. > > -- Unknown > > > > - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Setting goals for upcoming releases
I write up a blog entry with the schedule and goals. i'll mention the construction if ITs and point to some examples. On Sep 3, 2010, at 9:10 AM, Brian Fox wrote: > On Thu, Sep 2, 2010 at 8:44 PM, Jason van Zyl wrote: >> I think trying to release 3.0 sooner, and then sticking to 6 week release >> cycles would be a better use of time. We're going to fix anything that >> arises but I don't believe there will be widespread testing until 3.0 is >> released, and I don't believe many will pick up 3.x in large-scale >> production environments until 3.1. I think the faster we get 3.0 out the >> better. >> >> Shoot for October 1st, and then have the 3.0.1 release with fixes for the >> first wave of issues raised in mid-November. >> > > Fine with me. Then lets announce that intention to the user list now > and get the page updated to make it easy for people to find the betas. > > >> On Sep 2, 2010, at 7:34 PM, Brian Fox wrote: >> >>> Now that Maven 3 beta 3 is out with Guice and Aether, we can pretty >>> safely call it feature complete. I'd like to propose a few goals to >>> get some things done. We have ApacheCon coming up the first week of >>> November, and it would be great to set that as a target to get Maven >>> 3.0 out the door. >>> >>> So far the feedback on the betas has been good but fairly limited. I >>> think that without a clear plan, and our history with this mammoth >>> release, people are probably reluctant to spend a lot of time testing >>> each beta. In the past we've been successful pushing out release >>> candidate builds and involving the user list. If we start that >>> soonish, there should be plenty of time to uncover and fix >>> regressions, especially if everyone pitches in. There's even time to >>> cut another beta before we launch into the RCs if it's needed. >>> >>> So first of all, Benjamin, Herve, Kristian you've collectively done >>> the majority of the work in M3 recently. Do you think the above is >>> achievable and desirable? What does everyone else think? >>> >>> Secondly, For me personally, I'm going to commit to get the Maven >>> Index code committed and to push updated releases of the dependency >>> and enforcer plugins before ApacheCon. Anyone else want to ante up for >>> some chunk of work and get things rolling? >>> >>> Thanks, >>> Brian >>> >>> - >>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org >>> For additional commands, e-mail: dev-h...@maven.apache.org >>> >> >> Thanks, >> >> Jason >> >> -- >> Jason van Zyl >> Founder, Apache Maven >> http://twitter.com/jvanzyl >> - >> >> You are never dedicated to something you have complete confidence in. >> No one is fanatically shouting that the sun is going to rise tomorrow. >> They know it is going to rise tomorrow. When people are fanatically >> dedicated to political or religious faiths or any other kind of >> dogmas or goals, it's always because these dogmas or >> goals are in doubt. >> >> -- Robert Pirzig, Zen and the Art of Motorcycle Maintenance >> >> >> >> > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl - We all have problems. How we deal with them is a measure of our worth. -- Unknown
Re: Fwd: [maven-release-plugin] Is it possible to configure maven-release-plugin to NOT pull in META-INF/LICENSE and NOTICE
On Friday 03 September 2010 2:34:00 am han hongfang wrote: > Forward to dev list to see if somebody has some advice for me on this > question. It's not the release plugin, it's the remote-resources plugin generating them. You would need to figure out where the remote-resources thing is configured. You don't mention which project, but if it's and Apache project using the Apache parent pom, that would be pulled in automatically. Th easy fix is to rename your files to LICENSE and and NOTICE. remote- resources will not overwrite new files if existing files exist. Dan > > Best regards, > > Han Hong Fang > > -- Forwarded message -- > From: han hongfang > Date: Fri, Aug 27, 2010 at 5:27 PM > Subject: [maven-release-plugin] Is it possible to configure > maven-release-plugin to NOT pull in META-INF/LICENSE and NOTICE > To: us...@maven.apache.org > > > > Hi, > > Our project uses maven-release-plugin in the release process. We maintain > the LICENSE.txt and NOTICE.txt (which contains module specifc statement) > for each of our modules in subversion. When we issue mvn release:prepare, > standard LICENSE and NOTICE files are pulled into META-INF folder of > target artifact. These standard files are duplicated with LICENSE.txt and > NOTICE.txt we maintained. > > Is it possible to configure maven-release-plugin to not pull in these > files? If yes, could you show me how to do it? > > Thanks in advance for your reply! -- Daniel Kulp dk...@apache.org http://dankulp.com/blog - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Setting goals for upcoming releases
It's not changing at this point. On Sep 3, 2010, at 9:14 AM, Paul Benedict wrote: > What are the plans for the .m2 user directory? I understand keeping it > for migration purposes, but maybe you want to bring back .mvn (so it > doesn't need to change per version). > > Paul > > On Fri, Sep 3, 2010 at 8:10 AM, Brian Fox wrote: >> On Thu, Sep 2, 2010 at 8:44 PM, Jason van Zyl wrote: >>> I think trying to release 3.0 sooner, and then sticking to 6 week release >>> cycles would be a better use of time. We're going to fix anything that >>> arises but I don't believe there will be widespread testing until 3.0 is >>> released, and I don't believe many will pick up 3.x in large-scale >>> production environments until 3.1. I think the faster we get 3.0 out the >>> better. >>> >>> Shoot for October 1st, and then have the 3.0.1 release with fixes for the >>> first wave of issues raised in mid-November. >>> >> >> Fine with me. Then lets announce that intention to the user list now >> and get the page updated to make it easy for people to find the betas. >> >> >>> On Sep 2, 2010, at 7:34 PM, Brian Fox wrote: >>> Now that Maven 3 beta 3 is out with Guice and Aether, we can pretty safely call it feature complete. I'd like to propose a few goals to get some things done. We have ApacheCon coming up the first week of November, and it would be great to set that as a target to get Maven 3.0 out the door. So far the feedback on the betas has been good but fairly limited. I think that without a clear plan, and our history with this mammoth release, people are probably reluctant to spend a lot of time testing each beta. In the past we've been successful pushing out release candidate builds and involving the user list. If we start that soonish, there should be plenty of time to uncover and fix regressions, especially if everyone pitches in. There's even time to cut another beta before we launch into the RCs if it's needed. So first of all, Benjamin, Herve, Kristian you've collectively done the majority of the work in M3 recently. Do you think the above is achievable and desirable? What does everyone else think? Secondly, For me personally, I'm going to commit to get the Maven Index code committed and to push updated releases of the dependency and enforcer plugins before ApacheCon. Anyone else want to ante up for some chunk of work and get things rolling? Thanks, Brian - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org >>> >>> Thanks, >>> >>> Jason >>> >>> -- >>> Jason van Zyl >>> Founder, Apache Maven >>> http://twitter.com/jvanzyl >>> - >>> >>> You are never dedicated to something you have complete confidence in. >>> No one is fanatically shouting that the sun is going to rise tomorrow. >>> They know it is going to rise tomorrow. When people are fanatically >>> dedicated to political or religious faiths or any other kind of >>> dogmas or goals, it's always because these dogmas or >>> goals are in doubt. >>> >>> -- Robert Pirzig, Zen and the Art of Motorcycle Maintenance >>> >>> >>> >>> >> >> - >> 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 > Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl - You are never dedicated to something you have complete confidence in. No one is fanatically shouting that the sun is going to rise tomorrow. They know it is going to rise tomorrow. When people are fanatically dedicated to political or religious faiths or any other kind of dogmas or goals, it's always because these dogmas or goals are in doubt. -- Robert Pirzig, Zen and the Art of Motorcycle Maintenance
Re: Setting goals for upcoming releases
What are the plans for the .m2 user directory? I understand keeping it for migration purposes, but maybe you want to bring back .mvn (so it doesn't need to change per version). Paul On Fri, Sep 3, 2010 at 8:10 AM, Brian Fox wrote: > On Thu, Sep 2, 2010 at 8:44 PM, Jason van Zyl wrote: >> I think trying to release 3.0 sooner, and then sticking to 6 week release >> cycles would be a better use of time. We're going to fix anything that >> arises but I don't believe there will be widespread testing until 3.0 is >> released, and I don't believe many will pick up 3.x in large-scale >> production environments until 3.1. I think the faster we get 3.0 out the >> better. >> >> Shoot for October 1st, and then have the 3.0.1 release with fixes for the >> first wave of issues raised in mid-November. >> > > Fine with me. Then lets announce that intention to the user list now > and get the page updated to make it easy for people to find the betas. > > >> On Sep 2, 2010, at 7:34 PM, Brian Fox wrote: >> >>> Now that Maven 3 beta 3 is out with Guice and Aether, we can pretty >>> safely call it feature complete. I'd like to propose a few goals to >>> get some things done. We have ApacheCon coming up the first week of >>> November, and it would be great to set that as a target to get Maven >>> 3.0 out the door. >>> >>> So far the feedback on the betas has been good but fairly limited. I >>> think that without a clear plan, and our history with this mammoth >>> release, people are probably reluctant to spend a lot of time testing >>> each beta. In the past we've been successful pushing out release >>> candidate builds and involving the user list. If we start that >>> soonish, there should be plenty of time to uncover and fix >>> regressions, especially if everyone pitches in. There's even time to >>> cut another beta before we launch into the RCs if it's needed. >>> >>> So first of all, Benjamin, Herve, Kristian you've collectively done >>> the majority of the work in M3 recently. Do you think the above is >>> achievable and desirable? What does everyone else think? >>> >>> Secondly, For me personally, I'm going to commit to get the Maven >>> Index code committed and to push updated releases of the dependency >>> and enforcer plugins before ApacheCon. Anyone else want to ante up for >>> some chunk of work and get things rolling? >>> >>> Thanks, >>> Brian >>> >>> - >>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org >>> For additional commands, e-mail: dev-h...@maven.apache.org >>> >> >> Thanks, >> >> Jason >> >> -- >> Jason van Zyl >> Founder, Apache Maven >> http://twitter.com/jvanzyl >> - >> >> You are never dedicated to something you have complete confidence in. >> No one is fanatically shouting that the sun is going to rise tomorrow. >> They know it is going to rise tomorrow. When people are fanatically >> dedicated to political or religious faiths or any other kind of >> dogmas or goals, it's always because these dogmas or >> goals are in doubt. >> >> -- Robert Pirzig, Zen and the Art of Motorcycle Maintenance >> >> >> >> > > - > 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: Setting goals for upcoming releases
On Thu, Sep 2, 2010 at 8:44 PM, Jason van Zyl wrote: > I think trying to release 3.0 sooner, and then sticking to 6 week release > cycles would be a better use of time. We're going to fix anything that arises > but I don't believe there will be widespread testing until 3.0 is released, > and I don't believe many will pick up 3.x in large-scale production > environments until 3.1. I think the faster we get 3.0 out the better. > > Shoot for October 1st, and then have the 3.0.1 release with fixes for the > first wave of issues raised in mid-November. > Fine with me. Then lets announce that intention to the user list now and get the page updated to make it easy for people to find the betas. > On Sep 2, 2010, at 7:34 PM, Brian Fox wrote: > >> Now that Maven 3 beta 3 is out with Guice and Aether, we can pretty >> safely call it feature complete. I'd like to propose a few goals to >> get some things done. We have ApacheCon coming up the first week of >> November, and it would be great to set that as a target to get Maven >> 3.0 out the door. >> >> So far the feedback on the betas has been good but fairly limited. I >> think that without a clear plan, and our history with this mammoth >> release, people are probably reluctant to spend a lot of time testing >> each beta. In the past we've been successful pushing out release >> candidate builds and involving the user list. If we start that >> soonish, there should be plenty of time to uncover and fix >> regressions, especially if everyone pitches in. There's even time to >> cut another beta before we launch into the RCs if it's needed. >> >> So first of all, Benjamin, Herve, Kristian you've collectively done >> the majority of the work in M3 recently. Do you think the above is >> achievable and desirable? What does everyone else think? >> >> Secondly, For me personally, I'm going to commit to get the Maven >> Index code committed and to push updated releases of the dependency >> and enforcer plugins before ApacheCon. Anyone else want to ante up for >> some chunk of work and get things rolling? >> >> Thanks, >> Brian >> >> - >> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org >> For additional commands, e-mail: dev-h...@maven.apache.org >> > > Thanks, > > Jason > > -- > Jason van Zyl > Founder, Apache Maven > http://twitter.com/jvanzyl > - > > You are never dedicated to something you have complete confidence in. > No one is fanatically shouting that the sun is going to rise tomorrow. > They know it is going to rise tomorrow. When people are fanatically > dedicated to political or religious faiths or any other kind of > dogmas or goals, it's always because these dogmas or > goals are in doubt. > > -- Robert Pirzig, Zen and the Art of Motorcycle Maintenance > > > > - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Welcome Kristian Rosenvold to the Maven PMC
Woo hoo! On Sep 2, 2010, at 7:19 PM, Brian Fox wrote: > This is a little delayed, but still deserved. A few weeks ago, > Kristian joined us on the Maven PMC. He's been driving a lot of > interesting work in Maven 3 to support parallel builds. If you haven't > tried that out yet, please do and send some feedback. > > Welcome Kristian! > > --Brian Fox > Maven PMC Chair > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl - happiness is like a butterfly: the more you chase it, the more it will elude you, but if you turn your attention to other things, it will come and sit softly on your shoulder ... -- Thoreau
Re: Setting goals for upcoming releases
On Sep 2, 2010, at 11:46 PM, Dan Tran wrote: > I think i agree with Jason on shooting maven 3.0 out to public as soon > as you can, however the dev team might want fix up blocking bugs which > prevent user like me from using maven 3 > > one of the blocking bug for me is http://jira.codehaus.org/browse/MNG-4788 > Benjamin has done an enormous amount of testing in plugins, and we told people over 6 months ago that if they wanted to be prepared for 3.0 then start writing ITs for their plugins as we suggested. We can't write ITs for every plugin that exists. There was plenty of warning. If you want to make sure your plugin works with Maven 3.x then get some ITs in place and then we will help you wire your tests into the grid. We should probably publicize this now. As good ITs in plugins only help us find regressions, but we can't write tests for everything. > Thanks > > -Dan > > On Thu, Sep 2, 2010 at 6:12 PM, Mark Derricutt wrote: >> Personally I'd still like to see some resolution to the problems introduced >> by the version range resolution change ( no more -SNAPSHOT resolution except >> for on the bounds ). >> >> On one hand I applaud the change from a release standpoint, but it currently >> causes issues for our integration build processes. >> >> Two options come to mind: >> >> 1) Explicit GAV patterns for -SNAPSHOT resolution get defined somewhere >> 2) If a GAV is a particpant in a reactor build, it's -SNAPSHOT should be >> considered kosher for resolution >> >> Option 1 would probably require some form of POM change as I don't think the >> resolution part of a configurable plugin, so most likely can't be done. >> >> Option 2 should be fine, as when releasing an individual artifact, nothing >> external would be in the reactor, unless it was part of the build chain, so >> no extraneous -SNAPSHOTs would be considered. This should give a fairly >> good compromise between "fixing ranges for release" and "not breaking >> existing builds". >> >> Each time I've brought the subject up I don't seem to see any traction or >> replies/discussion come along, is there room to address this somehow? >> >> -- >> Pull me down under... >> >> On Fri, Sep 3, 2010 at 11:34 AM, Brian Fox wrote: >> >>> Now that Maven 3 beta 3 is out with Guice and Aether, we can pretty >>> safely call it feature complete. I'd like to propose a few goals to >>> get some things done. We have ApacheCon coming up the first week of >>> November, and it would be great to set that as a target to get Maven >>> 3.0 out the door. >>> >> > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl - A man enjoys his work when he understands the whole and when he is responsible for the quality of the whole -- Christopher Alexander, A Pattern Language
Re: Welcome Kristian Rosenvold to the Maven PMC
Congrats Kristian! On Fri, Sep 3, 2010 at 1:19 AM, Brian Fox wrote: > This is a little delayed, but still deserved. A few weeks ago, > Kristian joined us on the Maven PMC. He's been driving a lot of > interesting work in Maven 3 to support parallel builds. If you haven't > tried that out yet, please do and send some feedback. > > Welcome Kristian! > > --Brian Fox > Maven PMC Chair > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > >
Re: Setting goals for upcoming releases
+1 On 3 September 2010 01:44, Jason van Zyl wrote: > I think trying to release 3.0 sooner, and then sticking to 6 week release > cycles would be a better use of time. We're going to fix anything that > arises but I don't believe there will be widespread testing until 3.0 is > released, and I don't believe many will pick up 3.x in large-scale > production environments until 3.1. I think the faster we get 3.0 out the > better. > > Shoot for October 1st, and then have the 3.0.1 release with fixes for the > first wave of issues raised in mid-November. > > On Sep 2, 2010, at 7:34 PM, Brian Fox wrote: > > > Now that Maven 3 beta 3 is out with Guice and Aether, we can pretty > > safely call it feature complete. I'd like to propose a few goals to > > get some things done. We have ApacheCon coming up the first week of > > November, and it would be great to set that as a target to get Maven > > 3.0 out the door. > > > > So far the feedback on the betas has been good but fairly limited. I > > think that without a clear plan, and our history with this mammoth > > release, people are probably reluctant to spend a lot of time testing > > each beta. In the past we've been successful pushing out release > > candidate builds and involving the user list. If we start that > > soonish, there should be plenty of time to uncover and fix > > regressions, especially if everyone pitches in. There's even time to > > cut another beta before we launch into the RCs if it's needed. > > > > So first of all, Benjamin, Herve, Kristian you've collectively done > > the majority of the work in M3 recently. Do you think the above is > > achievable and desirable? What does everyone else think? > > > > Secondly, For me personally, I'm going to commit to get the Maven > > Index code committed and to push updated releases of the dependency > > and enforcer plugins before ApacheCon. Anyone else want to ante up for > > some chunk of work and get things rolling? > > > > Thanks, > > Brian > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > > For additional commands, e-mail: dev-h...@maven.apache.org > > > > Thanks, > > Jason > > -- > Jason van Zyl > Founder, Apache Maven > http://twitter.com/jvanzyl > - > > You are never dedicated to something you have complete confidence in. > No one is fanatically shouting that the sun is going to rise tomorrow. > They know it is going to rise tomorrow. When people are fanatically > dedicated to political or religious faiths or any other kind of > dogmas or goals, it's always because these dogmas or > goals are in doubt. > > -- Robert Pirzig, Zen and the Art of Motorcycle Maintenance > > > >
Re: Maven 3 goals for release questions
On 3 September 2010 01:38, Barrie Treloar wrote: > I didn't want to hijack the other thread with my questions after > reading https://cwiki.apache.org/MAVEN/maven-3x-compatibility-notes.html > > Caching of Artifact Resolution Errors > > Marker files are great! Is there any documentation on what they > are? The maven-eclipse-plugin has the hack I added with marker files. > Standardizing on the marker file will be the first thing I do once I > know what do use. > > Automatic Plugin Version Resolution > > Now that plugin versions are expected to be locked down in the pom > has the documentation been updated to describe how to manage the > version upgrades? > For example there was a question on the list a while ago about a > tool to check whether new versions of dependencies were available and > to provide a report. > mvn versions:display-dependency-updates > Something like that for plugins would also be needed. The benefit > mvn versions:display-plugin-updates > of not locking them down was I got the latest releases without doing > anything. > The downside was the build was not reproducible and if the new > plugin had bugs I would need to lock down the plugin to the previous > working version. > Some guidance on how to manage this lifecyle would be appreciated by > less experienced build managers. > > Plugin Repositories > "Maven 3 aims at supporting a stricter > separation between the compile/runtime/test dependencies" > > Has the > http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html > > Dependency Scope been modified to define "test compile" and "test > runtime"? > Without something like this dependency:analyze has false positives > with test scopes and a lot of the benefit of checking is lost. > Is this possible and on the feature list? > > Cheers > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > >
Re: Setting goals for upcoming releases
+1 On Fri, Sep 3, 2010 at 2:44 AM, Jason van Zyl wrote: > I think trying to release 3.0 sooner, and then sticking to 6 week release > cycles would be a better use of time. We're going to fix anything that > arises but I don't believe there will be widespread testing until 3.0 is > released, and I don't believe many will pick up 3.x in large-scale > production environments until 3.1. I think the faster we get 3.0 out the > better. > > Shoot for October 1st, and then have the 3.0.1 release with fixes for the > first wave of issues raised in mid-November. > > On Sep 2, 2010, at 7:34 PM, Brian Fox wrote: > > > Now that Maven 3 beta 3 is out with Guice and Aether, we can pretty > > safely call it feature complete. I'd like to propose a few goals to > > get some things done. We have ApacheCon coming up the first week of > > November, and it would be great to set that as a target to get Maven > > 3.0 out the door. > > > > So far the feedback on the betas has been good but fairly limited. I > > think that without a clear plan, and our history with this mammoth > > release, people are probably reluctant to spend a lot of time testing > > each beta. In the past we've been successful pushing out release > > candidate builds and involving the user list. If we start that > > soonish, there should be plenty of time to uncover and fix > > regressions, especially if everyone pitches in. There's even time to > > cut another beta before we launch into the RCs if it's needed. > > > > So first of all, Benjamin, Herve, Kristian you've collectively done > > the majority of the work in M3 recently. Do you think the above is > > achievable and desirable? What does everyone else think? > > > > Secondly, For me personally, I'm going to commit to get the Maven > > Index code committed and to push updated releases of the dependency > > and enforcer plugins before ApacheCon. Anyone else want to ante up for > > some chunk of work and get things rolling? > > > > Thanks, > > Brian > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > > For additional commands, e-mail: dev-h...@maven.apache.org > > > > Thanks, > > Jason > > -- > Jason van Zyl > Founder, Apache Maven > http://twitter.com/jvanzyl > - > > You are never dedicated to something you have complete confidence in. > No one is fanatically shouting that the sun is going to rise tomorrow. > They know it is going to rise tomorrow. When people are fanatically > dedicated to political or religious faiths or any other kind of > dogmas or goals, it's always because these dogmas or > goals are in doubt. > > -- Robert Pirzig, Zen and the Art of Motorcycle Maintenance > > > >
Fwd: [maven-release-plugin] Is it possible to configure maven-release-plugin to NOT pull in META-INF/LICENSE and NOTICE
Forward to dev list to see if somebody has some advice for me on this question. Best regards, Han Hong Fang -- Forwarded message -- From: han hongfang Date: Fri, Aug 27, 2010 at 5:27 PM Subject: [maven-release-plugin] Is it possible to configure maven-release-plugin to NOT pull in META-INF/LICENSE and NOTICE To: us...@maven.apache.org Hi, Our project uses maven-release-plugin in the release process. We maintain the LICENSE.txt and NOTICE.txt (which contains module specifc statement) for each of our modules in subversion. When we issue mvn release:prepare, standard LICENSE and NOTICE files are pulled into META-INF folder of target artifact. These standard files are duplicated with LICENSE.txt and NOTICE.txt we maintained. Is it possible to configure maven-release-plugin to not pull in these files? If yes, could you show me how to do it? Thanks in advance for your reply! -- Best regards, Han Hong Fang -- Best regards, Han Hong Fang
