Re: [vote] release maven-release-1 parent and maven-release-manager-1.0-alpha-1
+1 Stéphane On 4/13/07, Jesse McConnell [EMAIL PROTECTED] wrote: With maven-scm having its latest release underway, the final linchpin in getting alpha releases of continuum up and running is the maven-release and maven-release-manager. So I am calling a vote to get the maven-release parent pom released and the maven-release-manager which the continuum-release module makes use of as well as the maven-release-plugin which is _not_ under the purview of this vote. In Staging Repo: http://people.apache.org/~jmcconnell/org/apache/maven/release Tags: http://svn.apache.org/repos/asf/maven/release/tags/ Anyway, lets try this and see how it goes: 72 hrs +1/0/-1. Cast away! :) jesse +1 from me... -- jesse mcconnell [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: Remove auto-resolution of plugin versions from Maven 2.1
On 4/14/07, ArneD [EMAIL PROTECTED] wrote: 2. Many users don't want to make a distinction between Maven itself and the Maven core plugins (compile, jar, ...). This also not true in my experience. Core plugins are not distributed with Maven because we have consciously decoupled the lifecycle of plugins from the core because any plugins we house here may, in fact, be release two or three times between major releases of Maven and binding these versions in the core would be a bad idea. Well, why not release Maven more often then? For those who need a freshly released plugin version urgently, there still could be an override mechanism. Eclipse.org makes coordinated releases of many sub-projects. The sub-projects do have an independent lifecycle, but there are coordinated schedules when bundles are published. So each user knows: Every June there's a new major Eclipse release, and between these releases there's a public visible schedule when new Milestone releases are published. I think the only reason Eclipse can get away with this approach is because IBM are funding a large proportion of the development efforts with Eclipse. Maven doesn't have that kind of cash backing to see this happen. I agree with the points you are raising. I think the cop out answer will be that Maven is open source and that if these features are wanted enough then someone needs to scratch the itch and come up with a solution. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Remove auto-resolution of plugin versions from Maven 2.1
Brett Porter wrote: I think it's more complicated than just removing that. Firstly, large numbers of command line plugins will stop working. Secondly, we need to provide a solution for implied plugins (we can set the version in the lifecycle and then let the user give pluginManagement to override it, but I'd like to see plugin 'packs' as a better solution to reduce the amount of configuration needed). Thirdly, we need to think carefully about the impact on existing builds. We're not just impacting the people that wrote the build - we impact the random people that grab a project and unwittingly try and build it with 2.1 not knowing the author never tested that, and get the bad experience. I'm still in favour of a compatibility mode that can be driven by the prerequisites or the modelVersion. I say let people use the dependency plugin now to start fixing their builds, but for 2.1 let them make the conscious decision to move up to this. I've talked about this before and I still mean that Maven should have a prerequisite flag for Maven version as you're saying. -- Trygve - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Release maven-dependency-tree
+1 Emmanuel Carlos Sanchez a écrit : anyone? On 4/10/07, Carlos Sanchez [EMAIL PROTECTED] wrote: This release adds iterator methods that simplify the tree navigation Right now is set to 1.0-alpha-3 but has been stable for months so I'd go for 1.0-beta-1 or 1.0 https://svn.apache.org/repos/asf/maven/shared/trunk/maven-dependency-tree 527390 Note that it depends on the release of the maven-plugin-testing-harness -- I could give you my word as a Spaniard. No good. I've known too many Spaniards. -- The Princess Bride - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Release Maven-SCM 1.0-rc1
Yes, but before 1.0 final, I'd like SCM-292 fixed because Perforce can't be used with continuum. And we need to document the TCK too and close SCM-17 Emmanuel Carlos Sanchez a écrit : I'd say that if in 1/2 weeks nobody finds critical bugs it should be released final. Non critical bugs can be postponed to 1.0.1 On 4/13/07, John Casey [EMAIL PROTECTED] wrote: +1, though I'm a little curious whether it would be better to simply try to release a 1.0. If this is good enough for a release candidate, and you've staged it where people can try it out, then this candidate could just be pushed out as a final release if nobody reports a problem... How long of a soak period do you feel would be appropriate for this release candidate, before we can be sure it's ready to be -final? -john On 4/13/07, Carlos Sanchez [EMAIL PROTECTED] wrote: +1 On 4/13/07, Emmanuel Venisse [EMAIL PROTECTED] wrote: Hi, I'd like to release Maven SCM 1.0-rc1 This version fix few bugs, add a new provider (mercurial) and few commands. Road Map: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10527styleName=Htmlversion=13066 Site: http://people.apache.org/~evenisse/stage/site/ Staging repo: http://people.apache.org/~evenisse/stage/repo/ Tag: http://svn.apache.org/repos/asf/maven/scm/tags/maven-scm-1.0-rc1/ So, let's try 72h +1/+0/-1. Please cast your votes! Here my +1 Emmanuel -- I could give you my word as a Spaniard. No good. I've known too many Spaniards. -- The Princess Bride
5 plugins do not have module tags in the maven-plugins parent pom
The: maven-enforcer-plugin maven-gpg-plugin maven-invoker-plugin maven-remote-resources-plugin maven-stage-plugin do not have module tags in the maven-plugins parent pom. Patch attached - also removes trailing whitespace from one line, and flips maven-war-plugin and maven-verifier-plugin around so that the list is fully in alphabetic order. Max. Index: pom.xml === --- pom.xml (revision 528800) +++ pom.xml (working copy) @@ -87,9 +87,12 @@ modulemaven-ear-plugin/module modulemaven-eclipse-plugin/module modulemaven-ejb-plugin/module +modulemaven-enforcer-plugin/module +modulemaven-gpg-plugin/module modulemaven-help-plugin/module modulemaven-idea-plugin/module modulemaven-install-plugin/module +modulemaven-invoker-plugin/module modulemaven-jar-plugin/module modulemaven-javadoc-plugin/module modulemaven-one-plugin/module @@ -97,12 +100,14 @@ modulemaven-pmd-plugin/module modulemaven-project-info-reports-plugin/module modulemaven-rar-plugin/module +modulemaven-remote-resources-plugin/module modulemaven-repository-plugin/module modulemaven-resources-plugin/module modulemaven-site-plugin/module -modulemaven-source-plugin/module +modulemaven-source-plugin/module +modulemaven-stage-plugin/module +modulemaven-verifier-plugin/module modulemaven-war-plugin/module -modulemaven-verifier-plugin/module /modules scm connectionscm:svn:http://svn.apache.org/repos/asf/maven/plugins/trunk//connection signature.asc Description: OpenPGP digital signature
RE: 5 plugins do not have module tags in the maven-plugins parent pom
Applied. Thanks Max. -Original Message- From: Max Bowsher [mailto:[EMAIL PROTECTED] Sent: Saturday, April 14, 2007 9:42 AM To: [EMAIL PROTECTED] Subject: 5 plugins do not have module tags in the maven-plugins parent pom The: maven-enforcer-plugin maven-gpg-plugin maven-invoker-plugin maven-remote-resources-plugin maven-stage-plugin do not have module tags in the maven-plugins parent pom. Patch attached - also removes trailing whitespace from one line, and flips maven-war-plugin and maven-verifier-plugin around so that the list is fully in alphabetic order. Max. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[VOTE] Release maven ant plugin 2.0
I'd like to release the maven ant plugin for Maven 2. Last release was a year ago Specially addressed to Vincent Siveton, as he has been the one working more on it. https://svn.apache.org/repos/asf/maven/plugins/trunk/maven-ant-plugin rev# 528823 deployed as 2.0-SNAPSHOT Roadmap http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=11124fixfor=12933 I'd push MANT-22 for the next release -- I could give you my word as a Spaniard. No good. I've known too many Spaniards. -- The Princess Bride - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Common base directory for staging releases
On 4/1/07, Jason van Zyl [EMAIL PROTECTED] wrote:
I wanted to setup a common base directory for staging releases so
that each person doesn't have to change their setting each time they
stage, or use a -D parameter. I would just like to have a commons
base directory and then use information about the project to
construct the staging repository. How about:
http://people.apache.org/staging-repositories/${project}/
Then other projects can do the same, so ours would be:
http://people.apache.org/staging-repositories/maven/
There is already http://people.apache.org/builds/${project}, mentioned
in the release FAQ [1] as being for nightly builds, in practice it's
also used for staging and releases that aren't put on the mirrors for
whatever reason.
And I just change distributionManagementrelease, since I never
want anything deployed directly to the rsynced repo.
[1] http://www.apache.org/dev/release.html
.
--
Wendy
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [vote] release maven-release-1 parent and maven-release-manager-1.0-alpha-1
Jesse McConnell wrote: With maven-scm having its latest release underway, the final linchpin in getting alpha releases of continuum up and running is the maven-release and maven-release-manager. So I am calling a vote to get the maven-release parent pom released and the maven-release-manager which the continuum-release module makes use of as well as the maven-release-plugin which is _not_ under the purview of this vote. In Staging Repo: http://people.apache.org/~jmcconnell/org/apache/maven/release Tags: http://svn.apache.org/repos/asf/maven/release/tags/ Anyway, lets try this and see how it goes: 72 hrs +1/0/-1. Cast away! :) jesse +1 from me... Too late for this release, but could someone take a look at MRELEASE-137 so it gets into the next one? It's a trivial one-liner fix. The attached patch is for maven-release-plugin, but the relevant class has since moved into maven-release-manager. It's obvious how to forward port the single change to the new code. Max. signature.asc Description: OpenPGP digital signature
RE: [VOTE] Release maven ant plugin 2.0
MANT-22 has a patch and it seems pretty trivial. Why not apply it? I don't use mant much so maybe I'm missing something obvious. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Carlos Sanchez Sent: Saturday, April 14, 2007 11:48 AM To: Maven Developers List Subject: [VOTE] Release maven ant plugin 2.0 I'd like to release the maven ant plugin for Maven 2. Last release was a year ago Specially addressed to Vincent Siveton, as he has been the one working more on it. https://svn.apache.org/repos/asf/maven/plugins/trunk/maven-ant-plugin rev# 528823 deployed as 2.0-SNAPSHOT Roadmap http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=11124 fixfor=12933 I'd push MANT-22 for the next release -- I could give you my word as a Spaniard. No good. I've known too many Spaniards. -- The Princess Bride - 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]
