[jira] Commented: (MPWAR-29) in the property "maven.war.classes.includes", Classes are relative to ${maven.build.dir}?

2004-08-12 Thread jira
The following comment has been added to this issue: Author: Zhang Yang Created: Thu, 12 Aug 2004 8:55 PM Body: sorry! maven.war.classes.includes=** ../test-classes/** can not walkaround it. - View this comment:

[ANN] maven-findbugs-plugin 0.8.4 release

2004-08-12 Thread Eric Pugh
The maven-plugins team is pleased to announce the FindBugs Plug-in 0.8.4 release! http://maven-plugins.sourceforge.net A plugin to automate FindBugs tasks Changes in this version include: New Features: o Add example Findbugs report to site docs. Fixed bugs: o Only include jar dependencie

RE: Generate xml report in Clover plugin by default

2004-08-12 Thread Vincent Massol
> -Original Message- > From: Carlos Sanchez [mailto:[EMAIL PROTECTED] > Sent: jeudi 12 août 2004 15:58 > To: 'Maven Developers List' > Subject: Generate xml report in Clover plugin by default > > Hi, > > I wonder if there's any problem changing default maven.clover.report.xml > to > tru

[jira] Created: (MAVEN-1425) Provide access to ant -inputhandler command line option

2004-08-12 Thread jira
Message: A new issue has been created in JIRA. - View the issue: http://jira.codehaus.org/browse/MAVEN-1425 Here is an overview of the issue: - Key:

Generate xml report in Clover plugin by default

2004-08-12 Thread Carlos Sanchez
Hi, I wonder if there's any problem changing default maven.clover.report.xml to true. I wanna change it because dashboard plugin (with report-single) don't get the clover results. If there's no problem I'll set it, else it should be documented in dashboard doc. Regards Carlos Sanchez A Coruña, S

[jira] Commented: (MAVEN-1424) maven -p with a non-existant pom file results in BUILD SUCCESSFUL

2004-08-12 Thread jira
The following comment has been added to this issue: Author: Felipe Leme Created: Thu, 12 Aug 2004 9:59 AM Body: > It's not hard when you have a strategy. Agreed (sorry, didn't know you had such strategy :-) > The CVS Red book is a good source of information on this. Yes, that's

[jira] Commented: (MAVEN-1424) maven -p with a non-existant pom file results in BUILD SUCCESSFUL

2004-08-12 Thread jira
The following comment has been added to this issue: Author: Brett Porter Created: Thu, 12 Aug 2004 9:41 AM Body: Only the branch version will be applied to Maven. We merge the branch to HEAD at regular intervals (for now, at point releases). the command is cvs -j. For instance, a

[jira] Commented: (MAVEN-1424) maven -p with a non-existant pom file results in BUILD SUCCESSFUL

2004-08-12 Thread jira
The following comment has been added to this issue: Author: Felipe Leme Created: Thu, 12 Aug 2004 7:48 AM Body: I don't that's a way to ensure that. What you can do, though, is apply some changes in a branch (1.0, in this case) and then merge them back to the main trunk - I haven'

[jira] Commented: (MAVEN-1424) maven -p with a non-existant pom file results in BUILD SUCCESSFUL

2004-08-12 Thread jira
The following comment has been added to this issue: Author: Michael Mattox Created: Thu, 12 Aug 2004 7:38 AM Body: What I meant is, how are fixes tracked to ensure they are applied to both branches? For example if someone fixes on one branch but not another? We have this problem

[jira] Commented: (MPJAVADOC-38) [PATHC] javadoc artifact is installed/deployed with a weird extension

2004-08-12 Thread jira
The following comment has been added to this issue: Author: Felipe Leme Created: Thu, 12 Aug 2004 7:37 AM Body: Arnauld, I haven't though about the automatic download issue, as I was thinking in the problem from a human being point of view :-). In our case, for instance, we have

[jira] Commented: (MAVEN-1424) maven -p with a non-existant pom file results in BUILD SUCCESSFUL

2004-08-12 Thread jira
The following comment has been added to this issue: Author: Felipe Leme Created: Thu, 12 Aug 2004 7:26 AM Body: When you get do a 'cvs co maven', you get the MAIN branch, which refers to the future 1.1 release. To get the 1.0 branch (which will have a 1.0.1 tag/release at some poi

[jira] Created: (MAVENUPLOAD-188) JPOX 1.0.2 Enhancer Upload

2004-08-12 Thread jira
Message: A new issue has been created in JIRA. - View the issue: http://jira.codehaus.org/browse/MAVENUPLOAD-188 Here is an overview of the issue: -

[jira] Created: (MAVENUPLOAD-187) JPOX 1.0.2 Upload

2004-08-12 Thread jira
Message: A new issue has been created in JIRA. - View the issue: http://jira.codehaus.org/browse/MAVENUPLOAD-187 Here is an overview of the issue: -

Re: md5 checksum formats on BSD

2004-08-12 Thread Stefan Bodewig
On Wed, 11 Aug 2004, Mark R. Diggory <[EMAIL PROTECTED]> wrote: > In the larger community the BSD default format is refered to as SVF > (Simple File Verification) and the GNU md5sum format as MD5SUM, I > suspect it would be good to see these as output features/options > that could be set within An

[jira] Created: (MPDIST-14) making it possible to add config or libs to the dirst

2004-08-12 Thread jira
Message: A new issue has been created in JIRA. - View the issue: http://jira.codehaus.org/browse/MPDIST-14 Here is an overview of the issue: - Key:

[jira] Commented: (MPDIST-14) making it possible to add config or libs to the dirst

2004-08-12 Thread jira
The following comment has been added to this issue: Author: Kees Jongenburger Created: Thu, 12 Aug 2004 3:52 AM Body: or a leat make it configurable to add some directories - View this comment: http://jira.codeha

[jira] Commented: (MAVEN-1424) maven -p with a non-existant pom file results in BUILD SUCCESSFUL

2004-08-12 Thread jira
The following comment has been added to this issue: Author: Michael Mattox Created: Thu, 12 Aug 2004 3:05 AM Body: Thanks for the patch, that was really fast!! On a side note, I'm curious how the fixes are tracked to ensure they are applied to both branches. ---