Re: [VOTE] Release maven-one-plugin 1.2

+1 On 10/09/2007, at 6:26 AM, Dennis Lundberg wrote: Hi, I'd like to release maven-one-plugin 1.2. Release Notes: http://jira.codehaus.org/secure/ReleaseNote.jspa? projectId=11241&styleName=Html&version=13531 Tag: https://svn.apache.org/repos/asf/maven/plugins/tags/maven-one- plugin-1.2/

Re: Standard location for a plugin smoke test

On 9 Sep 07, at 8:24 PM 9 Sep 07, Brett Porter wrote: Sorry, not quite grokking this - are you referring to setting up plugin ITs like the Maven core-its, but on a per-plugin basis? I think basically we want in each project: . `-- src `-- functional-tests |-- java `-- pr

Re: Standard location for a plugin smoke test

On 9 Sep 07, at 8:27 PM 9 Sep 07, Brian E. Fox wrote: Presumably wouldn't this just mean building plugins/ with the latest candidate 2.1? This would also be to check new versions of plugins with older versions of Maven. Knowing for certain and being able to test that the prereq is actuall

RE: [vote] bring shade-maven-plugin to apache

The move is complete and the apache code is now in the maven-sandbox/plugins/maven-shade-plugin. The fate of the shade source at mojo is still pending but the votes so far indicate it will be a full move. (removed from the mojo svn) -Original Message- From: Brian E. Fox [mailto:[EMAIL PRO

RE: code documentation was: For anyone trying to fix configuration bugs in 2.1 (and some notes on how Maven 2.1 works)

I would prefer the javadocs so it's self contained. Anyone looking at this detailed level would really want javadocs and not an APT anyway. The narrative description can go in the class javadoc to describe how/what/why etc. -Original Message- From: Brett Porter [mailto:[EMAIL PROTECTED]

RE: Standard location for a plugin smoke test

Presumably wouldn't this just mean building plugins/ with the latest candidate 2.1? If they don't already have Its, then they wouldn't be avail to port to this new location anyway so I'm not sure it makes a huge difference. -Original Message- From: Jason van Zyl [mailto:[EMAIL PROTECTED]

RE: Classpath ordering of dependencies

And you can use the enforcer noBannedDependency rule to make sure it doesn't come back. Take a look at the dependency plugin pom to see how I used it because the containerApi kept sneaking in. -Original Message- From: Wayne Fay [mailto:[EMAIL PROTECTED] Sent: Sunday, September 09, 2007 9:

Re: Standard location for a plugin smoke test

Sorry, not quite grokking this - are you referring to setting up plugin ITs like the Maven core-its, but on a per-plugin basis? I think basically we want in each project: . `-- src `-- functional-tests |-- java `-- projects |-- test-project1 | |--

Re: Path to 2.1-alpha-1

On 10/09/2007, at 9:21 AM, Jason van Zyl wrote: Hi, For the first set of alpha releases I think we should be focusing on fixing many of the problems and specifically dealing with: 1) Any backward compatibility problems 2) Error reporting and general usability issues 3) Regressions 4) Fail

Re: code documentation was: For anyone trying to fix configuration bugs in 2.1 (and some notes on how Maven 2.1 works)

Cool. This mail has some good content that I'd like to retain in the code documentation. What process should we have for documenting code in Maven core? I kind of like: - as much as possible in the class javadoc that describes just that class (I think the current javadoc for MERP does thi

Standard location for a plugin smoke test

Hi, Just doing some more planning for 2.1 and it would be very advantageous if we could harness many of the ITs created for plugins in a standard way so that we could run a build of Maven against as many plugins as we can get our hands on. I was thinking a standard directory location of a

Re: Classpath ordering of dependencies

It also sounds like perhaps you need an excludes in your dependency declaration, to get rid of that "bad" transitive dep. Wayne > On 7 Sep 07, at 2:20 PM 7 Sep 07, Paul Gier wrote: > > > I did a little more research, and it looks like the artifact was > > renamed, so maven didn't know they were t

Final reminder for 2.1 proposals

Hi, Just another friendly reminder that you have to get your proposals in for 2.1 by Friday in order to be considered for 2.1 Devs: http://docs.codehaus.org/display/MAVEN/All+Proposals Users: http://docs.codehaus.org/display/MAVENUSER/User+Proposals Thanks, Jason -

For anyone trying to fix configuration bugs in 2.1 (and some notes on how Maven 2.1 works)

Hi, I have made a great attempt to push all configuration of anything possible to configure in Maven to this class: http://svn.apache.org/repos/asf/maven/components/trunk/maven-embedder/ src/main/java/org/apache/maven/embedder/execution/ DefaultMavenExecutionRequestPopulator.java For anyo

Path to 2.1-alpha-1

Hi, For the first set of alpha releases I think we should be focusing on fixing many of the problems and specifically dealing with: 1) Any backward compatibility problems 2) Error reporting and general usability issues 3) Regressions 4) Failing ITs (There are 11 commented out and one failing

[VOTE] Release maven-one-plugin 1.2

Hi, I'd like to release maven-one-plugin 1.2. Release Notes: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11241&styleName=Html&version=13531 Tag: https://svn.apache.org/repos/asf/maven/plugins/tags/maven-one-plugin-1.2/ Staged at: http://people.apache.org/~dennisl/staging-reposit