Re: 3.0 beta 2/3/4 roadmap was Re: Merging in our Aether and Guice changes to Maven 3.x

+1 S. --- [image: Linkedin] [image: Twitter] 2010/8/6 Arnaud Héritier > Ok, > > Thus talking is good but doing is better ( I know I'm talking more than > I'm doing :-) ) > > Could we have a consensus if we : > - release now th

Re: 3.0 beta 2/3/4 roadmap was Re: Merging in our Aether and Guice changes to Maven 3.x

+1

Re: 3.0 beta 2/3/4 roadmap was Re: Merging in our Aether and Guice changes to Maven 3.x

+1 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org

[jira] Subscription: Design & Best Practices

Issue Subscription Filter: Design & Best Practices (24 issues) Subscriber: mavendevlist Key Summary MNG-2184Possible problem with @aggregator and forked lifecycles http://jira.codehaus.org/browse/MNG-2184 MNG-612 implement conflict resolution techniques

Re: 3.0 beta 2/3/4 roadmap was Re: Merging in our Aether and Guice changes to Maven 3.x

+1 On 8/5/10 8:04 PM, Arnaud Héritier wrote: Ok, Thus talking is good but doing is better ( I know I'm talking more than I'm doing :-) ) Could we have a consensus if we : - release now the trunk as a beta 2 without Guice and Aether. With that we'll have a solid base to compare futur

Re: 3.0 beta 2/3/4 roadmap was Re: Merging in our Aether and Guice changes to Maven 3.x

+1 Regards, Hervé Le vendredi 06 août 2010, Arnaud Héritier a écrit : > Ok, > > Thus talking is good but doing is better ( I know I'm talking more than > I'm doing :-) ) > > Could we have a consensus if we : > - release now the trunk as a beta 2 without Guice and Aether. With that > we'l

Re: 3.0 beta 2/3/4 roadmap was Re: Merging in our Aether and Guice changes to Maven 3.x

Arnaud, I think your plan is sensible. I agree with what you and Dennis have said. It allows the Maven community to move forward but also doesn't stop development of the integration. Paul 2010/8/5 Arnaud Héritier > Ok, > > Thus talking is good but doing is better ( I know I'm talking more tha

Re: 3.0 beta 2/3/4 roadmap was Re: Merging in our Aether and Guice changes to Maven 3.x

yes the goal will be to do more communications on beta-3 than beta-2 to let a maximum number of users trying it. If they have any issues due to Ather or Guice we'll be able to ask them to come back to beta 2 the time we fix issues and deploy the beta-4 On Aug 6, 2010, at 2:09 AM, Mark Derricutt

Re: 3.0 beta 2/3/4 roadmap was Re: Merging in our Aether and Guice changes to Maven 3.x

+1 on releasing beta-2 followed -very quickly- with beta-3 inc guice/aether (like days apart). Tho I wonder if it might confuse people - but then, if you're playing with beta's you're probably following these threads anyway ). Mark -- Pull me down under... 2010/8/6 Arnaud Héritier > WDYT

3.0 beta 2/3/4 roadmap was Re: Merging in our Aether and Guice changes to Maven 3.x

Ok, Thus talking is good but doing is better ( I know I'm talking more than I'm doing :-) ) Could we have a consensus if we : - release now the trunk as a beta 2 without Guice and Aether. With that we'll have a solid base to compare future changes with. We know it is stable and it is bet

Re: Merging in our Aether and Guice changes to Maven 3.x

> > The first thing I would like to happen is that we release 3.0-beta-2 > *without* merging the proposed code. There are two reasons for this. Lets stage them both, I don't see any harm in having them back to back, it certainly could help isolate any regressions.

Re: Merging in our Aether and Guice changes to Maven 3.x

Hi all Some very important questions have been asked regarding Jason's proposal. I usually let my first impressions sink in a bit before I reply. That often help to make my comments more about the facts and less about the feelings, and we've seen a lot of feelings in this thread. The first thing

Re: [VOTE] Release Maven SCM 1.4 (Take 2)

yes sure. 2010/8/5 Evgeny Mandrikov : > BTW, Olivier, do you have plans to release maven-scm-provider-svnjava > 1.11 after release of Maven SCM 1.4 ? > > On Thu, Aug 5, 2010 at 20:03, Evgeny Mandrikov wrote: >> +1 >> >> On Thu, Aug 5, 2010 at 19:09, John Casey wrote: >>> +1 >>> >>> On 8/5/10 10:

Re: [ANN] Maven Doxia Tools 1.1 Released

Actually it's not an error, but I should have explained it more. The artifact doxia-tools is just a parent with pom packaging. In the multi module build there are two artifacts with jar packaging. The first is doxia-linkcheck and the other is doxia-converter. I should have included POM snippets fo

Re: [VOTE] Release Maven SCM 1.4 (Take 2)

BTW, Olivier, do you have plans to release maven-scm-provider-svnjava 1.11 after release of Maven SCM 1.4 ? On Thu, Aug 5, 2010 at 20:03, Evgeny Mandrikov wrote: > +1 > > On Thu, Aug 5, 2010 at 19:09, John Casey wrote: >> +1 >> >> On 8/5/10 10:15 AM, Olivier Lamy wrote: >>> >>> 2010/8/5 Olivier

Re: [VOTE] Release Maven SCM 1.4 (Take 2)

+1 On Thu, Aug 5, 2010 at 19:09, John Casey wrote: > +1 > > On 8/5/10 10:15 AM, Olivier Lamy wrote: >> >> 2010/8/5 Olivier Lamy: >>> >>> Hi, >>> >>> In preparation of the Release Plugin release, I'd like to release Maven >>> Scm 1.4. >>> Change since first try : fix for SCM-568 >>> We solved 23 i

Re: [VOTE] Release Maven SCM 1.4 (Take 2)

+1 On 8/5/10 10:15 AM, Olivier Lamy wrote: 2010/8/5 Olivier Lamy: Hi, In preparation of the Release Plugin release, I'd like to release Maven Scm 1.4. Change since first try : fix for SCM-568 We solved 23 issues : http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10527&version=16128

Re: Where is maven-toolchain for M3?

I don't think org.apache.maven.toolchain.java should ever have been in maven-toolchain, it should have lived in its own artifact. maven-toolchain was tied to core, and AFAIK the core classloader will always win in such cases, so the net result is it is not possible to add the extra methods that we

Re: Where is maven-toolchain for M3?

I'll think about that overnight... and perhaps discuss with Benjamin the implications on IRC tomorrow. If I feel it's better out I'll call a vote first. If we are taking it out I'd rather see it removed before 3.0-beta-2. My thinking is that we remove the org.apache.maven.toolchain.java package

Re: Where is maven-toolchain for M3?

Stephen Connolly wrote: So if I want to add more core toolchains I now have to push the changes to core, or will the classloader always take from core and not from a newer maven-toolchains dep of a plugin? Not sure what you mean with "core toolchain" here, at least in M3 you should be free to

Re: Where is maven-toolchain for M3?

Or should I just create a new component for to hold toolchains and their factories... that way if multiple plugins need the same non-core toolchains, at least there is only one dependency that is needed. I'm looking at MINVOKER-100 and the supplied patch does not smell good to me, so I'm thinking

Re: Where is maven-toolchain for M3?

Maybe just decouple it completely from the core if you think it's going to vary that much. I would be for completely extracting it. On Aug 5, 2010, at 10:27 AM, Stephen Connolly wrote: > H > > So if I want to add more core toolchains I now have to push the changes to > core, or will the cl

Re: Where is maven-toolchain for M3?

H So if I want to add more core toolchains I now have to push the changes to core, or will the classloader always take from core and not from a newer maven-toolchains dep of a plugin? -Stephen On 5 August 2010 15:25, Jason van Zyl wrote: > > https://svn.apache.org/repos/asf/maven/maven-3/t

Re: Where is maven-toolchain for M3?

Stephen Connolly wrote: Where is maven-toolchain... maven-core Benjamin - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org

Re: Where is maven-toolchain for M3?

https://svn.apache.org/repos/asf/maven/maven-3/trunk/maven-core/src/main/java/org/apache/maven/toolchain/ On Aug 5, 2010, at 10:21 AM, Stephen Connolly wrote: > Where is maven-toolchain... the last one I can find in SVN: > https://svn.apache.org/repos/asf/maven/maven-2/branches/maven-2.2.x/maven-

Re: Merging in our Aether and Guice changes to Maven 3.x

Having worked with Aether yesterday in some test code, and after sleeping on it last night, I'll withdraw my objections for now. This looks like a good way forward in terms of code. I'm still concerned about volatility in terms of writing plugins that need to resolve X or Y artifact at runtime

Re: Where is maven-toolchain for M3?

OK, I can see: r789006 | bentmann | 2009-06-27 19:18:46 +0100 (Sat, 27 Jun 2009) | 1 line Changed paths: M /maven/components/trunk/apache-maven/pom.xml M /maven/components/trunk/maven-core/pom.xml M /maven/components

Where is maven-toolchain for M3?

Where is maven-toolchain... the last one I can find in SVN: https://svn.apache.org/repos/asf/maven/maven-2/branches/maven-2.2.x/maven-toolchain repo1, shows that there was a 3.0-alpha-1 and 3.0-alpha-2 release but no 3.0-beta-1 release... http://repo1.maven.org/maven2/org/apache/maven/maven-toolch

Re: [VOTE] Release Maven SCM 1.4 (Take 2)

2010/8/5 Olivier Lamy : > Hi, > > In preparation of the Release Plugin release, I'd like to release Maven Scm > 1.4. > Change since first try : fix for SCM-568 > We solved 23 issues : > http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10527&version=16128 > > Staging repo: > https://repos

[VOTE] Release Maven SCM 1.4 (Take 2)

Hi, In preparation of the Release Plugin release, I'd like to release Maven Scm 1.4. Change since first try : fix for SCM-568 We solved 23 issues : http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10527&version=16128 Staging repo: https://repository.apache.org/content/repositories/maven

Re: Resolving SNAPSHOTs from Version Ranges in Maven 3

Mark Derricutt wrote: Ideally, what I'd love to see is a way of allowing -SNAPSHOT resolution in ranges as an option, so that for those particular artifacts that need it, still get them. Thoughts? Vote on http://jira.codehaus.org/browse/MNG-4751 Benjamin ---

Re: Merging in our Aether and Guice changes to Maven 3.x

A thing I forgot to add yesterday : For me Maven is a success because of its fundamentals (rules/guidelines) which allowed to created a large large variety of services with plugins. The value of Maven is many many more in its plugins than in its core (I don't want to reduce the work done on it

Re: [VOTE] Release Maven SCM 1.4

Sorry for that and yes - cvs is a pain. On Thu, Aug 5, 2010 at 16:03, Olivier Lamy wrote: > So vote cancelled I will restart a new process. > > arf cvs pain of my life :-) > > 2010/8/5 Evgeny Mandrikov : >> Yes - it's blocker. >> >> On Thu, Aug 5, 2010 at 10:46, Olivier Lamy wrote: >>> Is it blo

Re: [VOTE] Release Maven SCM 1.4

So vote cancelled I will restart a new process. arf cvs pain of my life :-) 2010/8/5 Evgeny Mandrikov : > Yes - it's blocker. > > On Thu, Aug 5, 2010 at 10:46, Olivier Lamy wrote: >> Is it blocker for something for you ? (I mean in the sonar stuff ). >> If yes, I can certainly cancel the vote an

Re: [VOTE] Release Maven Linkcheck Plugin version 1.0

+1 2010/8/5 Dennis Lundberg : > Hi, > > This is the first release of this plugin. There are no issues in JIRA. > > If you want to see it in action, it has been configured in a profile > called "linkcheck" in the POM for the Maven site. > > Staging repo: > https://repository.apache.org/content/repo

Re: [VOTE] Release Maven Linkcheck Plugin version 1.0

+1 Emmanuel On Thu, Aug 5, 2010 at 12:41 AM, Dennis Lundberg wrote: > Hi, > > This is the first release of this plugin. There are no issues in JIRA. > > If you want to see it in action, it has been configured in a profile > called "linkcheck" in the POM for the Maven site. > > Staging repo: > h

Re: [VOTE] Release Maven Linkcheck Plugin version 1.0

+1 -Lukas Dennis Lundberg wrote: Hi, This is the first release of this plugin. There are no issues in JIRA. If you want to see it in action, it has been configured in a profile called "linkcheck" in the POM for the Maven site. Staging repo: https://repository.apache.org/content/repositorie

Re: [VOTE] Release Maven SCM 1.4

Yes - it's blocker. On Thu, Aug 5, 2010 at 10:46, Olivier Lamy wrote: > Is it blocker for something for you ? (I mean in the sonar stuff ). > If yes, I can certainly cancel the vote and restart the process. > Let me know. > > 2010/8/5 Evgeny Mandrikov : >> Hi Olivier, >> >> Looks like patch for S

Re: [VOTE] Release Maven Linkcheck Plugin version 1.0

Dennis Lundberg wrote: Staging repo: https://repository.apache.org/content/repositories/maven-066/ Staging site: http://maven.apache.org/plugins/maven-linkcheck-plugin-1.0/ +1 Benjamin - To unsubscribe, e-mail: dev-unsubsc

Re: Merging in our Aether and Guice changes to Maven 3.x

OK, I am going to round off my view on the topic. Guice integration: +1 Aether integration: +0.99 _for now_... let's suck it and see... if it works well and the interaction between the two code bases works well, then all is good. There is a generic issue when we have volunteers and paid for

Re: Merging in our Aether and Guice changes to Maven 3.x

Hi there, As for Guice, I think that what JVZ said does stands: a very few people does understand how big and complex that work was (and is, since it is ongoing). Stuart did a real magic, with just a "drop in" replacement for Plexus-components backed by Guice. But don't stop there. With his founda

Re: Merging in our Aether and Guice changes to Maven 3.x

Mark Derricutt wrote: Can the guice stuff be merged in cleanly independent of aether? Yes, see patch at http://jira.codehaus.org/browse/MNG-4749. There are no interdependencies between Aether and the Plexus-Guice-Bridge. The Git branch I mentioned earlier aggregates them for the sole purpos

Re: [ANN] Maven Doxia Tools 1.1 Released

Yes, clearly a copy-paste error from another release Dennis is doing right now. The artifactId should be 'doxia-tools'. /Anders On Thu, Aug 5, 2010 at 09:51, Tony Chemit wrote: > Le Wed, 04 Aug 2010 23:53:49 +0200, > Dennis Lundberg a écrit : > > > The Maven team is pleased to announce the rele

Re: [ANN] Maven Doxia Tools 1.1 Released

Le Wed, 04 Aug 2010 23:53:49 +0200, Dennis Lundberg a écrit : > The Maven team is pleased to announce the release of the Maven Doxia > Tools, version 1.1 > > Doxia Tools is a set of tools for working with Doxia documents. It > contains a Converter and a Linkchecker. > > http://maven.apache.org/