Re: Releasing our parent POMs

I want to see maven-plugin-plugin release before releasing maven-plugins-parent. We did several major changes since the last release (around 1 year) and only one issue is left. Then please schedule MPLUGIN-73 for this release, too. Benjamin Bentmann --

Re: Releasing our parent POMs

Hi Dennis, 2008/2/16, Dennis Lundberg <[EMAIL PROTECTED]>: > Hi all > > I'm going to release maven-parent-8 and when that is done > maven-plugins-11 (also a parent). Is there something more that should be > included before I go ahead with the releases? > > > Changelogs > > maven-parent: > https://

Re: Archiva won't proxy cargo-maven2-plugin?

Seems to be a bug in the metadata handling. I went through this process: - ensured nothing from cargo-maven2-plugin was in the my local repository or archiva repository - try building struts apps - get failure that it can't find RELEASE. - checked metadata returned from Archiva - it contains n

Re: Missing Maven 2.0.8 sources

Brian, Can you put the maven-ant-task-2.0.8-sources in the right location too? Thanks, Paul On Feb 6, 2008 11:42 AM, Brian E. Fox <[EMAIL PROTECTED]> wrote: > Ok it's in the right place now. > > -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > On Behalf Of Paul B

Releasing our parent POMs

Hi all I'm going to release maven-parent-8 and when that is done maven-plugins-11 (also a parent). Is there something more that should be included before I go ahead with the releases? Changelogs maven-parent: https://svn.apache.org/viewvc/maven/pom/trunk/maven/pom.xml?r1=628267&r2=587312&di

Re: [VOTE] Release Maven Surefire version 2.4.2

+1 Fabrice On Feb 16, 2008 12:51 AM, Dan Fabulich <[EMAIL PROTECTED]> wrote: > > As you might expect, all the good bugs were found in 2.4.1 [looks like > some folks were waiting for SP1 to start testing... ;-)] > > We solved 5 issues: > > http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId

RE: Looking for lifecycle execution reusability (building a corporate pom)

Profile defined in a profiles.xml cannot contain any plugins. So i don't see how i could use this to invoke plugins (plugin executions) defined in the corporate pom. Kind Regards, Wouter Hermeling Brian E Fox wrote: > > I was told today that profiles defined in the profiles.xml are inherited >

Re: svn commit: r628218 - in /maven/plugins/trunk/maven-war-plugin/src: it/MWAR-143/ it/MWAR-143/war-common/ it/MWAR-143/war-common/src/main/images/ main/java/org/apache/maven/plugin/war/ main/java/or

2008/2/16, Stephane Nicoll <[EMAIL PROTECTED]>: > Yep. I think lots of users are corrupting their binary files at first. > > Do you also think that we should exclude well known format by default > (png,jpg,jpeg,bmp,etc)? Yep, this will be easier and transparent for users. > > Thanks, > Stéphane >

Re: svn commit: r628218 - in /maven/plugins/trunk/maven-war-plugin/src: it/MWAR-143/ it/MWAR-143/war-common/ it/MWAR-143/war-common/src/main/images/ main/java/org/apache/maven/plugin/war/ main/java/or

Yep. I think lots of users are corrupting their binary files at first. Do you also think that we should exclude well known format by default (png,jpg,jpeg,bmp,etc)? Thanks, Stéphane On Feb 16, 2008 10:28 AM, Olivier Lamy <[EMAIL PROTECTED]> wrote: > Hi, > Here it's a global option at the mojo le

Re: svn commit: r628218 - in /maven/plugins/trunk/maven-war-plugin/src: it/MWAR-143/ it/MWAR-143/war-common/ it/MWAR-143/war-common/src/main/images/ main/java/org/apache/maven/plugin/war/ main/java/or

Hi, Here it's a global option at the mojo level to disable filtering on user defined file extensions. IMHO, it's more easy for a user to not have declare twice a resource (in the war plugin : webResource or an overlay) directory : - one with filtering enabled (with some includes/excludes to exclude