[Result] [vote] [m1] couple of plugins for rc1

We have three binding (Arnaud, Stephane, myself) and 1 non-binding (Jeff) +1s, voting thread is here: http://www.nabble.com/-vote---m1--couple-of-plugins-for-rc1-tf3677026s177.html I'll do the releases ASAP. Thanks, -Lukas Lukas Theussl wrote: Hi, Here's a bunch of plugins I'd like to

Re: [VOTE] Clover 2 preparations for the Clover plugin

+1 (I don't actually think this needs a vote, it should just be standard practice) On 06/05/2007, at 12:57 PM, Vincent Massol wrote: Hi, I'd like to add support for Clover 2 in our Clover plugin. I'm proposing the following: * Fix a few of the outstanding bugs in JIRA and release the

Re: [VOTE] MINSTALL-37 WAS forceVersion for maven-install-plugin?

I thought I already replied, sorry. Anyway, it sounds like this is a hack around the lack of ability to do something else, so I wouldn't be in favour of it. I haven't seen anyone else say they need this. - Brett On 06/05/2007, at 9:54 PM, Brian E. Fox wrote: I know many people where

Re: [VOTE] Clover 2 preparations for the Clover plugin

On May 7, 2007, at 1:31 PM, Brett Porter wrote: +1 (I don't actually think this needs a vote, it should just be standard practice) Yes. I wasn't sure and as I've not been very active lately I thought it more prudent. But fine, I'll go ahead with it then :) Thanks -Vincent On

Re: Publishing plugin docs

(Sorry if this results in a re-send, dodgy connection) I have contributed to a number of threads in the past regarding the fact that maven site's are just another set of meta-data or, if you will, a view upon an artifact and therefore the site for a specific version of an artifact must remain

Re: Publishing plugin docs

Found original JIRA ticket http://jira.codehaus.org/browse/MNG-2679 John jallen wrote: -snip- So here's another appeal from me, please consider an artifact's site part of its state and thus unique in terms of group, artifact and version by default and no longer assume that an

Re: svn commit: r535524 - in /maven/plugins/trunk/maven-javadoc-plugin: ./ src/main/java/org/apache/maven/plugin/javadoc/ src/site/ src/site/apt/ src/site/apt/examples/ src/site/fml/ src/test/java/org

Hi Brett, I tried with maven 2.0.6 and I got NoSuchMethodError for getDirectoryNames(). Any suggestions? Cheers, Vincent 2007/5/6, Vincent Siveton [EMAIL PROTECTED]: Hi Brett, 2007/5/6, Brett Porter [EMAIL PROTECTED]: On 05/05/2007, at 10:09 AM, [EMAIL PROTECTED] wrote: Author:

Re: svn commit: r535524 - in /maven/plugins/trunk/maven-javadoc-plugin: ./ src/main/java/org/apache/maven/plugin/javadoc/ src/site/ src/site/apt/ src/site/apt/examples/ src/site/fml/ src/test/java/org

Set the prereqs to 2.0.6. It won't work with lower. I think what Jason was getting at is: - no matter what you declare, with = 2.0.5 you get 1.1 - in 2.0.6 you get what you ask for, but if you use classes that are incompatible you'll get problems. Since you're using something that was purely

Re: svn commit: r535524 - in /maven/plugins/trunk/maven-javadoc-plugin: ./ src/main/java/org/apache/maven/plugin/javadoc/ src/site/ src/site/apt/ src/site/apt/examples/ src/site/fml/ src/test/java/org

So I will do. Thanks! Vincent 2007/5/7, Brett Porter [EMAIL PROTECTED]: Set the prereqs to 2.0.6. It won't work with lower. I think what Jason was getting at is: - no matter what you declare, with = 2.0.5 you get 1.1 - in 2.0.6 you get what you ask for, but if you use classes that are

Re: [VOTE] MINSTALL-37 WAS forceVersion for maven-install-plugin?

I'm +1 on that one. On 5/7/07, Brett Porter [EMAIL PROTECTED] wrote: I thought I already replied, sorry. Anyway, it sounds like this is a hack around the lack of ability to do something else, so I wouldn't be in favour of it. I haven't seen anyone else say they need this. - Brett On

Re: [VOTE] MINSTALL-37 WAS forceVersion for maven-install-plugin?

Ya, I don't really care... I'd rather see 2.2 get released now and forget about this madness. Well, I still think its useful, but only in a very specific case. --jason On May 7, 2007, at 4:40 AM, Brett Porter wrote: I thought I already replied, sorry. Anyway, it sounds like this is a

Re: avoid that central repo gets garbage dump

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi there, The biggest problem as I see it is not the groupId structures (although it DOES bother me...) but rather the dependencies metadata which is often incorrect, or atleast not quite right. Examples are numerous and range from optional

RE: [VOTE] MINSTALL-37 WAS forceVersion for maven-install-plugin?

Stephan, to be clear, I think your +1 was for close MINSTALL-37 as won't fix and direct to use install:install-file if needed. -Original Message- From: Stephane Nicoll [mailto:[EMAIL PROTECTED] Sent: Monday, May 07, 2007 12:35 PM To: Maven Developers List Subject: Re: [VOTE]

Re: avoid that central repo gets garbage dump

We already do 2, it should be easier, but we already have that with the synced repositories. Central ideally is an aggregation of other repos, if anybody wants to pick up a group, just ask for. On 5/7/07, Joerg Hohwiller [EMAIL PROTECTED] wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1

Re: [VOTE] MINSTALL-37 WAS forceVersion for maven-install-plugin?

Brian, yes my +1 was for that option. Thanks, Stéphane On 5/7/07, Brian E. Fox [EMAIL PROTECTED] wrote: Stephan, to be clear, I think your +1 was for close MINSTALL-37 as won't fix and direct to use install:install-file if needed. -Original Message- From: Stephane Nicoll

removeCompileSourceRoot ?

Hi there, I'm developing a suite of J2ME related plugins for maven2. I'm writing mojos that do the following: Preprocess Compile Preverify Obfuscate Package Run/Debug a MIDlet in an emulator I've implemented a PreProcessorMojo using FreeMarker, and unfortunately i wasn't able to extend the

attaching some behaviour to archetypes

Hi, Last week, i talk with Nicolas de Loof who tells me about an archetype feature he need: modify (read merge) the generated web.xml file from a webapp archetype (when using that archetype in a partial creation (read using an archetype in an existing project to enhance its features). I wonder

Archetype packaging

Hi if i would create a new packaging for archetypes, what is the way (i don't need doco link about lifecycle hook of a mojo, i already know it ;) ) to have a specific metadata uploaded as long with the artifact during the install and deploy phases. My point is how to create metadata and how to