RE: mojo inheritance

Jason van Zyl wrote on Wednesday, September 26, 2007 7:59 AM: > On 25 Sep 07, at 10:21 PM 25 Sep 07, Brian E. Fox wrote: > >> This is interesting functionality that the dev team should be aware >> of. I know it's frequently asked how to extend a plugin. >> > > We could definitely integrate this

Re: mojo inheritance

On 25 Sep 07, at 10:21 PM 25 Sep 07, Brian E. Fox wrote: This is interesting functionality that the dev team should be aware of. I know it's frequently asked how to extend a plugin. We could definitely integrate this method, would be highly useful. When we integrate the anno-mojo stuff we

RE: mojo inheritance

This is interesting functionality that the dev team should be aware of. I know it's frequently asked how to extend a plugin. --Brian -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Stuart McCulloch Sent: Tuesday, September 25, 2007 11:21 AM To: Maven User

Re: Time to release the site plugin

yes and no the problem is that it works with the previous beta and I can't say if users won't have this problem on another CI server ? Arnaud On 25/09/2007, Dennis Lundberg <[EMAIL PROTECTED]> wrote: > > Like I said in that issue: I cannot reproduce your problem. I do think > it is related to Hud

RE: Maven-war-plugin not installing war. Installs ".jar" and renames it to ".war"

As you requested, I have created an issue in MWAR and attached the necessary files. Dave. -Original Message- From: Stephane Nicoll [mailto:[EMAIL PROTECTED] Sent: September 25, 2007 03:57 AM To: Maven Developers List Subject: Re: Maven-war-plugin not installing war. Installs ".jar" an

Re: Time to release the site plugin

Like I said in that issue: I cannot reproduce your problem. I do think it is related to Hudson somehow. Arnaud HERITIER wrote: I just tested it I have always this bug http://jira.codehaus.org/browse/MSITE-256 For me the site plugin is unusable Arnaud On 25/09/2007, Dennis Lundberg <[EMAIL PR

RE: svn commit: r579029 - in /maven/plugins/trunk/maven-dependency-plugin: pom.xml src/site/apt/index.apt src/site/apt/usage.apt

I guess I was having a bad night. I'll fix it. -Original Message- From: Dennis Lundberg [mailto:[EMAIL PROTECTED] Sent: Tuesday, September 25, 2007 1:40 PM To: dev@maven.apache.org Subject: Re: svn commit: r579029 - in /maven/plugins/trunk/maven-dependency-plugin: pom.xml src/site/apt/i

Re: Time to release the site plugin

I just tested it I have always this bug http://jira.codehaus.org/browse/MSITE-256 For me the site plugin is unusable Arnaud On 25/09/2007, Dennis Lundberg <[EMAIL PROTECTED]> wrote: > > I've seen that on a couple of occasions. It only happens for that > particular jar and seems to have something

Re: svn commit: r579029 - in /maven/plugins/trunk/maven-dependency-plugin: pom.xml src/site/apt/index.apt src/site/apt/usage.apt

Was there a special reason for reinserting the tab characters into the pom, that I previously (r576579) removed? Also, I'm sure you didn't mean to check in your svn conflicts into maven/plugins/trunk/maven-dependency-plugin/src/site/apt/usage.apt ;-) [EMAIL PROTECTED] wrote: Author: brianf D

Re: Time to release the site plugin

I've seen that on a couple of occasions. It only happens for that particular jar and seems to have something to do with bcel. I looked briefly, but couldn't find any reference to either one in the site-plugin code base. Dan Tran wrote: looking good. however I see some annoying warnings like

Re: More DefaultArtifactCollector queries

On 24/07/2007, Brett Porter <[EMAIL PROTECTED]> wrote: > IIRC, it switched to the other dependency because the alternate scope > is going to modify the subtree under that dependency. Does that make > sense? Blast from the past.. sorry Brett, I don't see what your saying here. There's no subtree

Re: Documentation Plan

The layout below with stated modifications sounds good to me. See also on archiva-dev today: [EMAIL PROTECTED]> under "[proposal] Move Archiva's wiki to cwiki.apache.org" for the different types I'd like to see. I think the documentation can be deployed to /docs/1.1, /docs/1.0.3, etc. Che

Re: [proposal] Move Archiva's wiki to cwiki.apache.org

My thought is this: - documentation should be complete enough for the version that gets released. It should be versioned according to that release, and distributed either with it, or as a separate zip file alongside it. This is very difficult to get from the wiki, so I suggest we continue

maven shared components targeting 1.5 ?

Hi, the following maven snapshots appear to have been compiled with a target of 1.5: org.apache.maven.shared maven-dependency-tree 1.1-SNAPSHOT org.apache.maven.shared maven-osgi 0.2.0-SNAPSHOT [INFO] Compilation failure /home/stuart/Code/

Re: Maven-war-plugin not installing war. Installs ".jar" and renames it to ".war"

Create an issue in the MWAR project with a sample project to reproduce and I'll have a look to it. Sorry I forgot the attachment restriction on this list. Thanks, Stéphane On 9/24/07, Dave Rathnow <[EMAIL PROTECTED]> wrote: > > Stephane, > > The file is too large for the list server and is being

Re: [VOTE] Release maven-gpg-plugin 1.0-alpha-4

+1 Arnaud On 25/09/2007, Brian E. Fox <[EMAIL PROTECTED]> wrote: > > +1 > > -Original Message- > From: Daniel Kulp [mailto:[EMAIL PROTECTED] > Sent: Monday, September 24, 2007 4:55 PM > To: Maven Developers List > Subject: [VOTE] Release maven-gpg-plugin 1.0-alpha-4 > > > All but one bug