Re: wagon write locking / synchronization in 2.1 or 2.2?

Christian, I am glad to see this question as I have the answer :) Fine people from Jetty community helped us with the Mercury project (http://docs.codehaus.org/display/MAVEN/Mercury) and provided Jetty client with transactional support. The client accepts a set of files to upload or download

Re: [vote] release maven enforcer plugin 1.0-alpha-4

+1 --jason On Sep 9, 2008, at 7:38 AM, Brian E. Fox wrote: Time to release the enforcer with all its new rules. The plugin is staged here: http://people.apache.org/~brianf/stage/ The site is staged here: http://people.apache.org/~brianf/plugins/maven-enforcer-plugin/ http://people.ap

Re: wagon write locking / synchronization in 2.1 or 2.2?

On 09/09/2008, at 5:48 AM, Christian Edward Gruber wrote: Hi all, Looking at the release plans for 2.1 and 2.2 I don't see anything about addressing the big fat hairy race condition that prevents multiple maven builds on the same local repository from risking corruption of the local

wagon write locking / synchronization in 2.1 or 2.2?

Hi all, Looking at the release plans for 2.1 and 2.2 I don't see anything about addressing the big fat hairy race condition that prevents multiple maven builds on the same local repository from risking corruption of the local repo. There have been a few proposals and several JIRAs,

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

I had an interesting issue with the ant plugin in building the open-jbi-components project. Looks to me like ${project.build.directory} is now resolved as a relative path instead of an absolute path at plugin

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

John, Should MNG-3746 be revisited to not allow java.* properties to be overridden? I am concerned that while this is previous behavior, perhaps it is really allowing people to shoot themselves in the foot. I consider that Maven should error on such property names -- or at least be configured to h

[PLEASE TEST] Maven 2.1.0-M1-RC16

Hi again, I've fixed two more issues that came up in RC13 and the intervening release candidates: - http://jira.codehaus.org/browse/MNG-3746 - http://jira.codehaus.org/browse/MNG-3747 Here's the URL for the RC16 release candidate: http://people.apache.org/~jdcasey/stage/current-maven-RC/ Pl

[vote] release maven enforcer plugin 1.0-alpha-4

Time to release the enforcer with all its new rules. The plugin is staged here: http://people.apache.org/~brianf/stage/ The site is staged here: http://people.apache.org/~brianf/plugins/maven-enforcer-plugin/ http://people.apache.org/~brianf/enforcer/ Release Notes http://jira.codeh

Re: m-eclipse-p: ITs failing

The invocation will use ~/.m2/settings.xml so I can put those settings in there. I'm now left with the TestServlet error below, which only occurs if I run: mvn clean mvn -Prun-its install and then again mvn -Prun-its install the second time I get this error. Does anyone else get this proble

RE: [vote] release maven-parent 9 TAKE 2

>Sorry, I missed that last bit. >Staging two releases simultaneously to the same staging repo will make >it difficult for you to move *only one* artifact to the central >repository using the Stage Plugin. I recommend using two different repo >directories for that, because the Stage Plugin copies

RE: [vote] release maven-parent 9 TAKE 2

>Not sure I follow you here: what about the site? The site.xml has changed which is inherited. I didn't see any reason not to release it given the changes and the length of time so I didn't waste time analyzing it. I know 9-SNAPSHOT works and it seemed less effort and more forward progress to rel

Re: [vote] release maven-parent 9 TAKE 2

Brian E. Fox wrote: > Take 2: I removed the enforcer version and the clirr checks. (see other > vote thread for reasons) > > > > I need to release the maven-parent v9 before I can do the enforcer > release. Since there isn't a project to track changes in jira, here are > the diffs since v8. It'

RE: [vote] release maven-parent 9

>No, it's available in the quality-checks profile as well. I saw that but it didn't work. It tried to find alpha-3-snapshot because it was running against alpha-4-snapshot. >It is supposed to do this: > "compares the current code against the latest released version" >This is also what it does,

RE: svn commit: r693209 - /maven/enforcer/trunk/pom.xml

It's dependent, if the parent fails, I'll rollback the whole thing. I don't think we need to be inefficient and wait 3 days for a parent pom and then 3 more days for the enforcer. -Original Message- From: Dennis Lundberg [mailto:[EMAIL PROTECTED] Sent: Monday, September 08, 2008 5:14 PM

Re: [vote] release maven-parent 9 TAKE 2

And with versions-maven-plugin:update-parent making it easy to ensure you have the latest parent, releasing the parent a lot shold be less of a pain ;-) -Stephen On Mon, Sep 8, 2008 at 10:19 PM, Dennis Lundberg <[EMAIL PROTECTED]> wrote: > Not sure I follow you here: what about the site? > > We

Re: [vote] release maven-parent 9 TAKE 2

Not sure I follow you here: what about the site? Well, as I said we have been holding off on the parent release (for too long) specifically to get the new enforcer in there. So releasing the parent without it now feels like an anticlimax. That said, I agree that we need to release our parents mor

Re: svn commit: r693209 - /maven/enforcer/trunk/pom.xml

Brian, I have a couple of objections to this commit. 1. Depending on a parent that is not yet available on central will cause mayhem for CI servers. Trust me I did that once before, and it was not a pretty sight. 2. Since the vote is still open on the parent you can't tag and stage a release of t

Re: [vote] release maven-parent 9 TAKE 2

Sorry for this but -1 again since we missed some releases: apache-jar-resource-bundle:1.4 maven-plugin-plugin:2.4.3 maven-scm-plugin:1.1 plexus-maven-plugin:1.3.8 I already fixed in [1] Cheers, Vincent [1] http://svn.apache.org/viewvc?rev=693273&view=rev 2008/9/8 Brian E. Fox <[EMAIL PROTECTED

Re: [vote] release maven-parent 9 TAKE 2

I don't but I don't know how not including it might affect the site specifically. The parent isn't a magical thing and it's been 6 months. Why not release it, do the enforcer and release it again? Release it 3 or 4 more times for good measure. Sent from my iPhone On Sep 8, 2008, at 4:47 P

Re: [vote] release maven-parent 9

Brian E. Fox wrote: > -1 also because Clirr is a PITA. First of all, it is only setup to run > when you do a release so you don't notice a problem until you are in the > throws of releasing. No, it's available in the quality-checks profile as well. > Second, Clirr can't run against a snapshot bec

Re: Poms that Incorrectly Specify Encoding

Le lundi 08 septembre 2008, Shane Isbell a écrit : > I'm working on refactoring the project builder code, and I've come across > an xml parser error, resulting from a pom claiming it's UTF-8 encoded while > it's not. This causes the woodstox parser to fail. How is this currently > handled in Maven?

Re: Requesting advice on how to extend the maven repository format

Will these listeners be provided with the necessary references (Stream, etc.) to support artifact transformation? In other words, is this a super-set of the filtering functionality I described? On Fri, Sep 5, 2008 at 5:15 PM, Oleg Gusakov <[EMAIL PROTECTED]>wrote: > > > Shane Isbell wrote: > >>

Re: [vote] release maven-parent 9 TAKE 2

Brian, why do you need to release maven-parent-9 to be able to do the enforcer release? We have been holding off the release of the parent so that we could get the new enforcer into the parent... Brian E. Fox wrote: > Take 2: I removed the enforcer version and the clirr checks. (see other > vote

[vote] release maven-parent 9 TAKE 2

Take 2: I removed the enforcer version and the clirr checks. (see other vote thread for reasons) I need to release the maven-parent v9 before I can do the enforcer release. Since there isn't a project to track changes in jira, here are the diffs since v8. It's mostly housekeeping and plugin loc

RE: [vote] release maven-parent 9

-1 also because Clirr is a PITA. First of all, it is only setup to run when you do a release so you don't notice a problem until you are in the throws of releasing. Second, Clirr can't run against a snapshot because it tries to find the previous version snapshot (not the last release version) and w

Reporting architecture question

Creating aggregate reports in maven has historically been a little awkward. To this end i remember chatter about revamping the reporting framework to support registering listeners to reports. Has any of this changed?

Re: [vote] release maven-parent 9

2008/9/8 Brian E. Fox <[EMAIL PROTECTED]> > > I need to release the maven-parent v9 before I can do the enforcer > release. Since there isn't a project to track changes in jira, here are > the diffs since v8. It's mostly housekeeping and plugin lockdown: > > > > http://svn.apache.org/viewvc/maven/p

Re: [vote] release maven-parent 9

+1 Arnaud On Mon, Sep 8, 2008 at 9:19 PM, Brian E. Fox <[EMAIL PROTECTED]>wrote: > I need to release the maven-parent v9 before I can do the enforcer > release. Since there isn't a project to track changes in jira, here are > the diffs since v8. It's mostly housekeeping and plugin lockdown: > >

[vote] release maven-parent 9

I need to release the maven-parent v9 before I can do the enforcer release. Since there isn't a project to track changes in jira, here are the diffs since v8. It's mostly housekeeping and plugin lockdown: http://svn.apache.org/viewvc/maven/pom/trunk/maven/pom.xml?r1=632423&r2= 693201&diff_forma

Re: [PROPOSAL] Release plan for the Site Plugin

Lukas Theussl wrote: > Sounds good to me. I haven't quite followed the discussion on release > plans recently but it's still itching me to get doxia released. Great > Just a few comments: > > - I proposed on the doxia-dev list to release the alpha branch as 1.0 > final but haven't gotten any fee

[PLEASE TEST] Maven 2.1.0-M1-RC15

Hi everyone, I've fixed a bug in RC13 (yes, it took two tries, thus the RC15 version of this post). You can find the new release candidate here: http://people.apache.org/~jdcasey/stage/current-maven-RC As a matter of fact, I'll just start updating this URL with the latest RC when I roll a ne

Poms that Incorrectly Specify Encoding

I'm working on refactoring the project builder code, and I've come across an xml parser error, resulting from a pom claiming it's UTF-8 encoded while it's not. This causes the woodstox parser to fail. How is this currently handled in Maven? Should we fail the build if a dependency incorrectly state

Re: Wagon problems, maybe somebody has answers?

James, Brett, Thanks for answering these question. I have copied some code from a streaming wagon and that addressed the put tests, but get is still failing, I am debugging that. Thanks, Oleg - To unsubscribe, e-mail:

RE: m-eclipse-p: ITs failing

The IT harness is launching a new maven invocation to run the plugin. It doesn't pay attention to your settings, so it will only work if you can get to the repos without a proxy iirc. -Original Message- From: Barrie Treloar [mailto:[EMAIL PROTECTED] Sent: Monday, September 08, 2008 12:25

Re: [PROPOSAL] Release plan for the Site Plugin

Sounds good to me. I haven't quite followed the discussion on release plans recently but it's still itching me to get doxia released. Just a few comments: - I proposed on the doxia-dev list to release the alpha branch as 1.0 final but haven't gotten any feedback. I think it's a good idea, dox

Re: Wagon problems, maybe somebody has answers?

On 05/09/2008, at 7:00 AM, Oleg Gusakov wrote: I tried to create mercury-based wagon provider and got overwhelmed with Wagon's strange architecture decisions and APIs. Yeah, as James said, it kind of grew with Maven (refactoring of Maven 1.x artifact code and an aborted pre-m2 attempt I be

Re: Maven 2.1.0 GA Plan

Please see http://docs.codehaus.org/display/MAVEN/Automatic+Parent+Versioning. I've also linked it from the Release Plan document. Ralph John Casey wrote: I've read MNG-624, and quite a bit of the code, and I feel like I understand the algorithm relatively well. What I'm having trouble under