Re: Maven 2.0.10-RC4

Ah :) perhaps "fixed in RCx" as the last comment is enough? - Brett On 01/08/2008, at 1:35 PM, Paul Benedict wrote: Brett, I know those discussions existed. I was apart of them :-) and I recommended we should not create extra JIRA versions for 1 and 2 tickets. My question this time, however

Re: Maven 2.0.10-RC4

Brett, I know those discussions existed. I was apart of them :-) and I recommended we should not create extra JIRA versions for 1 and 2 tickets. My question this time, however, is a bit different. I just wanted to know if we should somehow mark the ticket with RC1, RC2, etc. within the version just

[jira] Subscription: Design & Best Practices

Issue Subscription Filter: Design & Best Practices (28 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 htt

RE: Maven 2.0.10-RC4

Until we actually think all the known issues are resolved, we shouldn't send it to [EMAIL PROTECTED] We don't want to lose their attention by bringing RCs in an early stage. -Original Message- From: John Casey [mailto:[EMAIL PROTECTED] Sent: Thursday, July 31, 2008 6:04 PM To: Maven Deve

RE: Vmware (Was: Maven 2.0.10-RC3 - Please Test!)

You can't run osx on vmware (legally at least) because it requires apple hardware in the license. (who's the monopoly now) -Original Message- From: Vincent Siveton [mailto:[EMAIL PROTECTED] Sent: Thursday, July 31, 2008 6:45 PM To: Maven Developers List Subject: Vmware (Was: Maven 2.0

[VOTE] Release Maven IDEA plugin version 2.2

Hi, We solved 8 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11135&styleName=Html&version=13580 There are still a couple of issues left in JIRA: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11135&status=1 Staging repo: http://people.apache.org/~dennis

Vmware (Was: Maven 2.0.10-RC3 - Please Test!)

Hi guys, 2008/7/31 John Casey <[EMAIL PROTECTED]>: [SNIP] > BTW, I'm running on OS X. Maybe a dummy question but do we have in Apache world some Vmware files? Cheers, Vincent - To unsubscribe, e-mail: [EMAIL PROTECTED] For add

Re: [VOTE] Release Maven Filtering version 1.0-alpha-1

2008/7/31 Dennis Lundberg <[EMAIL PROTECTED]>: > Olivier Lamy wrote: >> >> Hi Dennis, >> Ok I understand the point. >> But nothing prevent us to republish the site with this the scm url fix > > Actually it does, because that site would then be labeled with the next > version (1.0-beta-1-SNAPSHOT).

Re: Maven 2.0.10-RC4

Hi Benjamin, For the first one, I guess that javadoc:javadoc was not call from core. For jdk6, I have no clue about BSH but I noticed that maven-javadoc-plugin version is 2.4 and not 2.5-snap. Thanks to have a glance :) Vincent 2008/7/31 Benjamin Bentmann <[EMAIL PROTECTED]>: > Vincent Siveton

Re: [VOTE] Release Maven Filtering version 1.0-alpha-1

2008/7/31 Dennis Lundberg <[EMAIL PROTECTED]>: > Thanks for pushing this towards a release! > > +1 on promotion from sandbox > > -1 on release due to bad spelling of the file name of a public class. Fixed > in svn r681499. Ok, I will cancel this and do an other release. > > > Also I have some que

Re: Maven 2.0.10-RC4

Vincent Siveton wrote: I tried RC4 under javadoc plugin and I have now 3 ITs failures on my side: MJAVADOC-172 MJAVADOC-180 MJAVADOC-194 MJAVADOC-180 is a strange one: The IT's verify.bsh is run only if System.getProperty( "java.specification.version" ).equals( "1.5" ) ?? Anyway, I run "mvn

Re: Maven 2.0.10-RC4

We already had that discussion and decided it would be overkill - once 2.0.10 is released nobody will be concerned with the difference between these release candidates (And they won't be available for download any more anyway). There are few enough changes between each that you can use time

Re: Maven 2.0.10-RC4

Yes, I believe this would be a good candidate to push to [EMAIL PROTECTED] I'll put together the message now. It's worth remembering that we may have a problem expressed somewhere in the javadoc plugin, so this may not be the last RC. But it's becoming must more stable with this RC. -john B

Re: Maven 2.0.10-RC4

Until I can get the javadoc plugin working on OS X there's nothing I can do to even peek at this. Why is it failing? Can you formulate a MNG issue with the relevant details that are causing the ITs to fail? If I had some sort of set of steps to reproduce the problem, it would help a lot. -jo

Re: Maven 2.0.10-RC4

OTOH, there is a 'Fix Version' property in JIRA that you can use to assign a release/build/version id. Rahul On Fri, Aug 1, 2008 at 9:28 AM, Paul Benedict <[EMAIL PROTECTED]> wrote: > Is there anywhere in JIRA we can tag some issues as being fixed in RC1, RC2, > etc.? I liked how Bugzilla had fla

Re: [VOTE] Release Maven Filtering version 1.0-alpha-1

Thanks for pushing this towards a release! +1 on promotion from sandbox -1 on release due to bad spelling of the file name of a public class. Fixed in svn r681499. Also I have some questions, after reading the docs (I fixed some minor documentation issues in SVN). Disclaimer: I haven't use

Re: svn commit: r681482 - /maven/sandbox/trunk/shared/maven-filtering/src/main/java/org/apache/maven/shared/filtering/

Dennis Lundberg wrote: Also, we need to add some IDE tricks to avoid these errors. Yes, these errors were caught by IDEA. Eclipse has likewise options to check javadocs (Window > Preferences > Java > Compiler > Javadoc). Benjamin -

Re: [VOTE] Release Maven Filtering version 1.0-alpha-1

Olivier Lamy wrote: Hi Dennis, Ok I understand the point. But nothing prevent us to republish the site with this the scm url fix Actually it does, because that site would then be labeled with the next version (1.0-beta-1-SNAPSHOT). That is confusing to the users and we should try to avoid it

Re: Maven 2.0.10-RC4

Is there anywhere in JIRA we can tag some issues as being fixed in RC1, RC2, etc.? I liked how Bugzilla had flags to mark items. Anything like that in JIRA? Paul On Thu, Jul 31, 2008 at 4:16 PM, Brett Porter <[EMAIL PROTECTED]> wrote: > Would this be a good one to push to users@, particularly hi

Re: svn commit: r681482 - /maven/sandbox/trunk/shared/maven-filtering/src/main/java/org/apache/maven/shared/filtering/

Vincent Siveton wrote: Hi Dennis, 2008/7/31 <[EMAIL PROTECTED]>: Author: dennisl Date: Thu Jul 31 13:52:45 2008 New Revision: 681482 URL: http://svn.apache.org/viewvc?rev=681482&view=rev Log: o Remove date based @since tags. o Fix Javadoc errors. [SNIP] public class CompositeMap @@ -4

Re: [VOTE] Release Maven Filtering version 1.0-alpha-1

Hi Dennis, Ok I understand the point. But nothing prevent us to republish the site with this the scm url fix (btw thanks to you and vincent for documentation fix). -- Olivier 2008/7/31 Dennis Lundberg <[EMAIL PROTECTED]>: > This is usually done in two steps, with some maintenance work in-between:

Re: Maven 2.0.10-RC4

Would this be a good one to push to users@, particularly highlighting the need to test projects with creative uses of interpolation and various deployment setups? Cheers, Brett On 01/08/2008, at 6:50 AM, John Casey wrote: Hi, I've got a new release candidate for people to try out: http:/

Re: svn commit: r681482 - /maven/sandbox/trunk/shared/maven-filtering/src/main/java/org/apache/maven/shared/filtering/

Hi Dennis, 2008/7/31 <[EMAIL PROTECTED]>: > Author: dennisl > Date: Thu Jul 31 13:52:45 2008 > New Revision: 681482 > > URL: http://svn.apache.org/viewvc?rev=681482&view=rev > Log: > o Remove date based @since tags. > o Fix Javadoc errors. > [SNIP] > public class CompositeMap > @@ -44,7 +43,

Re: Maven 2.0.10-RC4

Hi John, I tried RC4 under javadoc plugin and I have now 3 ITs failures on my side: MJAVADOC-172 MJAVADOC-180 MJAVADOC-194 Cheers, Vincent 2008/7/31 John Casey <[EMAIL PROTECTED]>: > Hi, > > I've got a new release candidate for people to try out: > > http://people.apache.org/~jdcasey/stage/apac

Maven 2.0.10-RC4

Hi, I've got a new release candidate for people to try out: http://people.apache.org/~jdcasey/stage/apache-maven/2.0.10-RC4/org/apache/maven/apache-maven/2.0.10-RC4/ Major changes: - Bumped wagon version to 1.0-beta-4 - Improved handling of mirror definitions without an element The only outs

Re: Releasng the war and deploy plugins

Hi, Due to MINVOKER-43, you can't release it with the current trunk without a small change :-(. You have to disable the feature from the version 1.2 [1] or use the workaround like this commit [2]. -- Olivier [1] http://maven.apache.org/plugins/maven-invoker-plugin/examples/fast-use.html [2] http:

Re: [VOTE] Release Maven Filtering version 1.0-alpha-1

On 01/08/2008, at 6:01 AM, Dennis Lundberg wrote: This is usually done in two steps, with some maintenance work in- between: 1. promote from sandbox 2. Fix SCM URLs, site etc due to the promotion from sandbox 3. release I think all the SCM information in the release is correct, the trunk

Re: Releasng the war and deploy plugins

On Fri, May 9, 2008 at 1:38 PM, Olivier Lamy <[EMAIL PROTECTED]> wrote: > Hi, > No objections. > But currently the war plugin trunk depends on other snapshots : > - org.apache.maven.plugins:maven-invoker-plugin:1.2-SNAPSHOT > - org.apache.maven.shared:maven-filtering:1.0-alpha-1-SNAPSHOT > > The fi

Re: [VOTE] Release Maven DOAP plugin version 1.0

+1 On 29/07/2008, at 9:45 AM, Vincent Siveton wrote: Hi, We solved 10 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11310&styleName=Html&version=13182 There are just one issue left in JIRA: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11310&status=1

Re: [VOTE] Release Maven Filtering version 1.0-alpha-1

This is usually done in two steps, with some maintenance work in-between: 1. promote from sandbox 2. Fix SCM URLs, site etc due to the promotion from sandbox 3. release Olivier Lamy wrote: Hi, In preparation of the maven-war-plugin, I'd like to release and promote out of the sandbox the mave

Verify Deploy

Hello: I am trying to write a plugin to verify deployment of artifacts. The user story is: 1.project a is built (clean, install) from repo a 2.project a deploys (deploy via distribution management) to repo b 3.project a is built (clean, install) from repo b 4.all the above are done with one mave

Re: Maven 2.0.10-RC3 - Please Test!

This is not the case on my machine. I've been very careful NOT to set M2_HOME, JAVA_HOME, or CLASSPATH on my machine. The first two are set using a mvn delegating script in ~/bin that sets the maven version and jdk version before calling the real maven script. I've just verified that CLASSPATH

Re: POM rewriting with DecentXML

Michael McCallum schrieb: > there is already that is worth considering... its goal > is > correctness and roundtripability ;-)... its mature and stable... i have used > it and been very happy xom doesn't preserve whitespace in elements (no XML parser besides DecentXML can d

Re: Maven 2.0.10-RC3 - Please Test!

Hi John, Maybe your pb was related to CLASSPATH as said by Stephen. FYI I am able to built it with 1.4, 1.5 and 1.6 and mvn 2.0.9 on two stations and Hudson was happy yesterday. Unfortunately, with rc3, it's failing on twice. The twice javadoc ITs seem to not call javadoc goal, and so apidocs out

Re: Maven 2.0.10-RC3 - Please Test!

Hi Paul, 2008/7/31 Paul Benedict <[EMAIL PROTECTED]>: > Would it behoove the Javadoc plugin developers to test for the CLASSPATH > variable? Issue a warning instead of blowing up? I know it's not a plugin > problem, per se, but it obviously leads some people to believe it is. The last entry in th

Re: repository metadata was: bouncycastle in central

On 01/08/2008, at 3:16 AM, Benjamin Bentmann wrote: John Casey wrote: To me, all of this points to a dire need to separate dependency metadata from the POM that all of these derivative artifacts shares. I could imagine this would also ease long-term interoperability of different Maven ve

Re: Maven 2.0.10-RC3 - Please Test!

Would it behoove the Javadoc plugin developers to test for the CLASSPATH variable? Issue a warning instead of blowing up? I know it's not a plugin problem, per se, but it obviously leads some people to believe it is. Paul On Thu, Jul 31, 2008 at 12:43 PM, Stephen Connolly < [EMAIL PROTECTED]> wro

Re: bouncycastle in central was: Mojo for validating PGP signature

On Thu, Jul 31, 2008 at 6:55 PM, Stephen Connolly < [EMAIL PROTECTED]> wrote: > But perhaps it should be! > > Consider this case... > > I have an artifact foo... it depends on bar... it does not really care what > JDK > > Another artifact manchu also depends on bar... but it needs the jdk14 > vers

Re: Maven 2.0.10-RC3 - Please Test!

The core release doesn't have any dependency on SCM - I think you are looking for native support in the release plugin? Cheers, Brett On 01/08/2008, at 12:27 AM, Mark Struberg wrote: Is there a chance to get maven-2.0.10 running with maven-scm-1.1? You know, I'd like to see native git suppo

Re: bouncycastle in central was: Mojo for validating PGP signature

But perhaps it should be! Consider this case... I have an artifact foo... it depends on bar... it does not really care what JDK Another artifact manchu also depends on bar... but it needs the jdk14 version My webapp foomanchu depends on both foo and manchu and is targetted at jdk14, while the

Re: Maven 2.0.10-RC3 - Please Test!

check if the CLASSPATH environment variable is set. it blows up javadoc if it is Sent from my iPod On 31 Jul 2008, at 18:06, John Casey <[EMAIL PROTECTED]> wrote: Hi Vincent, I can't even get the javadoc plugin to run on my machine under Maven 2.0.9, not with JDK 1.4 or JDK 1.6...so I'm a

Re: bouncycastle in central was: Mojo for validating PGP signature

John Casey wrote: I've been talking to various people in the Maven community about this sort of thing for ages, probably more than two years at this point. Some of the most interesting conversations come when you talk to people interested in using Maven to build C projects, where certain lib

Re: bouncycastle in central was: Mojo for validating PGP signature

John Casey wrote: To me, all of this points to a dire need to separate dependency metadata from the POM that all of these derivative artifacts shares. I could imagine this would also ease long-term interoperability of different Maven versions with the repository. Imagine the day when the POM

Re: Maven 2.0.10-RC3 - Please Test!

Hi Vincent, I can't even get the javadoc plugin to run on my machine under Maven 2.0.9, not with JDK 1.4 or JDK 1.6...so I'm afraid I'm of little use on these issues. I can give you some time to distill a failing test case that I can pursue, if you like... Let me know. Maybe I'll cut the RC4

Re: bouncycastle in central was: Mojo for validating PGP signature

I've been talking to various people in the Maven community about this sort of thing for ages, probably more than two years at this point. Some of the most interesting conversations come when you talk to people interested in using Maven to build C projects, where certain libraries are required t

Re: bouncycastle in central was: Mojo for validating PGP signature

Jason van Zyl wrote: That's really not fundamentally different then just using a different artifact id. I think where I'm going is that classifiers are not suitable for the bits that make up the build path and classpath. Those are really for secondary artifacts like javadoc jars and source ja

Re: bouncycastle in central was: Mojo for validating PGP signature

That's really not fundamentally different then just using a different artifact id. I think where I'm going is that classifiers are not suitable for the bits that make up the build path and classpath. Those are really for secondary artifacts like javadoc jars and source jars. On 31-Jul-08, a

Re: bouncycastle in central was: Mojo for validating PGP signature

On 31-Jul-08, at 8:04 AM, Jesse McConnell wrote: Maybe we extend the definition of a classifier to explicitly refer to things like sources and javadocs which have no impact on the dependency requirements. GWT for the MAC is really a different artifact then GWT for Linux and maybe we should

Re: bouncycastle in central was: Mojo for validating PGP signature

To me that seems over complicated in that you need a whole other sub- system in Maven to define the requirements of a target. Why not just state explicitly what the target needs and dispense with the rest of the machinery. Dependencies accrued via profiles is a very nasty beast in the projec

Re: bouncycastle in central was: Mojo for validating PGP signature

My solution is to allow pom's with classifiers! That way the -jdk14 jar has a -jdk14 pom to specify it's dependencies. If the pom is not there then you assume the pom for without the classifier thus not requiring a DOM change... i.e. could be made work for 2.0.11. And plus it will only affect

Re: bouncycastle in central was: Mojo for validating PGP signature

I had some ideas about expanding classifier usage for use with NMaven. May be worth a look: http://docs.codehaus.org/display/MAVENUSER/Expanded+Classifier+Support Shane On Thu, Jul 31, 2008 at 8:04 AM, Jesse McConnell <[EMAIL PROTECTED]>wrote: > > Maybe we extend the definition of a classifier t

Re: bouncycastle in central was: Mojo for validating PGP signature

> Maybe we extend the definition of a classifier to explicitly refer to things > like sources and javadocs which have no impact on the dependency > requirements. GWT for the MAC is really a different artifact then GWT for > Linux and maybe we should just start treating them as such. > This is what

Re: bouncycastle in central was: Mojo for validating PGP signature

Yea, there are bunches of examples. Any JAX-WS or JAXB thing wouldn't need the jaxb/jaxws api jars if running on Java 6. Recent xml apis are in java 5. Java 7 will probably have a ton of other things. I'm wondering if we could activate profiles based on classifiers.

Re: bouncycastle in central was: Mojo for validating PGP signature

On Thu, Jul 31, 2008 at 4:43 PM, Jason van Zyl <[EMAIL PROTECTED]> wrote: > If it is the case where it is common that for a given GAV the classified > artifact requires different dependencies then I think we have some flaws in > the system. But that seems to be quite naturally to me. Consider the

Re: bouncycastle in central was: Mojo for validating PGP signature

I just started dialog with the BC guys to look at Mercury so I will see what there thoughts are. If it is the case where it is common that for a given GAV the classified artifact requires different dependencies then I think we have some flaws in the system. It means we just ran out of runwa

RE: Maven 2.0.10-RC3 - Please Test!

We're already started the RC process so only blocking issues and regressions are being included. -Original Message- From: Mark Struberg [mailto:[EMAIL PROTECTED] Sent: Thursday, July 31, 2008 10:28 AM To: Maven Developers List Subject: Re: Maven 2.0.10-RC3 - Please Test! Is there a chan

Re: Maven 2.0.10-RC3 - Please Test!

Is there a chance to get maven-2.0.10 running with maven-scm-1.1? You know, I'd like to see native git support in maven ;) LieGrü, strub --- Vincent Siveton <[EMAIL PROTECTED]> schrieb am Do, 31.7.2008: > Von: Vincent Siveton <[EMAIL PROTECTED]> > Betreff: Re: Maven 2.0.10-RC3 - Please Test! >

Re: A wiki page has gone ...

I given a wrong link. The erroneous link is here : http://maven.apache.org/guides/development/guide-m2-development.html I'm updating the doc cheers On Thu, Jul 31, 2008 at 2:01 PM, Arnaud HERITIER <[EMAIL PROTECTED]>wrote: > ok guys > I do the update and republish the site. > thx > > > On Thu,

Re: Maven 2.0.10-RC3 - Please Test!

Hi John, With RC-3, Javadoc ITs (MJAVADOC-172 and MJAVADOC-194) failed. Sounds like an issue in the invoker-plugin (defined as 1.2 in the pom). Unfortunately, I tried with 1.2.1-snap without success. So it is probably in the core. Could you have a glance? Last step before calling a vote ;) Cheers

Re: A wiki page has gone ...

ok guys I do the update and republish the site. thx On Thu, Jul 31, 2008 at 1:59 PM, Dennis Lundberg <[EMAIL PROTECTED]> wrote: > Arnaud HERITIER wrote: > >> Hi guys, >> >> i noticed that this page [1] wasremoved from the wiki but there's always >> a >> link to it in our documentation [2] >> Sh

Re: A wiki page has gone ...

Arnaud HERITIER wrote: Hi guys, i noticed that this page [1] wasremoved from the wiki but there's always a link to it in our documentation [2] Should we restore the page or update our doc ? [1] http://docs.codehaus.org/display/MAVEN/How+to+help [2] http://maven.apache.org/guides/development

Re: A wiki page has gone ...

Hi, 2008/7/31 Arnaud HERITIER <[EMAIL PROTECTED]>: > Hi guys, > > i noticed that this page [1] wasremoved from the wiki but there's always a > link to it in our documentation [2] > Should we restore the page or update our doc ? +1 to update doc. Adding a link to http://maven.apache.org/guides/d

A wiki page has gone ...

Hi guys, i noticed that this page [1] wasremoved from the wiki but there's always a link to it in our documentation [2] Should we restore the page or update our doc ? [1] http://docs.codehaus.org/display/MAVEN/How+to+help [2] http://maven.apache.org/guides/development/guide-building-m2.html -

Re: bouncycastle in central was: Mojo for validating PGP signature

2008/7/23 Brett Porter <[EMAIL PROTECTED]>: > On 23/07/2008, at 1:34 AM, Jason van Zyl wrote: >> Ok, >> >> I have a package for the new 140 version as that's what I'm using but what >> they have in central currently doesn't use classifiers which is probably not >> so good. >> >> http://repo1.maven.

RE: CI job maven-shared: fail-at-end?

Yep, fixed that. The deadlock on the wrong jdk must be new in the updated Hudson. -Original Message- From: Benjamin Bentmann [mailto:[EMAIL PROTECTED] Sent: Thursday, July 31, 2008 4:15 AM To: Maven Developers List Subject: Re: CI job maven-shared: fail-at-end? Brian E. Fox wrote: > Fix

Re: [VOTE] Release Maven DOAP plugin version 1.0

+1 -Lukas Vincent Siveton wrote: Hi, We solved 10 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11310&styleName=Html&version=13182 There are just one issue left in JIRA: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11310&status=1 Staging repo: http

Re: [VOTE] Release Maven Filtering version 1.0-alpha-1

+1 BTW I fixed some typo in the documentation. Cheers, Vincent 2008/7/29 Olivier Lamy <[EMAIL PROTECTED]>: > Hi, > In preparation of the maven-war-plugin, I'd like to release and > promote out of the sandbox the maven-filtering component version > 1.0-alpha-1. > The goal of this component is to

Re: CI job maven-shared: fail-at-end?

Brian E. Fox wrote: Fixed now, never seen that happen before so I'll keep an eye out. Thanks! Can you also have a look at https://ci.sonatype.org/job/maven-2.0.10-RC/2/console I assume the job needs to be reconfigured to use Java 1.5 or each build will deadlock again. Benjamin

Re: CI job maven-shared: fail-at-end?

ok for me. I completly forgot the -fae option in maven. :-) On Wed, Jul 30, 2008 at 7:15 PM, Brian Fox <[EMAIL PROTECTED]> wrote: > Just add -fae to the goals line. Until I verify the use separate repo works > I prefer to use the maven switch directly > > Sent from my iPhone > > On Jul 30, 2008