Re: maven-jar-plugin fixes to be reviewed committed

On 4/13/06, Tim Kettler <[EMAIL PROTECTED]> wrote: > I just deleted my local repo and checked out the latest versions of the jar > and webstart > plugins from svn and can't reproduce the second NPE from MJAR-31 anymore. So > this is fixed > somehow already (at least for me). Thanks for the repor

Re: maven-jar-plugin fixes to be reviewed committed

I just deleted my local repo and checked out the latest versions of the jar and webstart plugins from svn and can't reproduce the second NPE from MJAR-31 anymore. So this is fixed somehow already (at least for me). -Tim jerome lacoste schrieb: On 4/13/06, Brett Porter <[EMAIL PROTECTED]> wrot

Re: Debugging Maven with Eclipse?

Have you found this threads in the archives: http://www.mail-archive.com/users@maven.apache.org/msg31345.html http://www.mail-archive.com/users@maven.apache.org/msg27239.html Hope this helps -Tim Jochen Kuhnle schrieb: Hi, is there a guide/howto for this? Or even better, does anybody have a

Re: maven-jar-plugin fixes to be reviewed committed

On 4/13/06, Brett Porter <[EMAIL PROTECTED]> wrote: > jerome lacoste wrote: > > There were 2 potential NPE reported in that issue. One was already > > fixed as a side effect to another bug fix. The other one, I want to be > > able to understand how it can happen (e.g. if the NPE is just caused > >

[jira] Subscription: Outstanding Repository Maintenance: Uploads

Issue Subscription Filter: Outstanding Repository Maintenance: Uploads (9 issues) Subscriber: mavendevlist Key Summary MAVENUPLOAD-834Please update to the latest stable version. http://jira.codehaus.org/browse/MAVENUPLOAD-834 MAVENUPLOAD-827SVG Salamander - tools and utilities

[jira] Subscription: Outstanding Repository Maintenance: Evangelism

Issue Subscription Filter: Outstanding Repository Maintenance: Evangelism (31 issues) Subscriber: mavendevlist Key Summary MEV-374 activeio 3.0 not deployed http://jira.codehaus.org/browse/MEV-374 MEV-373 activemq 4.0-M3 pom invalid http://jira.codehaus.org

Re: maven-jar-plugin fixes to be reviewed committed

jerome lacoste wrote: There were 2 potential NPE reported in that issue. One was already fixed as a side effect to another bug fix. The other one, I want to be able to understand how it can happen (e.g. if the NPE is just caused by a user configuration/usage error, I won't push the proposed patch

Re: maven-jar-plugin fixes to be reviewed committed

On 4/12/06, Carlos Sanchez <[EMAIL PROTECTED]> wrote: > Jerome, the way to go with bugs is first create a test case that > exploits the bug, so test fails, and then fix it. When i don't see a > test case patch I cannot be sure that the patch is really fixing that > problem, and that it won't happen

Re: [vote] Release Maven PMD plugin 2.0

Mike Perham wrote: A few issues: 1) The howto doc still has not been updated to explain the check goals. Heh. It seems I forgot to commit it. I was pretty happy with your explanation and samples - I've just updated it a little. 2) I'd prefer the check goal to be named pmd-check for symmetr

Debugging Maven with Eclipse?

Hi, is there a guide/howto for this? Or even better, does anybody have a working .launch file? Regards, Jochen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

Re: maven-jar-plugin fixes to be reviewed committed

Jerome, the way to go with bugs is first create a test case that exploits the bug, so test fails, and then fix it. When i don't see a test case patch I cannot be sure that the patch is really fixing that problem, and that it won't happen again. If you follow this guidelines I'm pretty sure that an

maven-jar-plugin fixes to be reviewed committed

Hi Fellow Riders of the Lost good code, Would appreciate if someone was to review/commit patches attached to MJAR-32 and MJAR-27 and maybe comment on http://tinyurl.com/fle9y so that I can identify if the last bit in the issue really needs to be fixed (if so please apply the fix pasted in the comm

Re: Sorry for the SPAM on [EMAIL PROTECTED]

Hi guys ! I didn't think I'll launch such a thread :-) I try to reply to everybody. - About the policy to release maven, as I already said it, I'm in favor to use the same one as in tomcat, httpd, ... We release regularly a new version and we vote for the stability : alpha / beta / stable.

Re: Update from 1.0.2 to 1.0.3 SNAPSHOT

The procedure is similar but you must keep 1.0.3 application.xml because we have updated it for database schema update Emmanuel Thomas Recloux a écrit : Hello, I'd like to try the 1.0.3 SNAPSHOT and I used the same update procedure as for update from 1.0.1 to 1.0.2. I got this exception :

Re: svn commit: r393327 - /maven/maven-1/plugins/trunk/project.xml

It was to test continuum I hate to have a release 1.0 which represents nothing In fact I'll remove it. It's not necessary here Arnaud On 4/12/06, Brett Porter <[EMAIL PROTECTED]> wrote: > > [EMAIL PROTECTED] wrote: > > Author: aheritier > > Date: Tue Apr 11 15:50:35 2006 > > New Revision: 393327

Re: svn commit: r393396 - in /maven/maven-1/plugins/trunk/jar: ./ src/main/ src/main/org/ src/main/org/apache/ src/main/org/apache/maven/ src/main/org/apache/maven/jar/ src/plugin-test/test-manifest/

On 4/12/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > Author: ltheussl > Date: Tue Apr 11 23:10:38 2006 > New Revision: 393396 > > URL: http://svn.apache.org/viewcvs?rev=393396&view=rev > Log: > PR: MPJAR-19 > Add tests for jar manifest creation. > > Added: > maven/maven-1/plugins/trunk/