RE: Configuration not selected properly when a plugin is specified multiple times in the pom.

Yep, I think this is related to it only picking the first version it comes across, regardless of future version declarations. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ryan Ovrevik Sent: Wednesday, February 20, 2008 10:25 PM To: dev@maven.apache.org

Test errors in the Install plugin

It looks like some changes in maven-plugin-testing-harness caused errors in the tests in the Install plugin. This is the first build that shows the problem: http://maven.zones.apache.org/continuum/buildResult.action?buildId=39712&projectId=21 Could be that the tests need to be adjusted, I'm not s

Re: Configuration not selected properly when a plugin is specified multiple times in the pom.

On Wed, Feb 20, 2008 at 8:25 PM, Ryan Ovrevik <[EMAIL PROTECTED]> wrote: > Only the first plugin configuration is applied when a plugin is used > multiple times within a profile. Following plug in configurations do > not use their specified configuration. Instead, configuration is based > on wha

Configuration not selected properly when a plugin is specified multiple times in the pom.

Only the first plugin configuration is applied when a plugin is used multiple times within a profile. Following plug in configurations do not use their specified configuration. Instead, configuration is based on what appears to be a combination of the configuration specified in the first plugin con

[Discuss] Review plugin-tools groupId and version

Hi, I noticed that due to [1], the groupId for maven-plugin-testing-harness is no more org.apache.maven.shared. Moreover, we will do a jump from 1.1 to 2.4 [2]. Similar problems occur for maven-plugin-tools-* and only maven-plugin-plugin is not affected by this version pb. I propose to create a n

Re: [VOTE] Release maven-parent pom 8

Hi, 2008/2/20, Dennis Lundberg <[EMAIL PROTECTED]>: > I think that we should be able to copy that entire file to maven-parent. > That way all our projects will share the same look. It was the goal :) > We should probably *not* copy the though, because the main Maven > site doesn't have any .

Re: [VOTE] Release maven-parent pom 8

I think that we should be able to copy that entire file to maven-parent. That way all our projects will share the same look. We should probably *not* copy the though, because the main Maven site doesn't have any . If we do this can we also change the date to use the recommended [2] ISO stan

Re: Enforcer Plugin and Dependency Resolution

This is a good idea, can you add it to the atypical plugin use cases page John put on docs.codehaus.org? Left a comment at http://docs.codehaus.org/display/MAVEN/Atypical+Plugin+Use+Cases that points to this thread. Benjamin -

[ANN] Maven Surefire Plugin 2.4.2 for Maven 2 Released

The Maven team is pleased to announce the release of the Maven Surefire Plugin, version 2.4.2. http://maven.apache.org/plugins/maven-surefire-plugin/ You can run mvn -up to get the latest version of the plugin, or specify the version in your project's plugin configuration: org.apache.mav

Re: propagating to repo1?

got it, please check in 4 hours, should be fixed now On Feb 20, 2008 9:57 AM, Dan Fabulich <[EMAIL PROTECTED]> wrote: > cc: [EMAIL PROTECTED] > > > Dan Fabulich wrote: > > > > > I staged Surefire 2.4.2 last night about 12 hours ago; it still hasn't shown > > up on repo1. > > > > http://repo1.maven

Re: propagating to repo1?

cc: [EMAIL PROTECTED] Dan Fabulich wrote: I staged Surefire 2.4.2 last night about 12 hours ago; it still hasn't shown up on repo1. http://repo1.maven.org/maven2/org/apache/maven/surefire/surefire/ http://people.apache.org/repo/m2-ibiblio-rsync-repository/org/apache/maven/surefire/surefire

propagating to repo1?

I staged Surefire 2.4.2 last night about 12 hours ago; it still hasn't shown up on repo1. http://repo1.maven.org/maven2/org/apache/maven/surefire/surefire/ http://people.apache.org/repo/m2-ibiblio-rsync-repository/org/apache/maven/surefire/surefire/ This seems longer than usual. Is the rsyn

Re: [VOTE] Release Maven Stage Plugin 1.0-alpha-1

Wendy Smoak wrote: On Feb 19, 2008 1:01 PM, Dennis Lundberg <[EMAIL PROTECTED]> wrote: The -sources jar is missing LICENSE and NOTICE files. I dislike changing anything after a vote has started. If it had been the main artifact I would definitely have started over with the release and vote.

RE: Enforcer Plugin and Dependency Resolution

Hi Ben, This is a good idea, can you add it to the atypical plugin use cases page John put on docs.codehaus.org? --Brian -Original Message- From: Benjamin Bentmann [mailto:[EMAIL PROTECTED] Sent: Wednesday, February 20, 2008 7:32 AM To: Maven Developers List Subject: Enforcer Plugin and

Re: [VOTE] Release maven-parent pom 8

Hi, I propose also to create a TLP Maven site, similar to [1]? WDYT? Cheers, Vincent [1] https://svn.apache.org/repos/asf/maven/plugins/trunk/src 2008/2/19, Dennis Lundberg <[EMAIL PROTECTED]>: > Hi > > To get the latest version of maven-source-plugin into our toolchain, I'd > like to release

Enforcer Plugin and Dependency Resolution

Hi, the Enforcer Plugin is usually executed in the "validate" phase and requires resolution of dependencies. This constellation can cause build failures. Consider an Enforcer-enabled multi-project build with a parent and two modules A and B where B has a dependency on A such that the reactor bui