Jira merge versions.
I'd like to merge a few older released versions together in Jira (to help in reducing the noise on some of the reports.) What I'd like to do ... Take versions: * 0.9 * 1.0-alpha-1 * 1.0-alpha-2 * 1.0-beta-1 * 1.0-beta-2 * 1.0-beta-3 * 1.0-beta-4 And merge them into: * 1.0 Any objections? - Joakim
Re: Jira merge versions.
I'm unsure. I'd definitely leave 0.9 out on it's own regardless. I kind of like the idea of merging, but I also hate to irreversibly lose information :) Does archiving the alpha/beta releases achieve what you need? What is the noise in the reports you are referring to? Thanks, Brett On 19/02/2008, at 6:05 AM, Joakim Erdfelt wrote: I'd like to merge a few older released versions together in Jira (to help in reducing the noise on some of the reports.) What I'd like to do ... Take versions: * 0.9 * 1.0-alpha-1 * 1.0-alpha-2 * 1.0-beta-1 * 1.0-beta-2 * 1.0-beta-3 * 1.0-beta-4 And merge them into: * 1.0 Any objections? - Joakim -- Brett Porter [EMAIL PROTECTED] http://blogs.exist.com/bporter/
Re: Jira merge versions.
On Feb 18, 2008 12:05 PM, Joakim Erdfelt [EMAIL PROTECTED] wrote: I'd like to merge a few older released versions together in Jira (to help in reducing the noise on some of the reports.) I don't think issues for 0.9 should be merged into 1.0-- it's a different codebase. -- Wendy
Re: Jira merge versions.
Archiving the version might accomplish the same thing. I see some checkboxes to exclude archived versions in the reports. (heh, still spelling archive wrong) As for reports, I can't find perma-links for most of them. But here's an example: http://urltea.com/2qf2 - Joakim Brett Porter wrote: I'm unsure. I'd definitely leave 0.9 out on it's own regardless. I kind of like the idea of merging, but I also hate to irreversibly lose information :) Does archiving the alpha/beta releases achieve what you need? What is the noise in the reports you are referring to? Thanks, Brett On 19/02/2008, at 6:05 AM, Joakim Erdfelt wrote: I'd like to merge a few older released versions together in Jira (to help in reducing the noise on some of the reports.) What I'd like to do ... Take versions: * 0.9 * 1.0-alpha-1 * 1.0-alpha-2 * 1.0-beta-1 * 1.0-beta-2 * 1.0-beta-3 * 1.0-beta-4 And merge them into: * 1.0 Any objections? - Joakim -- Brett Porter [EMAIL PROTECTED] http://blogs.exist.com/bporter/
Re: Plan to migrate towards Spring?
On Feb 18, 2008 8:23 PM, Joakim Erdfelt [EMAIL PROTECTED] wrote: I've been checking out some performance / scalability / tooling / testing tests recently at my office with regards to web frameworks. SpringMVC beat everything but Struts 1.x in performance. And SpringMVC makes testing really easy to boot. That's my motivation behind it. Yeah... but what are they testing for? The Archiva webapp doesn't need to hold up to thousands of hits a second. :) Struts 2 does have some known performance issues. On the dev list there's a renewed effort to figure out how to get away from OGNL (the prime suspect) and move to a different expression language. But yes, it would have a big impact. So, lets just consider something lower impact, moving from xwork/webwork to Struts 2. I think we have some friends in the struts 2 community to help us out if we hit a roadblock or two. Beside, we should be supporting out Apache brethren too. It's less about using another Apache project than about what the volunteer labor force here wants to work with. Speaking for myself I can't find any motivation to work on the Archiva webapp that uses an old version of WebWork. I'm not that interested in Spring MVC. I'm sure it's fine framework, it's just not the community I want to be involved in. I would welcome the excuse to get more involved at Struts again while working on a Struts 2.1 app though. -- Wendy
Re: svn commit: r628597 - /maven/components/branches/maven-2.0.x/README.txt
Hi Wendy, 2008/2/17, [EMAIL PROTECTED] [EMAIL PROTECTED]: Author: wsmoak Date: Sun Feb 17 18:21:26 2008 New Revision: 628597 URL: http://svn.apache.org/viewvc?rev=628597view=rev Log: Fix example for M2_HOME value. Modified: maven/components/branches/maven-2.0.x/README.txt Modified: maven/components/branches/maven-2.0.x/README.txt URL: http://svn.apache.org/viewvc/maven/components/branches/maven-2.0.x/README.txt?rev=628597r1=628596r2=628597view=diff == --- maven/components/branches/maven-2.0.x/README.txt (original) +++ maven/components/branches/maven-2.0.x/README.txt Sun Feb 17 18:21:26 2008 @@ -10,7 +10,7 @@ export PATH=$PATH:$M2_HOME/bin In addition, the last part of the M2_HOME path MUST be of the form maven-$version, eg: -/usr/local/maven-2.1-SNAPSHOT +/usr/local/apache-maven-2.0.9-SNAPSHOT I think that a generic version would be better, i.e. apache-maven-2.0.x-SNAPSHOT Cheers, Vincent You can set the parameters passed to the Java VM when running Maven2 bootstrap, setting the environment variable MAVEN_OPTS, e.g. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [ANN] Maven Archetype Plugin 2.0-alpha-1 for Maven 2 Released
This new plugin seems to be a great improvement and I welcome the further development. However, i'm not sure if it was intended to be picked up by the whole maven user population? This is because: - There is no backwards compatability, suddenly maven no longer works as it used to - The documentation on the new plugin has lots of broken links in it and is unusable - The archetype guides on the main maven site are now all incorrect Surely all this needed to be fixed before the whole community started using the new plugin? I understand that the plugins are alpha versions and can change, but to suddenly make things alot worse wasn’t a great experience. Apologies for moaning about an improvement to the tool! Rich -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Raphaël Piéroni Sent: 09 February 2008 03:41 To: [EMAIL PROTECTED]; [EMAIL PROTECTED] Cc: dev@maven.apache.org Subject: [ANN] Maven Archetype Plugin 2.0-alpha-1 for Maven 2 Released The Maven team is pleased to announce the release of the Maven Archetype Plugin, version 2.0-alpha-1 You can use it by calling mvn archetype:create Release Notes - Maven 2.x Archetype Plugin - Version 2.0-alpha-1 ** Bug * [ARCHETYPE-82] - add-groups doesn't create archetype.xml * [ARCHETYPE-83] - archetypeng:create crashes with java.lang.ClassNotFoundException: org.apache.maven.plugin.resource.loader.ProjectResourceLoader * [ARCHETYPE-84] - need a way to preserve the java package in create-from-project * [ARCHETYPE-87] - create-from-project replaces too many things in the pom with variables * [ARCHETYPE-88] - sometimes add-groups fails when there is a pom present * [ARCHETYPE-90] - all the contents of an archetype shouldn't be processed by velocity during creation * [ARCHETYPE-91] - create is prompting for a package * [ARCHETYPE-93] - archetypeng:create loop forever when the selected group contains no archetype * [ARCHETYPE-94] - Archetype not registered when installed in local repository * [ARCHETYPE-97] - modules section is missing after using create-from-project * [ARCHETYPE-98] - parents in modules are not always correctly updated * [ARCHETYPE-99] - child module is getting replaced with parent artifactId and groupId * [ARCHETYPE-100] - sibling dependencies are not updated * [ARCHETYPE-103] - acrchetype.properties should be in /target not root * [ARCHETYPE-104] - module name changed for unknown reason * [ARCHETYPE-105] - not able to create from project with sibling-dependencies test project * [ARCHETYPE-121] - build don't works on windows and jdk1.4 ** Improvement * [ARCHETYPE-114] - NG code should not depend on Maven 2.1 ** New Feature * [ARCHETYPE-95] - Provide creation of partial archetypes in create-from-project ** Task * [ARCHETYPE-72] - Generate standard archetypes from real projects Enjoy, -The Maven team - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: svn commit: r628597 - /maven/components/branches/maven-2.0.x/README.txt
On Feb 18, 2008 4:56 AM, Vincent Siveton [EMAIL PROTECTED] wrote: In addition, the last part of the M2_HOME path MUST be of the form maven-$version, eg: -/usr/local/maven-2.1-SNAPSHOT +/usr/local/apache-maven-2.0.9-SNAPSHOT I think that a generic version would be better, i.e. apache-maven-2.0.x-SNAPSHOT That's fine with me. I just changed it from 2.1 to 2.0 because this is on the branch. (And added the apache- prefix, which it complained about when I followed the instructions 'as written'.) -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: atypical plugin use cases
On Feb 17, 2008, at 3:48 PM, Brett Porter wrote: - decent integration of code coverage plugins (we never got this forked lifecycle quite right) Can you shed some more light on this? Do we have specific test cases that we can put into the build? I'll have to read over the rest of your post a little more carefully before I can form a coherent response, but I wanted to ask this before I forgot about it. ;-) Thanks, -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: [ANN] Maven Archetype Plugin 2.0-alpha-1 for Maven 2 Released
On 18-Feb-08, at 4:55 AM, Richard Chamberlain wrote: This new plugin seems to be a great improvement and I welcome the further development. However, i'm not sure if it was intended to be picked up by the whole maven user population? It is as a consequence of Maven auto-updating which we recognize as a problem. The problem has been fixed and we'll get a release out ASAP. This is because: - There is no backwards compatability, suddenly maven no longer works as it used to - The documentation on the new plugin has lots of broken links in it and is unusable - The archetype guides on the main maven site are now all incorrect All will be back to regularly scheduled programming with the alpha-2. Surely all this needed to be fixed before the whole community started using the new plugin? I understand that the plugins are alpha versions and can change, but to suddenly make things alot worse wasn’t a great experience. Apologies for moaning about an improvement to the tool! Rich -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Raphaël Piéroni Sent: 09 February 2008 03:41 To: [EMAIL PROTECTED]; [EMAIL PROTECTED] Cc: dev@maven.apache.org Subject: [ANN] Maven Archetype Plugin 2.0-alpha-1 for Maven 2 Released The Maven team is pleased to announce the release of the Maven Archetype Plugin, version 2.0-alpha-1 You can use it by calling mvn archetype:create Release Notes - Maven 2.x Archetype Plugin - Version 2.0-alpha-1 ** Bug * [ARCHETYPE-82] - add-groups doesn't create archetype.xml * [ARCHETYPE-83] - archetypeng:create crashes with java.lang.ClassNotFoundException: org.apache.maven.plugin.resource.loader.ProjectResourceLoader * [ARCHETYPE-84] - need a way to preserve the java package in create-from-project * [ARCHETYPE-87] - create-from-project replaces too many things in the pom with variables * [ARCHETYPE-88] - sometimes add-groups fails when there is a pom present * [ARCHETYPE-90] - all the contents of an archetype shouldn't be processed by velocity during creation * [ARCHETYPE-91] - create is prompting for a package * [ARCHETYPE-93] - archetypeng:create loop forever when the selected group contains no archetype * [ARCHETYPE-94] - Archetype not registered when installed in local repository * [ARCHETYPE-97] - modules section is missing after using create-from-project * [ARCHETYPE-98] - parents in modules are not always correctly updated * [ARCHETYPE-99] - child module is getting replaced with parent artifactId and groupId * [ARCHETYPE-100] - sibling dependencies are not updated * [ARCHETYPE-103] - acrchetype.properties should be in /target not root * [ARCHETYPE-104] - module name changed for unknown reason * [ARCHETYPE-105] - not able to create from project with sibling-dependencies test project * [ARCHETYPE-121] - build don't works on windows and jdk1.4 ** Improvement * [ARCHETYPE-114] - NG code should not depend on Maven 2.1 ** New Feature * [ARCHETYPE-95] - Provide creation of partial archetypes in create-from-project ** Task * [ARCHETYPE-72] - Generate standard archetypes from real projects Enjoy, -The Maven team - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Thanks, Jason -- Jason van Zyl Founder, Apache Maven jason at sonatype dot com -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
archetype release
Hi, Brett/Raphael I know that both of you talked about doing a release, and if you're around and are going to do it now great. I'll wait an hour, and if neither of you respond I'll start preparing the release. I can live the create-from-archetype not working on Windows. We have to fix the backward compat problem ASAP. Thanks, Jason -- Jason van Zyl Founder, Apache Maven jason at sonatype dot com -- First, the taking in of scattered particulars under one Idea, so that everyone understands what is being talked about ... Second, the separation of the Idea into parts, by dividing it at the joints, as nature directs, not breaking any limb in half as a bad carver might. -- Plato, Phaedrus (Notes on the Synthesis of Form by C. Alexander) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[vote] Benjamin Bentmann as Maven committer
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] Benjamin Bentmann as Maven committer
+1 Ralph 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] Benjamin Bentmann as Maven committer
+1 On 18-Feb-08, at 9:38 AM, 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] Thanks, Jason -- Jason van Zyl Founder, Apache Maven jason at sonatype dot com -- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [vote] Benjamin Bentmann as Maven committer
Definitely +1 Vincent 2008/2/18, Lukas Theussl [EMAIL PROTECTED]: 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] Benjamin Bentmann as Maven committer
+1 Milos 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [vote] Benjamin Bentmann as Maven committer
+1 -- Olivier 2008/2/18, Vincent Siveton [EMAIL PROTECTED]: Definitely +1 Vincent 2008/2/18, Lukas Theussl [EMAIL PROTECTED]: 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: archetype release
I don't object. Raphaël 2008/2/18, Jason van Zyl [EMAIL PROTECTED]: Ok, unless anyone objects I'm going to try and get this thing out. On 18-Feb-08, at 9:29 AM, Jason van Zyl wrote: Hi, Brett/Raphael I know that both of you talked about doing a release, and if you're around and are going to do it now great. I'll wait an hour, and if neither of you respond I'll start preparing the release. I can live the create-from-archetype not working on Windows. We have to fix the backward compat problem ASAP. Thanks, Jason -- Jason van Zyl Founder, Apache Maven jason at sonatype dot com -- First, the taking in of scattered particulars under one Idea, so that everyone understands what is being talked about ... Second, the separation of the Idea into parts, by dividing it at the joints, as nature directs, not breaking any limb in half as a bad carver might. -- Plato, Phaedrus (Notes on the Synthesis of Form by C. Alexander) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Thanks, Jason -- Jason van Zyl Founder, Apache Maven jason at sonatype dot com -- People develop abstractions by generalizing from concrete examples. Every attempt to determine the correct abstraction on paper without actually developing a running system is doomed to failure. No one is that smart. A framework is a resuable design, so you develop it by looking at the things it is supposed to be a design of. The more examples you look at, the more general your framework will be. -- Ralph Johnson Don Roberts, Patterns for Evolving Frameworks - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: archetype release
Ok, unless anyone objects I'm going to try and get this thing out. On 18-Feb-08, at 9:29 AM, Jason van Zyl wrote: Hi, Brett/Raphael I know that both of you talked about doing a release, and if you're around and are going to do it now great. I'll wait an hour, and if neither of you respond I'll start preparing the release. I can live the create-from-archetype not working on Windows. We have to fix the backward compat problem ASAP. Thanks, Jason -- Jason van Zyl Founder, Apache Maven jason at sonatype dot com -- First, the taking in of scattered particulars under one Idea, so that everyone understands what is being talked about ... Second, the separation of the Idea into parts, by dividing it at the joints, as nature directs, not breaking any limb in half as a bad carver might. -- Plato, Phaedrus (Notes on the Synthesis of Form by C. Alexander) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Thanks, Jason -- Jason van Zyl Founder, Apache Maven jason at sonatype dot com -- People develop abstractions by generalizing from concrete examples. Every attempt to determine the correct abstraction on paper without actually developing a running system is doomed to failure. No one is that smart. A framework is a resuable design, so you develop it by looking at the things it is supposed to be a design of. The more examples you look at, the more general your framework will be. -- Ralph Johnson Don Roberts, Patterns for Evolving Frameworks - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [vote] Benjamin Bentmann as Maven committer
+1 -john On Feb 18, 2008, at 12:38 PM, 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] --- 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: Version ranges and snapshots
Well ask us to do something rather than blabber on and we shut up... I lost two managers and a developer which has chewed up all my time... On Thu, 31 Jan 2008 02:14:59 Stephen Connolly wrote: IMHO I think a vote with the two positions clearly identified (perhaps with pros and cons for both if the pair of ye can agree on the pros and cons). (unless somebody else has a third position) -Stephen. On Jan 30, 2008 12:56 PM, Mark Hobson [EMAIL PROTECTED] wrote: On 30/01/2008, Mark Hobson [EMAIL PROTECTED] wrote: I don't think that linking this level of artifact resolution uncertainty to its source repository is a good idea. How version ranges are resolved should be completely deterministic and independent from where the artifact was actually downloaded from, otherwise we'll end up with no end of build reproducibility problems. In addition, the local repository would be exempt from these rules. This would require manually deleting artifacts from the local repo to ensure that certain versions weren't picked up; a maintenance nightmare I'm sure you'll agree. How's best to proceed with resolving this issue? Would voting make sense, or should the PMC lay down the intended direction? I'm not sure whether this thread needs to get any longer.. :) Mark - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Michael McCallum Enterprise Engineer mailto:[EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: atypical plugin use cases
On 19/02/2008, at 3:15 AM, John Casey wrote: On Feb 17, 2008, at 3:48 PM, Brett Porter wrote: - decent integration of code coverage plugins (we never got this forked lifecycle quite right) Can you shed some more light on this? Do we have specific test cases that we can put into the build? Vincent would probably happily give you a list from when he worked on the clover plugin :) Things like: - running the tests twice by necessity - not being able to reuse the enhanced classes easily - lack of consistency between build time checks and reporting It all kind of works, but I generally find configuring it is less pleasant than necessary and less flexible than it could be. I'll have to read over the rest of your post a little more carefully before I can form a coherent response, but I wanted to ask this before I forgot about it. ;-) Cool, thanks :) - Brett -- Brett Porter [EMAIL PROTECTED] http://blogs.exist.com/bporter/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: archetype release
No objections of course, I was waiting for you since it sounded like you'd said the windows issue was a blocker and that Brian was looking into it. On 19/02/2008, at 5:47 AM, Raphaël Piéroni wrote: I don't object. Raphaël 2008/2/18, Jason van Zyl [EMAIL PROTECTED]: Ok, unless anyone objects I'm going to try and get this thing out. On 18-Feb-08, at 9:29 AM, Jason van Zyl wrote: Hi, Brett/Raphael I know that both of you talked about doing a release, and if you're around and are going to do it now great. I'll wait an hour, and if neither of you respond I'll start preparing the release. I can live the create-from-archetype not working on Windows. We have to fix the backward compat problem ASAP. Thanks, Jason -- Jason van Zyl Founder, Apache Maven jason at sonatype dot com -- First, the taking in of scattered particulars under one Idea, so that everyone understands what is being talked about ... Second, the separation of the Idea into parts, by dividing it at the joints, as nature directs, not breaking any limb in half as a bad carver might. -- Plato, Phaedrus (Notes on the Synthesis of Form by C. Alexander) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Thanks, Jason -- Jason van Zyl Founder, Apache Maven jason at sonatype dot com -- People develop abstractions by generalizing from concrete examples. Every attempt to determine the correct abstraction on paper without actually developing a running system is doomed to failure. No one is that smart. A framework is a resuable design, so you develop it by looking at the things it is supposed to be a design of. The more examples you look at, the more general your framework will be. -- Ralph Johnson Don Roberts, Patterns for Evolving Frameworks - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Brett Porter [EMAIL PROTECTED] http://blogs.exist.com/bporter/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [vote] Benjamin Bentmann as Maven committer
+1 On 19/02/2008, at 4:38 AM, 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] -- Brett Porter [EMAIL PROTECTED] http://blogs.exist.com/bporter/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: wildcard mirror - svn commit: r628767
Hi Nicolas,
Neat change - I like it.
I just wonder if ${mirrorOf} instead of {0} might be more intuitive?
Also - don't forget to merge your change to artifact/trunk!
Cheers,
Brett
On 19/02/2008, at 1:55 AM, [EMAIL PROTECTED] wrote:
Author: nicolas
Date: Mon Feb 18 06:55:12 2008
New Revision: 628767
URL: http://svn.apache.org/viewvc?rev=628767view=rev
Log:
MNG-3407 : improve mirrorOf to support pattern based repository URL
Modified:
maven/components/branches/maven-2.0.x/maven-artifact-manager/src/
main/java/org/apache/maven/artifact/manager/DefaultWagonManager.java
maven/components/branches/maven-2.0.x/maven-artifact-manager/src/
test/java/org/apache/maven/artifact/manager/
DefaultWagonManagerTest.java
Modified: maven/components/branches/maven-2.0.x/maven-artifact-
manager/src/main/java/org/apache/maven/artifact/manager/
DefaultWagonManager.java
URL:
http://svn.apache.org/viewvc/maven/components/branches/maven-2.0.x/maven-artifact-manager/src/main/java/org/apache/maven/artifact/manager/DefaultWagonManager.java?rev=628767r1=628766r2=628767view=diff
=
=
=
=
=
=
=
=
==
--- maven/components/branches/maven-2.0.x/maven-artifact-manager/src/
main/java/org/apache/maven/artifact/manager/DefaultWagonManager.java
(original)
+++ maven/components/branches/maven-2.0.x/maven-artifact-manager/src/
main/java/org/apache/maven/artifact/manager/DefaultWagonManager.java
Mon Feb 18 06:55:12 2008
@@ -61,6 +61,7 @@
import java.util.Iterator;
import java.util.List;
import java.util.Map;
+import java.text.MessageFormat;
public class DefaultWagonManager
extends AbstractLogEnabled
@@ -710,6 +711,16 @@
if ( repository == null )
{
repository = (ArtifactRepository) mirrors.get( WILDCARD );
+ if ( repository != null )
+ {
+ String url = repository.getUrl();
+ if ( url.indexOf( {0} ) = 0 )
+ {
+url = MessageFormat.format( repository.getUrl(), new
Object[] { mirrorOf } );
+repository = new DefaultArtifactRepository( mirrorOf, url,
null );
+ mirrors.put( mirrorOf, repository );
+ }
+ }
}
return repository;
}
Modified: maven/components/branches/maven-2.0.x/maven-artifact-
manager/src/test/java/org/apache/maven/artifact/manager/
DefaultWagonManagerTest.java
URL:
http://svn.apache.org/viewvc/maven/components/branches/maven-2.0.x/maven-artifact-manager/src/test/java/org/apache/maven/artifact/manager/DefaultWagonManagerTest.java?rev=628767r1=628766r2=628767view=diff
=
=
=
=
=
=
=
=
==
--- maven/components/branches/maven-2.0.x/maven-artifact-manager/src/
test/java/org/apache/maven/artifact/manager/
DefaultWagonManagerTest.java (original)
+++ maven/components/branches/maven-2.0.x/maven-artifact-manager/src/
test/java/org/apache/maven/artifact/manager/
DefaultWagonManagerTest.java Mon Feb 18 06:55:12 2008
@@ -43,6 +43,15 @@
wagonManager = (WagonManager) lookup( WagonManager.ROLE );
}
+ public void testMappedMirror()
+ throws Exception
+ {
+ DefaultWagonManager manager = (DefaultWagonManager)
wagonManager;
+ manager.addMirror( wildcar, *, http://archiva/repository/
{0} );
+ assertEquals( http://archiva/repository/central;,
manager.getMirror( central ).getUrl() );
+ assertEquals( http://archiva/repository/apache.snapshots;,
manager.getMirror( apache.snapshots ).getUrl() );
+ }
+
public void testDefaultWagonManager()
throws Exception
{
--
Brett Porter
[EMAIL PROTECTED]
http://blogs.exist.com/bporter/
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [vote] Benjamin Bentmann as Maven committer
+1 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: archetype release
I just got the roundtrip tests working on windows, Do i wait for the release to commit? Another issue could be to update the internal catalog to grab the latest MAVENUSER wiki page. Raphaël 2008/2/18, Brett Porter [EMAIL PROTECTED]: No objections of course, I was waiting for you since it sounded like you'd said the windows issue was a blocker and that Brian was looking into it. On 19/02/2008, at 5:47 AM, Raphaël Piéroni wrote: I don't object. Raphaël 2008/2/18, Jason van Zyl [EMAIL PROTECTED]: Ok, unless anyone objects I'm going to try and get this thing out. On 18-Feb-08, at 9:29 AM, Jason van Zyl wrote: Hi, Brett/Raphael I know that both of you talked about doing a release, and if you're around and are going to do it now great. I'll wait an hour, and if neither of you respond I'll start preparing the release. I can live the create-from-archetype not working on Windows. We have to fix the backward compat problem ASAP. Thanks, Jason -- Jason van Zyl Founder, Apache Maven jason at sonatype dot com -- First, the taking in of scattered particulars under one Idea, so that everyone understands what is being talked about ... Second, the separation of the Idea into parts, by dividing it at the joints, as nature directs, not breaking any limb in half as a bad carver might. -- Plato, Phaedrus (Notes on the Synthesis of Form by C. Alexander) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Thanks, Jason -- Jason van Zyl Founder, Apache Maven jason at sonatype dot com -- People develop abstractions by generalizing from concrete examples. Every attempt to determine the correct abstraction on paper without actually developing a running system is doomed to failure. No one is that smart. A framework is a resuable design, so you develop it by looking at the things it is supposed to be a design of. The more examples you look at, the more general your framework will be. -- Ralph Johnson Don Roberts, Patterns for Evolving Frameworks - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Brett Porter [EMAIL PROTECTED] http://blogs.exist.com/bporter/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [vote] Benjamin Bentmann as Maven committer
+1 Rahul 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: archetype release
On 19/02/2008, at 8:16 AM, Raphaël Piéroni wrote: I just got the roundtrip tests working on windows, Do i wait for the release to commit? Commit away - an RM can prepare a release based on a previous revision if they see fit, though it sounds like these changes should be pulled in. Another issue could be to update the internal catalog to grab the latest MAVENUSER wiki page. I think this can wait (note my changes to hardcode the Maven archetype versions probably need to be reflected on the wiki, I didn't think the internal catalog would be regenerated from it). - Brett Raphaël 2008/2/18, Brett Porter [EMAIL PROTECTED]: No objections of course, I was waiting for you since it sounded like you'd said the windows issue was a blocker and that Brian was looking into it. On 19/02/2008, at 5:47 AM, Raphaël Piéroni wrote: I don't object. Raphaël 2008/2/18, Jason van Zyl [EMAIL PROTECTED]: Ok, unless anyone objects I'm going to try and get this thing out. On 18-Feb-08, at 9:29 AM, Jason van Zyl wrote: Hi, Brett/Raphael I know that both of you talked about doing a release, and if you're around and are going to do it now great. I'll wait an hour, and if neither of you respond I'll start preparing the release. I can live the create-from-archetype not working on Windows. We have to fix the backward compat problem ASAP. Thanks, Jason -- Jason van Zyl Founder, Apache Maven jason at sonatype dot com -- First, the taking in of scattered particulars under one Idea, so that everyone understands what is being talked about ... Second, the separation of the Idea into parts, by dividing it at the joints, as nature directs, not breaking any limb in half as a bad carver might. -- Plato, Phaedrus (Notes on the Synthesis of Form by C. Alexander) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Thanks, Jason -- Jason van Zyl Founder, Apache Maven jason at sonatype dot com -- People develop abstractions by generalizing from concrete examples. Every attempt to determine the correct abstraction on paper without actually developing a running system is doomed to failure. No one is that smart. A framework is a resuable design, so you develop it by looking at the things it is supposed to be a design of. The more examples you look at, the more general your framework will be. -- Ralph Johnson Don Roberts, Patterns for Evolving Frameworks - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Brett Porter [EMAIL PROTECTED] http://blogs.exist.com/bporter/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Brett Porter [EMAIL PROTECTED] http://blogs.exist.com/bporter/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: archetype release
2008/2/18, Brett Porter [EMAIL PROTECTED]: On 19/02/2008, at 8:16 AM, Raphaël Piéroni wrote: I just got the roundtrip tests working on windows, Do i wait for the release to commit? Commit away - an RM can prepare a release based on a previous revision if they see fit, though it sounds like these changes should be pulled in. Another issue could be to update the internal catalog to grab the latest MAVENUSER wiki page. I think this can wait (note my changes to hardcode the Maven archetype versions probably need to be reflected on the wiki, I didn't think the internal catalog would be regenerated from it). The first one was. it is my only argument to use it. I would rather have a coherent way to create catalogs for repositories. Raphaël - Brett Raphaël 2008/2/18, Brett Porter [EMAIL PROTECTED]: No objections of course, I was waiting for you since it sounded like you'd said the windows issue was a blocker and that Brian was looking into it. On 19/02/2008, at 5:47 AM, Raphaël Piéroni wrote: I don't object. Raphaël 2008/2/18, Jason van Zyl [EMAIL PROTECTED]: Ok, unless anyone objects I'm going to try and get this thing out. On 18-Feb-08, at 9:29 AM, Jason van Zyl wrote: Hi, Brett/Raphael I know that both of you talked about doing a release, and if you're around and are going to do it now great. I'll wait an hour, and if neither of you respond I'll start preparing the release. I can live the create-from-archetype not working on Windows. We have to fix the backward compat problem ASAP. Thanks, Jason -- Jason van Zyl Founder, Apache Maven jason at sonatype dot com -- First, the taking in of scattered particulars under one Idea, so that everyone understands what is being talked about ... Second, the separation of the Idea into parts, by dividing it at the joints, as nature directs, not breaking any limb in half as a bad carver might. -- Plato, Phaedrus (Notes on the Synthesis of Form by C. Alexander) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Thanks, Jason -- Jason van Zyl Founder, Apache Maven jason at sonatype dot com -- People develop abstractions by generalizing from concrete examples. Every attempt to determine the correct abstraction on paper without actually developing a running system is doomed to failure. No one is that smart. A framework is a resuable design, so you develop it by looking at the things it is supposed to be a design of. The more examples you look at, the more general your framework will be. -- Ralph Johnson Don Roberts, Patterns for Evolving Frameworks - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Brett Porter [EMAIL PROTECTED] http://blogs.exist.com/bporter/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Brett Porter [EMAIL PROTECTED] http://blogs.exist.com/bporter/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: archetype release
+1. Lets get the current fix out and do another release as soon as the windows issue is fixed. (it only affects creating a new archetype iirc) -Original Message- From: Jason van Zyl [mailto:[EMAIL PROTECTED] Sent: Monday, February 18, 2008 12:29 PM To: Maven Developers List Subject: archetype release Hi, Brett/Raphael I know that both of you talked about doing a release, and if you're around and are going to do it now great. I'll wait an hour, and if neither of you respond I'll start preparing the release. I can live the create-from-archetype not working on Windows. We have to fix the backward compat problem ASAP. Thanks, Jason -- Jason van Zyl Founder, Apache Maven jason at sonatype dot com -- First, the taking in of scattered particulars under one Idea, so that everyone understands what is being talked about ... Second, the separation of the Idea into parts, by dividing it at the joints, as nature directs, not breaking any limb in half as a bad carver might. -- Plato, Phaedrus (Notes on the Synthesis of Form by C. Alexander) - 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] Benjamin Bentmann as Maven committer
+1 for sure 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] -- Dennis Lundberg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
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: Version ranges and snapshots
I am only speaking in regard to MNG-3092, there are several other related issues which I think all should be fixed Cons -- 1) Continuous integration of trunks I would like to be able to run the tests of all of my artifacts against a build of trunk of every other. How I currently achieve this... Use continuum with clean install and force a rebuild of every artifact on a regular basis. If MNG-3092 were to go ahead in order to include a snapshot in a build I would have to change the dep of each artifact to include a -SNAPSHOT in one of the bounds. 2) Using MNG-3092 is not the correct approach to exclude snapshots from releases. The enforcer plugin can detect and alert when a snapshot is resolved anywhere in the transitive tree. It would be nice to be able to bind this to a release Pros - 1) stops you getting inconsistent builds when you have a snapshot repository in your repository list that has artifacts matching a range 2) will stop (i think) dirty builds from snapshot metadata in the local repository. The local repository has multiple personality disorder. There is no way to enable disable the local metadata left in the local repository after a release or install. If the local repository cache was separate and the actual local repository (i.e. for installs) was a first order repo then this problem would go away On Thu, 31 Jan 2008 02:14:59 Stephen Connolly wrote: IMHO I think a vote with the two positions clearly identified (perhaps with pros and cons for both if the pair of ye can agree on the pros and cons). (unless somebody else has a third position) -Stephen. On Jan 30, 2008 12:56 PM, Mark Hobson [EMAIL PROTECTED] wrote: On 30/01/2008, Mark Hobson [EMAIL PROTECTED] wrote: I don't think that linking this level of artifact resolution uncertainty to its source repository is a good idea. How version ranges are resolved should be completely deterministic and independent from where the artifact was actually downloaded from, otherwise we'll end up with no end of build reproducibility problems. In addition, the local repository would be exempt from these rules. This would require manually deleting artifacts from the local repo to ensure that certain versions weren't picked up; a maintenance nightmare I'm sure you'll agree. How's best to proceed with resolving this issue? Would voting make sense, or should the PMC lay down the intended direction? I'm not sure whether this thread needs to get any longer.. :) Mark - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Michael McCallum Enterprise Engineer mailto:[EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [vote] Benjamin Bentmann as Maven committer
+1 -Original Message- From: Lukas Theussl [mailto:[EMAIL PROTECTED] Sent: Monday, February 18, 2008 12:39 PM To: Maven Developers List Subject: [vote] Benjamin Bentmann as Maven committer 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-archetype-plugin-2.0-alpha-2
URL to the release? On 18-Feb-08, at 3:04 PM, Brian E. Fox wrote: The most important early issues have been fixed and we need to get this out there. The site is updated and here's the list of issues fixed: Release Notes - Maven Archetype - Version 2.0-alpha-2 ** Bug * [ARCHETYPE-128] - Unable to create a Cocoon app with Maven archetype: [WARNING] No archetype repository found. * [ARCHETYPE-133] - POMs generated as part of create-from-project are not correct and prevent using this feature completely ** Improvement * [ARCHETYPE-116] - -DarchetypeArtifactId parameter is no longer respected * [ARCHETYPE-117] - return previous defaults Because of the urgent nature of this release, this vote will be open for 24hrs unless someone objects. +1 --Brian Thanks, Jason -- Jason van Zyl Founder, Apache Maven jason at sonatype dot com -- Three people can keep a secret provided two of them are dead. -- Unknown - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: svn commit: r628845 - /maven/pom/trunk/maven/pom.xml
Hi Wendy
Did you mean for this to go into Maven parent pom?
The URL in your change suggests to me that is intended for Maven
components pom. If left in Maven parent pom there will be URL clashes
between say Maven 2.1 and Maven Project Info reports Plugin 2.1
[EMAIL PROTECTED] wrote:
Author: wsmoak
Date: Mon Feb 18 11:15:26 2008
New Revision: 628845
URL: http://svn.apache.org/viewvc?rev=628845view=rev
Log:
Override the distribution url to avoid inaadvertently publishing directly to
the rsynced repo.
Modified:
maven/pom/trunk/maven/pom.xml
Modified: maven/pom/trunk/maven/pom.xml
URL:
http://svn.apache.org/viewvc/maven/pom/trunk/maven/pom.xml?rev=628845r1=628844r2=628845view=diff
==
--- maven/pom/trunk/maven/pom.xml (original)
+++ maven/pom/trunk/maven/pom.xml Mon Feb 18 11:15:26 2008
@@ -82,6 +82,10 @@
/mailingLists
distributionManagement
+repository
+ idmaven.staging/id
+
urlscp://people.apache.org/www/people.apache.org/builds/maven/${project.version}/staging-repo/url
+/repository
site
idapache.website/id
urlscp://people.apache.org/www/maven.apache.org/url
--
Dennis Lundberg
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[vote] release maven-archetype-plugin-2.0-alpha-2
The most important early issues have been fixed and we need to get this out there. The site is updated and here's the list of issues fixed: Release Notes - Maven Archetype - Version 2.0-alpha-2 ** Bug * [ARCHETYPE-128] - Unable to create a Cocoon app with Maven archetype: [WARNING] No archetype repository found. * [ARCHETYPE-133] - POMs generated as part of create-from-project are not correct and prevent using this feature completely ** Improvement * [ARCHETYPE-116] - -DarchetypeArtifactId parameter is no longer respected * [ARCHETYPE-117] - return previous defaults Because of the urgent nature of this release, this vote will be open for 24hrs unless someone objects. +1 --Brian
Re: [vote] release maven-archetype-plugin-2.0-alpha-2
+1. Gave it a spin on a big project for :create and :generate, scanned the commit logs. Not blockers as they are matters of policy: * I'd prefer is consistency in the tag name - it's 2.0-alpha-2 instead of maven-archetype-2.0-alpha-2 * MavenArchetypeMojo, site.xml have out of date license headers - Brett On 19/02/2008, at 10:15 AM, Brian E. Fox wrote: Woop: http://people.apache.org/~brianf/staging-repository/ -Original Message- From: Jason van Zyl [mailto:[EMAIL PROTECTED] Sent: Monday, February 18, 2008 6:14 PM To: Maven Developers List Subject: Re: [vote] release maven-archetype-plugin-2.0-alpha-2 URL to the release? On 18-Feb-08, at 3:04 PM, Brian E. Fox wrote: The most important early issues have been fixed and we need to get this out there. The site is updated and here's the list of issues fixed: Release Notes - Maven Archetype - Version 2.0-alpha-2 ** Bug * [ARCHETYPE-128] - Unable to create a Cocoon app with Maven archetype: [WARNING] No archetype repository found. * [ARCHETYPE-133] - POMs generated as part of create-from-project are not correct and prevent using this feature completely ** Improvement * [ARCHETYPE-116] - -DarchetypeArtifactId parameter is no longer respected * [ARCHETYPE-117] - return previous defaults Because of the urgent nature of this release, this vote will be open for 24hrs unless someone objects. +1 --Brian Thanks, Jason -- Jason van Zyl Founder, Apache Maven jason at sonatype dot com -- Three people can keep a secret provided two of them are dead. -- Unknown - 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] -- Brett Porter [EMAIL PROTECTED] http://blogs.exist.com/bporter/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [vote] release maven-archetype-plugin-2.0-alpha-2
Woop: http://people.apache.org/~brianf/staging-repository/ -Original Message- From: Jason van Zyl [mailto:[EMAIL PROTECTED] Sent: Monday, February 18, 2008 6:14 PM To: Maven Developers List Subject: Re: [vote] release maven-archetype-plugin-2.0-alpha-2 URL to the release? On 18-Feb-08, at 3:04 PM, Brian E. Fox wrote: The most important early issues have been fixed and we need to get this out there. The site is updated and here's the list of issues fixed: Release Notes - Maven Archetype - Version 2.0-alpha-2 ** Bug * [ARCHETYPE-128] - Unable to create a Cocoon app with Maven archetype: [WARNING] No archetype repository found. * [ARCHETYPE-133] - POMs generated as part of create-from-project are not correct and prevent using this feature completely ** Improvement * [ARCHETYPE-116] - -DarchetypeArtifactId parameter is no longer respected * [ARCHETYPE-117] - return previous defaults Because of the urgent nature of this release, this vote will be open for 24hrs unless someone objects. +1 --Brian Thanks, Jason -- Jason van Zyl Founder, Apache Maven jason at sonatype dot com -- Three people can keep a secret provided two of them are dead. -- Unknown - 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: svn commit: r628845 - /maven/pom/trunk/maven/pom.xml
On Feb 18, 2008 4:12 PM, Dennis Lundberg [EMAIL PROTECTED] wrote: Hi Wendy Did you mean for this to go into Maven parent pom? The URL in your change suggests to me that is intended for Maven components pom. If left in Maven parent pom there will be URL clashes between say Maven 2.1 and Maven Project Info reports Plugin 2.1 I don't expect it to actually be used. Our release instructions say to define a deploy.altRepository property in settings.xml, and (at least for plugins) the release plugin is configured to use that. I want it in the parent pom to prevent any inadvertent publishing directly to m2-ibiblio-rsync-repository (which should never be published to directly, all releases should be staged for review.) And if it does somehow get used, the version number will keep _most_ things separate. If a sub-project does want a shared staging area, it can override this in the top-level pom for that sub-project. Archiva does it this way, see http://people.apache.org/builds/maven/archiva/ (which we need to clean up!) -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [vote] release maven-archetype-plugin-2.0-alpha-2
On 19/02/2008, at 10:49 AM, Brian E. Fox wrote: ... I had to enter all the values by hand ... That's unusual - is something not configured right? - Brett -- Brett Porter [EMAIL PROTECTED] http://blogs.exist.com/bporter/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [vote] release maven-archetype-plugin-2.0-alpha-2
Yeah, the versions in the pom where 2.0-SNAPSHOT instead of 2.0-alpha-2-SNAPSHOT -Original Message- From: Brett Porter [mailto:[EMAIL PROTECTED] Sent: Monday, February 18, 2008 7:04 PM To: Maven Developers List Subject: Re: [vote] release maven-archetype-plugin-2.0-alpha-2 On 19/02/2008, at 10:49 AM, Brian E. Fox wrote: ... I had to enter all the values by hand ... That's unusual - is something not configured right? - Brett -- Brett Porter [EMAIL PROTECTED] http://blogs.exist.com/bporter/ - 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-archetype-plugin-2.0-alpha-2
I'll reroll it to correct the tag and licenses. I had to enter all the values by hand and didn't catch the tag. -Original Message- From: Brett Porter [mailto:[EMAIL PROTECTED] Sent: Monday, February 18, 2008 6:46 PM To: Maven Developers List Subject: Re: [vote] release maven-archetype-plugin-2.0-alpha-2 +1. Gave it a spin on a big project for :create and :generate, scanned the commit logs. Not blockers as they are matters of policy: * I'd prefer is consistency in the tag name - it's 2.0-alpha-2 instead of maven-archetype-2.0-alpha-2 * MavenArchetypeMojo, site.xml have out of date license headers - Brett On 19/02/2008, at 10:15 AM, Brian E. Fox wrote: Woop: http://people.apache.org/~brianf/staging-repository/ -Original Message- From: Jason van Zyl [mailto:[EMAIL PROTECTED] Sent: Monday, February 18, 2008 6:14 PM To: Maven Developers List Subject: Re: [vote] release maven-archetype-plugin-2.0-alpha-2 URL to the release? On 18-Feb-08, at 3:04 PM, Brian E. Fox wrote: The most important early issues have been fixed and we need to get this out there. The site is updated and here's the list of issues fixed: Release Notes - Maven Archetype - Version 2.0-alpha-2 ** Bug * [ARCHETYPE-128] - Unable to create a Cocoon app with Maven archetype: [WARNING] No archetype repository found. * [ARCHETYPE-133] - POMs generated as part of create-from-project are not correct and prevent using this feature completely ** Improvement * [ARCHETYPE-116] - -DarchetypeArtifactId parameter is no longer respected * [ARCHETYPE-117] - return previous defaults Because of the urgent nature of this release, this vote will be open for 24hrs unless someone objects. +1 --Brian Thanks, Jason -- Jason van Zyl Founder, Apache Maven jason at sonatype dot com -- Three people can keep a secret provided two of them are dead. -- Unknown - 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] -- Brett Porter [EMAIL PROTECTED] http://blogs.exist.com/bporter/ - 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]
[vote] Take-2 release maven-archetype-plugin-2.0-alpha-2
Rerolled to correct the tag and 2 header issues identified by Brett. The most important early issues have been fixed and we need to get this out there. The site is updated and here's the list of issues fixed: Staging repo: http://people.apache.org/~brianf/staging-repository Release Notes - Maven Archetype - Version 2.0-alpha-2 ** Bug * [ARCHETYPE-128] - Unable to create a Cocoon app with Maven archetype: [WARNING] No archetype repository found. * [ARCHETYPE-133] - POMs generated as part of create-from-project are not correct and prevent using this feature completely ** Improvement * [ARCHETYPE-116] - -DarchetypeArtifactId parameter is no longer respected * [ARCHETYPE-117] - return previous defaults Because of the urgent nature of this release, this vote will be open for 24hrs unless someone objects. +1 --Brian
Re: [vote] Take-2 release maven-archetype-plugin-2.0-alpha-2
+1 - retested the new version. On 19/02/2008, at 11:18 AM, Brian E. Fox wrote: Rerolled to correct the tag and 2 header issues identified by Brett. The most important early issues have been fixed and we need to get this out there. The site is updated and here's the list of issues fixed: Staging repo: http://people.apache.org/~brianf/staging-repository Release Notes - Maven Archetype - Version 2.0-alpha-2 ** Bug * [ARCHETYPE-128] - Unable to create a Cocoon app with Maven archetype: [WARNING] No archetype repository found. * [ARCHETYPE-133] - POMs generated as part of create-from-project are not correct and prevent using this feature completely ** Improvement * [ARCHETYPE-116] - -DarchetypeArtifactId parameter is no longer respected * [ARCHETYPE-117] - return previous defaults Because of the urgent nature of this release, this vote will be open for 24hrs unless someone objects. +1 --Brian -- Brett Porter [EMAIL PROTECTED] http://blogs.exist.com/bporter/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [vote] Take-2 release maven-archetype-plugin-2.0-alpha-2
+1 I could make my archetypes, deploy, and use mvn archetype:generate no problem. The old way works fine too now as I've had a bunch of scripts forever I've used and they all spit out project that build. On 18-Feb-08, at 4:18 PM, Brian E. Fox wrote: Rerolled to correct the tag and 2 header issues identified by Brett. The most important early issues have been fixed and we need to get this out there. The site is updated and here's the list of issues fixed: Staging repo: http://people.apache.org/~brianf/staging-repository Release Notes - Maven Archetype - Version 2.0-alpha-2 ** Bug * [ARCHETYPE-128] - Unable to create a Cocoon app with Maven archetype: [WARNING] No archetype repository found. * [ARCHETYPE-133] - POMs generated as part of create-from-project are not correct and prevent using this feature completely ** Improvement * [ARCHETYPE-116] - -DarchetypeArtifactId parameter is no longer respected * [ARCHETYPE-117] - return previous defaults Because of the urgent nature of this release, this vote will be open for 24hrs unless someone objects. +1 --Brian Thanks, Jason -- Jason van Zyl Founder, Apache Maven jason at sonatype dot com -- We all have problems. How we deal with them is a measure of our worth. -- Unknown - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
continuum deploying maven snapshots?
Continuum doesn't seem to be deploying snapshots correctly from Zones anymore. The latest maven snapshots have carlos' paths in them builddef.lst file: -classpath C:\Documents and Settings\csanchez\.m2\repository\aspectj\aspectjrt\1.5.3\aspectjrt-1.5.3 .jar;C:\Documents and Settings\csanchez\.m2\repository\backport-util-concurrent\backport-util- concurrent\3.0\backport-util-concurrent-3.0.jar;C:\Documents and Settings\csanchez\.m2\repository\com\jcraft\jsch\0.1.27\jsch-0.1.27.jar; C:\Documents and Settings\csanchez\.m2\repository\commons-cli\commons-cli\1.0\commons-cli -1.0.jar;C:\Documents and Settings\csanchez\.m2\repository\jtidy\jtidy\4aug2000r7-dev\jtidy-4aug20 00r7-dev.jar;. --Brian
Best practices for multi-outputs projects.
Hi everyone, I apologize for asking a rudimentary question. I'm currently developing a plugin to manage Globus Toolkit related tasks (create GAR, flatten WSDLs, etc.) for Maven. I just wanted to know if it was better to have generated source as a submodule or as a classifier. Here is a quick example of what I think needs to be done: + project-root (output package GAR/ multimodules) !--src/main/resources/schema !-+service.wsdl !-+service.xsd !--+project-service (service implementation JAR) (no deps) !-+src/main/java/ !-+src/main/test/ !--+project-stub !-+src/main/java/ (classes generated from project-root WSDL2Java goal) !-+src/main/test/ !--+project-client (depends on project-stub JAR) !-+src/main/java/ (client implementation) !-+src/main/resources/ (shell scripts) The question is if project-root plugin-gar needs to dig in the subprojects how acurate is it to have this structure. What I mean is the GAR needs : the Project-service-1.0-jar , project-client-1.0.jar and project-stub-1.0.jar as well as the shell scripts (should they be moves in the project-root resources?). Finally, how OK in best practices sense is it for project-root to manipulate the files in proejct-stub ? Thanks for your help! Regards, Mathieu - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Release Maven Stage Plugin 1.0-alpha-1
On Feb 18, 2008 9:58 PM, Wendy Smoak [EMAIL PROTECTED] wrote: I'd like to do the first release of the Maven Stage Plugin. This plugin is already being used for Maven releases, and although it has limited functionality, it seems to be stable. ... Staging repo: http://people.apache.org/~wsmoak/staging-repo/ +1 I tested it by copying two staged Struts releases to a test repo: mvn stage:copy -Dsource=http://people.apache.org/builds/struts/1.3.8/m2-staging-repository; -Dtarget=scp://people.apache.org/home/wsmoak/public_html/stage-plugin-test-repo -Dversion=1.3.8 mvn stage:copy -Dsource=http://people.apache.org/builds/struts/1.3.9/m2-staging-repository; -Dtarget=scp://people.apache.org/home/wsmoak/public_html/stage-plugin-test-repo -Dversion=1.3.9 which produced... http://people.apache.org/~wsmoak/stage-plugin-test-repo/ I linked to it in the vote thread, but here's another link to the guide to testing staged releases, which Brett updated recently: http://maven.apache.org/guides/development/guide-testing-releases.html -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[VOTE] Release Maven Stage Plugin 1.0-alpha-1
I'd like to do the first release of the Maven Stage Plugin. This plugin is already being used for Maven releases, and although it has limited functionality, it seems to be stable. There are four open issues in JIRA: MSTAGE-1RepositoryCopierTest fails on Windows MSTAGE-2The version parameter is ignored MSTAGE-3The stage plugin only supports copying from http(s) to scp urls MSTAGE-4 stage-plugin hangs http://jira.codehaus.org/browse/MSTAGE Staging repo: http://people.apache.org/~wsmoak/staging-repo/ Staging site: http://maven.apache.org/plugins/maven-stage-plugin-1.0-SNAPSHOT/ Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html The vote will be open for at least 72 hours. Assuming all is well, I'll sync it on Friday or Saturday. [ ] +1 [ ] +0 [ ] -1 Thanks, -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Release Maven Stage Plugin 1.0-alpha-1
+1 On 18-Feb-08, at 8:58 PM, Wendy Smoak wrote: I'd like to do the first release of the Maven Stage Plugin. This plugin is already being used for Maven releases, and although it has limited functionality, it seems to be stable. There are four open issues in JIRA: MSTAGE-1RepositoryCopierTest fails on Windows MSTAGE-2The version parameter is ignored MSTAGE-3 The stage plugin only supports copying from http(s) to scp urls MSTAGE-4 stage-plugin hangs http://jira.codehaus.org/browse/MSTAGE Staging repo: http://people.apache.org/~wsmoak/staging-repo/ Staging site: http://maven.apache.org/plugins/maven-stage-plugin-1.0-SNAPSHOT/ Guide to testing staged releases: http://maven.apache.org/guides/development/guide-testing-releases.html The vote will be open for at least 72 hours. Assuming all is well, I'll sync it on Friday or Saturday. [ ] +1 [ ] +0 [ ] -1 Thanks, -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Thanks, Jason -- Jason van Zyl Founder, Apache Maven jason at sonatype dot com -- the course of true love never did run smooth ... -- Shakespeare - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [vote] Benjamin Bentmann as Maven committer
+1 Arnaud On Feb 18, 2008 11:46 PM, Dennis Lundberg [EMAIL PROTECTED] wrote: +1 for sure 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] -- Dennis Lundberg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- .. 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 ...
Re: [vote] Benjamin Bentmann as Maven committer
+1 2008/2/19, Arnaud HERITIER [EMAIL PROTECTED]: +1 Arnaud On Feb 18, 2008 11:46 PM, Dennis Lundberg [EMAIL PROTECTED] wrote: +1 for sure 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] -- Dennis Lundberg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- .. 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 ...
Re: Plan to migrate towards Spring?
2008/2/18, Joakim Erdfelt [EMAIL PROTECTED]: I've felt that we need to migrate our choice of IoC (plexus) towards a better documented and better supported container (I'm leaning towards Spring) +1000 : I was never very confortable with plexus and lack of documentation on available components. +1 for all moves from plexus-utils to apache commons-x equivalents org.codehaus.plexus.commandline.DefaultExecutableResolver; org.codehaus.plexus.commandline.ExecutableResolver; Used: archiva-webapp-test Plan: Investigate Need. Fork into archiva if truely needed. commons-exec allready did the investigation, but not ready yet for release AFAIK. Plan: Migrate expression-evaluator to archiva codebase. No idea what plexus.evaluator provides, but does this relates to commons-el or commons-jexl ? Plan: Migrate to JDK 1.5 + JPA + Annotations +1 : JDO is dead. JPA has many stable implementations now. Which one do you have in mind ? Plan: Fork it.could.webdav into new archiva-davserver component. If so I'd suggest some enhancements to support storing in SMB windows share filesystem org.codehaus.plexus.xwork.action.PlexusActionSupport; Used: archiva-webapp Plan: Switch to SwingMVC What is the benefict here ? Natural update from existing code is to move to Struts2. If we have to re-implement the web UI, why not use a higher abstraction level framework, like apache Wicket ? Thanks for this exciting proposal. Any chance to see maven-core migration to Spring also ? ;-) Nico
[MNG-3410] Plugin managed versions are ignored
I'd like to get some feedback in MNG-3410, particularly from John as he has been working on this. If you build and install a plugin with managed versions that affect plugin transitive dependencies, when it's used the dependency management is ignored If the dependency management affects the plugin direct dependecies it works properly because the information is merged. eg. Plugin A depends on jar B that depends on jar C[1.0] A dependencyManagement explicitly forces C[2.0], you build and install using C[2.0] in the classpath If you use plugin A in your pom it will be used with C version 1.0 -- 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]
