Re: where are :3.0-alpha-2-SNAPSHOT artifacts of maven-artifact

The auto parenting feature is on this branch, which does not require that snapshot: http://svn.apache.org/repos/asf/maven/components/branches/maven-2.1.x-MNG-624/ - Brett On 05/09/2008, at 8:35 AM, Harsha Godugu wrote: Hi There, I'm trying to build maven 2.1. (to try the auto parenting

where are :3.0-alpha-2-SNAPSHOT artifacts of maven-artifact

Hi There, I'm trying to build maven 2.1. (to try the auto parenting feature) I see the repo as : http://people.apache.org/repo/m2-snapshot-repository/ from the pom.xml in maven-components I get the folloing error stated below. I looked for the 3.0 snapshot repo at the above url. It's no

[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: Wagon problems, maybe somebody has answers?

Thats a bit crappy - does mercury force you to work with Files instead of streams? Quite the opposite - Mercury transport itself does all the work, including Stream Verifiers and so on, I just plug it into wagon and it does the file put/get. Moreover - that layer ensures transactional integ

Re: Wagon problems, maybe somebody has answers?

Hey Oleg, On Thu, 2008-09-04 at 18:11 -0700, Oleg Gusakov wrote: > James - thanks a lot for the reply! > No problems :) > James William Dumay wrote: > > > > Because these are used to track download progress - if you are using a > > Stream based protocol then the StreamWagon abstract class will

Re: Wagon problems, maybe somebody has answers?

James - thanks a lot for the reply! James William Dumay wrote: Because these are used to track download progress - if you are using a Stream based protocol then the StreamWagon abstract class will take care of this for you. My transport layer operates on files, so I cannot do streaming wagon

Re: Wagon problems, maybe somebody has answers?

Hey Oleg, On Thu, 2008-09-04 at 14:00 -0700, Oleg Gusakov wrote: > I tried to create mercury-based wagon provider and got overwhelmed with > Wagon's strange architecture decisions and APIs. > > First of all - inheriting from AbstractWagon and implementing required > methods took 20 min - excell

[RESULT] [VOTE] release versions-maven-plugin 1.0-alpha-1

On Tue, Sep 2, 2008 at 12:07 AM, Stephen Connolly < [EMAIL PROTECTED]> wrote: > Vote will be open for 72 hours and will conclude via lazy consensus. > This vote has passed: +1: Benjamin V. 0: Benjamin B. Thanks for reviewing and helpful comments go to: Benjamin B, Dennis and Nicolas. I will fi

Wagon problems, maybe somebody has answers?

I tried to create mercury-based wagon provider and got overwhelmed with Wagon's strange architecture decisions and APIs. First of all - inheriting from AbstractWagon and implementing required methods took 20 min - excellent! The rest two days (are still being) spent trying to understand: - w

Re: [PLEASE TEST] Maven 2.1.0-M1-RC13

I've replicated this problem in some of my own projects. It seems that the key is to have the compiler plugin configured in the pluginManagement section of the POM, and then to enable a report like the javadoc reports that will cause the lifecycle to fork and compile sources. At that point, it

preparing for enforcer alpha-4 release

I updated the maven dependencies in the enforcer from 2.0.6 to 2.0.9 and pushed out a 1.0-alpha-4-SNAPSHOT, please try it out and let me know if you see any problems. If nothing turns up, then I'll stage it tomorrow or this weekend for a vote. Thanks. -- Brian Fox Apac

RE: the new help plugin doesn't work with 2.1/3.0

Are you sure it's the same, MPH-38 doesn't mention a link error. -Original Message- From: Vincent Siveton [mailto:[EMAIL PROTECTED] Sent: Thursday, September 04, 2008 1:44 PM To: Maven Developers List Subject: Re: the new help plugin doesn't work with 2.1/3.0 Hi Brian, It is a known iss

Re: the new help plugin doesn't work with 2.1/3.0

Hi Brian, It is a known issue: MPH-38 Cheers, Vincent 2008/9/4, Brian E. Fox <[EMAIL PROTECTED]>: > I get this with the embedder: > > > > [INFO] Searching repository for plugin with prefix: 'help'. > > [INFO] Attempting to resolve a version for plugin: > org.apache.maven.plugins:maven-help-p

the new help plugin doesn't work with 2.1/3.0

I get this with the embedder: [INFO] Searching repository for plugin with prefix: 'help'. [INFO] Attempting to resolve a version for plugin: org.apache.maven.plugins:maven-help-plugin using meta-version: LATEST [INFO] snapshot org.apache.maven.plugins:maven-help-plugin:2.1.1-SNAPSHOT: checkin

Re: [PLEASE TEST] Maven 2.1.0-M1-RC13

I was having a lot of problems related to nonstandard local repository settings and the repository manager in between these builds and the central repo, so I've been basically running all the community builds on my machine to make sure things are happy. This way I can make sure all artifacts ar

Re: [PLEASE TEST] Maven 2.1.0-M1-RC13

Thanks a lot. I tested it and I didn't found regressions. arnaud On Thu, Sep 4, 2008 at 2:50 AM, John Casey <[EMAIL PROTECTED]> wrote: > Hi again everyone, > > On the last go around, we had one issue pop up with maven plugin builds > (though it might also apply to build extensions in the reacto

Re: [VOTE] Release Maven Help plugin version 2.1 (take 2)

The vote has passed with the following votes: +1 brett, olivier, emmanuel, arnaud, vincent I'll move the artifacts over. Cheers, Vincent 2008/8/31 Vincent Siveton <[EMAIL PROTECTED]>: > Hi, > > We solved more than 20 issues: > http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11141&sty

Re: m-eclipse-p: ITs failing

What do you have in the IT build log : D:/ide/maven/maven- eclipse-plugin/target/surefire-reports/build-output/org.apache.maven.plugin.eclipse.it.EclipsePluginIT_testProject01.build.log With a similar config it worked for me some days ago. I have actually a failure on CI server and I'll try to fi

Enforcer plugin release

Hi, What's the status on the Enforcer plugin release these days? Is it possible to get another alpha out if the pending JIRAs have to be fixed for 1.0.0? Seems to me that none of the outstanding issues are bugs which prevents releasing the current work. WDYT? -- - Jan Fredrik Wedén ---

Re: [PLEASE TEST] Maven 2.1.0-M1-RC13

Hi John, I see that on http://ci.sonatype.org/view/Community%20Test%20Projects/ the projects have not been built for 21 days (for XWiki for example). It might be good to run them to validate that 2.1.0-M1-RC13 works on them. WDYT? Thanks -Vincent On Sep 4, 2008, at 2:50 AM, John Casey wr