Re: Subclassing the war plugin

Hi, On 4/21/07, Franz Allan Valencia See <[EMAIL PROTECTED]> wrote: ... But if really don't like either approach, then you probably could just create your own version of the war plugin ( something like, org.apache.maven.plugins:maven-war-plugin:1.0-jochen ). So that using pluginManagement, you c

Re: Subclassing the war plugin

Good day to you, Jochen, If you really think maven-war-plugin will not fulfill your war's "special needs", then maybe your packaging is not really a war hence you'd have to go with mywar But if you think it really is a war, then you might want to extend the maven-war-plugin. But if really don

Re: Subclassing the war plugin

Hi, On 4/20/07, Jochen Wiedmann <[EMAIL PROTECTED]> wrote: Hi, I am about to implement a plugin, which generates war files. Wait, I hear you say, there already is a war plugin. Unfortunately, my war files are very special and need to be created in a way, which the war file cannot (and will not)

Re: Publishing plugin docs

On 4/20/07, Wendy Smoak <[EMAIL PROTECTED]> wrote: The only other thing I can come up with is to point to where we want the snapshot docs, and use the staging url for the released docs. Seems backwards, but I want 'mvn site-deploy' to just work during development, so you can't accidentally ove

Re: Publishing plugin docs

What I do is I have a profile with activation on performRelease=true that change the distribution management to something like scp://blablablbla/release/${project.version} So the standard url is used for the dev version and everytime a release is made, the release of version X.Y.Z is stored in t

[vote] release maven-source-plugin 2.0.3

Hi, I'd like to release the maven-source-plugin 2.0.3 The staging bits are available here: http://people.apache.org/~snicoll/maven-staging/repo/org/apache/maven/plugins/maven-source-plugin/2.0.3/ The release notes: ** Bug * [MSOURCES-6] - Sources plugin ignores resource includes/excludes

Re: [maven-source-plugin] Releasing 2.0.3

I have performed the staging release and will cast for the vote right now. Stéphane On 4/20/07, Jochen Wiedmann <[EMAIL PROTECTED]> wrote: Quoting Niall: ping! :-) On 4/13/07, Niall Pemberton <[EMAIL PROTECTED]> wrote: > ping! > > Niall > > On 4/3/07, Jason van Zyl <[EMAIL PROTECTED]> wrote: >

Re: Publishing plugin docs

On 4/20/07, Stephane Nicoll <[EMAIL PROTECTED]> wrote: Sounds good, except that I would put all stuff of a plugin under m.a.o/plugins/${artifactId}. What about the current link with your scenario? A redirect in .htaccess from /plugins/maven-xyz-plugin to maven-xyz-plugin-1.2? That would mean

RE: Publishing plugin docs

I agree, the main url for the plugin should be the same, even if it's just an index page to the available versions. -Original Message- From: Stephane Nicoll [mailto:[EMAIL PROTECTED] Sent: Friday, April 20, 2007 10:21 PM To: Maven Developers List Subject: Re: Publishing plugin docs Sou

Re: [vote] maven-model 3.0.2 for maven 1.1

+1 Stéphane On 4/21/07, Arnaud HERITIER <[EMAIL PROTECTED]> wrote: Hi team, We finalized the new version of maven-model 3.0.2 for maven 1.1. You can find the new web site in [1] and the model documentation [2] will replace the one actually in the maven 1 site [3]. I deployed a Snapshot o

Re: Publishing plugin docs

Sounds good, except that I would put all stuff of a plugin under m.a.o/plugins/${artifactId}. What about the current link with your scenario? Thanks, Stéphane On 4/21/07, Wendy Smoak <[EMAIL PROTECTED]> wrote: A while ago I pushed for publishing the plugin docs from svn, because there was so mu

Publishing plugin docs

A while ago I pushed for publishing the plugin docs from svn, because there was so much good information sitting there, invisible until a release finally happened. Now it's causing problems, mainly with the Assembly plugin which changed quite a bit from 2.1 to 2.2. Also, the changes in the ASF's

Re: [vote] maven-model 3.0.2 for maven 1.1

+1 On 20 Apr 07, at 6:48 PM 20 Apr 07, Arnaud HERITIER wrote: Hi team, We finalized the new version of maven-model 3.0.2 for maven 1.1. You can find the new web site in [1] and the model documentation [2] will replace the one actually in the maven 1 site [3]. I deployed a Snapshot of the

IllegalStateException when mvn exits

Hi folks, I keep seeing an evil IllegalStateException (randomly) when mvn exists. [INFO] [INFO] BUILD SUCCESSFUL [INFO] [INFO] Total time: 21

[vote] maven-model 3.0.2 for maven 1.1

Hi team, We finalized the new version of maven-model 3.0.2 for maven 1.1. You can find the new web site in [1] and the model documentation [2] will replace the one actually in the maven 1 site [3]. I deployed a Snapshot of the library. In this new version, the pom can be read/write with xpp3,

Subclassing the war plugin

Hi, I am about to implement a plugin, which generates war files. Wait, I hear you say, there already is a war plugin. Unfortunately, my war files are very special and need to be created in a way, which the war file cannot (and will not) fulfill. Ok, basically there is no problem. I am subclassin

Re: [maven-source-plugin] Releasing 2.0.3

Quoting Niall: ping! :-) On 4/13/07, Niall Pemberton <[EMAIL PROTECTED]> wrote: ping! Niall On 4/3/07, Jason van Zyl <[EMAIL PROTECTED]> wrote: > > On 3 Apr 07, at 1:39 PM 3 Apr 07, Jochen Wiedmann wrote: > > > Hi, > > > > now that Maria has applied MSOURCES-14, can this release proceed? > > >

Re: Preparing for continuum-1.1-alpha-1

On 4/20/07, Jesse McConnell <[EMAIL PROTECTED]> wrote: What do you guys think? just call a vote on it and get it pushed into the wild or can we just do the alpha's like this through the staging setup? The vote makes it an official release tha can be annouced on the user list. Whether to put i

Re: Preparing for continuum-1.1-alpha-1

might as well just use this thread... I have continuum 1.1 alpha 1 staged now...but I have one concern about calling a vote on this and making it official... Its kinda big (16M war, 25M plexus app) and I still don't really feel comfortable releasing something like continuum as an alpha into the

Re: [VOTE] Release maven-dependency-tree

Result 4 +1 will release 1.0 On 4/14/07, Emmanuel Venisse <[EMAIL PROTECTED]> wrote: +1 Emmanuel Carlos Sanchez a écrit : > anyone? > > On 4/10/07, Carlos Sanchez <[EMAIL PROTECTED]> wrote: >> This release adds iterator methods that simplify the tree navigation >> >> Right now is set to 1.0-

Re: Not able to build maven-release

sorry, that was my bad. I recently released the parent pom and the maven-release-manager...which here both updated to the parent version/version of 2-SNAPSHOT...but I didn't update the plugin's parent version. I am taking care of that now. jesse On 4/19/07, Pankaj Tandon <[EMAIL PROTECTED]> w

Re: [VOTE] Release maven-plugin-testing-harness

Result: 4 +1 will proceed with release of 1.0 On 4/13/07, Vincent Siveton <[EMAIL PROTECTED]> wrote: +1 Vincent 2007/4/13, Brian E. Fox <[EMAIL PROTECTED]>: > +1 > > -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Carlos > Sanchez > Sent: Friday, A

Re: [VOTE] Release maven ant plugin 2.0

Vincent is the most active with the plugin, so i didn't want to apply it if he already didn't I was waiting to hear his opinion in this thread On 4/14/07, Brian E. Fox <[EMAIL PROTECTED]> wrote: MANT-22 has a patch and it seems pretty trivial. Why not apply it? I don't use mant much so maybe I'm

Re: "Corrupted" maven-metadata-central.xml when going offline => online mode ?

On 20 Apr 07, at 11:45 AM 20 Apr 07, Damien Lecan wrote: 2007/4/20, Jason van Zyl <[EMAIL PROTECTED]>: It's in JIRA, same thing happens if there is a connection problem. The metadata will get written out and then not work on subsequent runs. This one ? http://jira.codehaus.org/browse/MNG-2

Re: Continuum & CVS

On 4/20/07, Emmanuel Venisse <[EMAIL PROTECTED]> wrote: Ok, so file an issue on Maven-SCM project (http://jira.codehaus.org/browse/SCM) and we'll fix it. http://jira.codehaus.org/browse/SCM-300

Re: :-)

> another issue is raised because each project in continuum required a client > spec it's a continuum / scm issue > and the number can be too high. perforce licensing is based on user for example evaluation perforce allows 2 users 5 clients so it means that continuum can have only build 5 projec

Re: "Corrupted" maven-metadata-central.xml when going offline => online mode ?

2007/4/20, Jason van Zyl <[EMAIL PROTECTED]>: It's in JIRA, same thing happens if there is a connection problem. The metadata will get written out and then not work on subsequent runs. This one ? http://jira.codehaus.org/browse/MNG-2377 Opened since Maven 2.0-alpha-1 (but only since june 2006)

Re: :-)

>Ok, it seems to be good. Can you send us your patches? no it's not good because i've change also public class PerforceScmProvider public static String getRepoPath( ScmLogger log, PerforceScmProviderRepository repo, File basedir ) if (false)//FIXME pom.exists() ) but it's not a fine solution I

Re: :-)

Ok, it seems to be good. Can you send us your patches? Thanks for your tests. Emmanuel leahpar a écrit : Do you have tested Continuum/Perforce with more than one projects? I think it doesn't work with two and more. yes, several project and several scm Do you have patched Continuum and/or Ma

Re: "Corrupted" maven-metadata-central.xml when going offline => online mode ?

It's in JIRA, same thing happens if there is a connection problem. The metadata will get written out and then not work on subsequent runs. The metadata should no be written to disk unless the artifact safely makes it down. Jason. On 20 Apr 07, at 4:20 AM 20 Apr 07, Damien Lecan wrote: He

Re: nice to have features

On 4/20/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: I hope that I am not asking for more features as you are finalizing 1.1 3) When a build fails contiuum must trigger another build in X minutes (configurable), based on the 2nd build the notification should be send out. This will avoid

Re: continuum and perforce

Index: main/java/org/apache/maven/scm/provider/perforce/command/changelog/PerforceChangeLogCommand.java === --- main/java/org/apache/maven/scm/provider/perforce/command/changelog/PerforceChangeLogCommand.java (revision 529895) +++

Re: :-)

>Do you have tested Continuum/Perforce with more than one projects? I think it doesn't work with two and more. yes, several project and several scm >Do you have patched Continuum and/or Maven-SCM? yes, both slightly but the aim is to make it working (no matter if there's feature lost) not having

Re: nice to have features

[EMAIL PROTECTED] a écrit : I hope that I am not asking for more features as you are finalizing 1.1 1) - Build success/Failure Continuum 1.0.3 has the feature but, I am looking for to give summary of successful ,failure and total builds. Get the trend of continuous integration. This fe

Re: nice to have features

I hope that I am not asking for more features as you are finalizing 1.1 1) - Build success/Failure Continuum 1.0.3 has the feature but, I am looking for to give summary of successful ,failure and total builds. Get the trend of continuous integration. 2) - Unit test successes/Failure (A

Re: Not able to build maven-release

Hi Deng, There are several Failures as you can see in the mvn install Test output on teh console below. I am posting some of the errors which hope are indicative of the problem. After you removed 1-SNAPSHOT from your local repo and replaced the POM with version 1, did you do a mvn clean before mv

Re: nice to have features

Can you add more explanantions? [EMAIL PROTECTED] a écrit : Some more suggestions Separate reporting sections for - Build success/Failure - Unit test successes/Failure (Able to dig in to details) ~nakees

Re: :-)

leahpar a écrit : Ok, it seems to be good. Can you send us your patches? no it's not good because i've change also public class PerforceScmProvider public static String getRepoPath( ScmLogger log, PerforceScmProviderRepository repo, File basedir ) if (false)//FIXME pom.exists() ) but it's

Re: "Corrupted" maven-metadata-central.xml when going offline => online mode ?

We see this a lot of Users@ when people download Maven, attempt to run things without configuring their proxy, end up with a ton of bad metadata, finally configure the proxy, and then still run into problems. So its a big annoying problem from my perspective. Wendy mentioned in a thread on Users@

Re: nice to have features

Some more suggestions Separate reporting sections for - Build success/Failure - Unit test successes/Failure (Able to dig in to details) ~nakees

Re: Controlling plugin versions using dependency management

Thank you Grzegorz Slowikowski Franz Allan Valencia See napisał(a): Good day, Use instead. Something like ... org.apache.maven.plugins maven-jar-plugin 2.0 See [1] for more info. Cheers, Franz [1] http://maven

Re: Controlling plugin versions using dependency management

Thank you. I thought, pluginManagement is for plugin configurations and all other stuff but versions, and dependencyManagement for artifact/plugin versions managing. I was wrong. Grzegorz Slowikowski LAMY Olivier napisał(a): Hi, In your root pom, use build/pluginManagement/plugins with this

RE: Controlling plugin versions using dependency management

Hi, In your root pom, use build/pluginManagement/plugins with this : maven-jar-plugin 2.0 And maybe use user ML for this question. -- Olivier -Message d'origine- De : Grzegorz Słowikowski [mailto:[EMAIL PROTECTED] Envoyé : vendredi 20 avril 2007

Re: Controlling plugin versions using dependency management

Good day, Use instead. Something like ... org.apache.maven.plugins maven-jar-plugin 2.0 See [1] for more info. Cheers, Franz [1] http://maven.apache.org/ref/current/maven-model/maven.html On 4/20/07, Grzegorz Sł

Controlling plugin versions using dependency management

Hi developers I want to control plugin versions used in a multimodule build with dependencyManagement. I thing, Maven behaves weird. Here is a test project, where I try to control maven-jar-plugin version. parent pom: 4.0.0 mycompany parent pom 1.0.0-SNAPSHOT child

"Corrupted" maven-metadata-central.xml when going offline => online mode ?

Hello, Very often, my team developers have problems with local repository that is not update correctly from our remote repository with Maven 2.0.4. Solution was to empty local repository. We haven updated very recently to Maven 2.0.6, so I haven't feedback enough to known if theses problems rema

Re: Release the maven-release-plugin?

Okay. I am taking care of that and I'll cast for a vote tonight. (Unless someone wants to do it earlier) Cheers, Stéphane On 4/20/07, Dan Tran <[EMAIL PROTECTED]> wrote: +1, please cut beta-5 On 4/19/07, Brian E. Fox <[EMAIL PROTECTED]> wrote: > > I agree. Why not release beta-5 now and then