[jira] Reopened: (MCLOVER-11) Add support for passing flush policy/flush interval to Clover

[ http://jira.codehaus.org/browse/MCLOVER-11?page=all ] Vincent Massol reopened MCLOVER-11: --- Reopen to set again versions after the jira move from "Maven 2" to "Maven 2.x Clover Plugin" > Add support for passing flush policy/flush interval to Clover

[jira] Closed: (MCLOVER-9) Locale problem in Clover plugin

[ http://jira.codehaus.org/browse/MCLOVER-9?page=all ] Vincent Massol closed MCLOVER-9: Assign To: Vincent Massol (was: Vincent Siveton) Resolution: Won't Fix This was not a clover plugin issue. It was a Maven 2.0 report issue fixed by Vincen

[jira] Updated: (MCLOVER-13) Check artifact language

[ http://jira.codehaus.org/browse/MCLOVER-13?page=all ] Vincent Massol updated MCLOVER-13: -- Version: 2.0-alpha-1 Fix Version: 2.0 type: Improvement (was: Bug) > Check artifact language > --- > > Key: MCLO

[jira] Reopened: (MCLOVER-9) Locale problem in Clover plugin

[ http://jira.codehaus.org/browse/MCLOVER-9?page=all ] Vincent Massol reopened MCLOVER-9: -- Reopen to set again versions after the jira move from "Maven 2" to "Maven 2.x Clover Plugin" > Locale problem in Clover plugin > --

[jira] Closed: (MCLOVER-8) Clover default target percentage too high - should be 0%

[ http://jira.codehaus.org/browse/MCLOVER-8?page=all ] Vincent Massol closed MCLOVER-8: Resolution: Won't Fix Fixed again versions after the jira move from "Maven 2" to "Maven 2.x Clover Plugin" > Clover default target percentage too high - should

[jira] Updated: (MCLOVER-8) Clover default target percentage too high - should be 0%

[ http://jira.codehaus.org/browse/MCLOVER-8?page=all ] Vincent Massol updated MCLOVER-8: - Version: 2.0-alpha-1 Fix Version: 2.0 set again versions after the jira move from "Maven 2" to "Maven 2.x Clover Plugin" > Clover default target percentag

[jira] Reopened: (MCLOVER-8) Clover default target percentage too high - should be 0%

[ http://jira.codehaus.org/browse/MCLOVER-8?page=all ] Vincent Massol reopened MCLOVER-8: -- Reopen to set again versions after the jira move from "Maven 2" to "Maven 2.x Clover Plugin" > Clover default target percentage too high - should be 0% > -

[jira] Updated: (MCLOVER-12) clover should generate a placeholder if project do not have test cases

[ http://jira.codehaus.org/browse/MCLOVER-12?page=all ] Vincent Massol updated MCLOVER-12: -- Version: 2.0-alpha-1 Fix Version: 2.0 set again versions after the jira move from "Maven 2" to "Maven 2.x Clover Plugin" > clover should generate a pla

[jira] Updated: (MCLOVER-5) Clover fails on multi-module builds

[ http://jira.codehaus.org/browse/MCLOVER-5?page=all ] Vincent Massol updated MCLOVER-5: - Version: 2.0-alpha-1 Fix Version: 2.0 set again versions after the jira move from "Maven 2" to "Maven 2.x Clover Plugin" > Clover fails on multi-module bu

[jira] Updated: (MCLOVER-7) "mvn clover:report" generates errors in tests that execute properly in "mvn test"

[ http://jira.codehaus.org/browse/MCLOVER-7?page=all ] Vincent Massol updated MCLOVER-7: - Version: 2.0-alpha-1 Fix Version: 2.0 set again versions after the jira move from "Maven 2" to "Maven 2.x Clover Plugin" > "mvn clover:report" generates e

[jira] Closed: (MCLOVER-2) clover breaks when encountering assert statements.

[ http://jira.codehaus.org/browse/MCLOVER-2?page=all ] Vincent Massol closed MCLOVER-2: Resolution: Fixed Fixed again versions after the jira move from "Maven 2" to "Maven 2.x Clover Plugin" > clover breaks when encountering assert statements. > -

[jira] Reopened: (MCLOVER-2) clover breaks when encountering assert statements.

[ http://jira.codehaus.org/browse/MCLOVER-2?page=all ] Vincent Massol reopened MCLOVER-2: -- Reopen to set again versions after the jira move from "Maven 2" to "Maven 2.x Clover Plugin" > clover breaks when encountering assert statements. > ---

[jira] Updated: (MCLOVER-2) clover breaks when encountering assert statements.

[ http://jira.codehaus.org/browse/MCLOVER-2?page=all ] Vincent Massol updated MCLOVER-2: - Version: 2.0-alpha-1 Fix Version: 2.0 set again versions after the jira move from "Maven 2" to "Maven 2.x Clover Plugin" > clover breaks when encountering

[jira] Commented: (MNGECLIPSE-15) Output folders are not set correctly by 'Update Sources' action

[ http://jira.codehaus.org/browse/MNGECLIPSE-15?page=comments#action_53828 ] Eugene Kuleshov commented on MNGECLIPSE-15: --- Actually it is trickier then it seems. You can't really use the same output folders between Eclipse compiler and any external

RE: Problems with JIRA Plug-in Projects

> -Original Message- > From: Jason van Zyl [mailto:[EMAIL PROTECTED] > Sent: mardi 20 décembre 2005 16:37 > To: Maven Developers List > Subject: Problems with JIRA Plug-in Projects > > Hi, > > There are a few issues with the movement of the issues. So I'll list > them and then we need t

[jira] Closed: (MCLOVER-6) change outputDirectory in reports to default to ${project.reporting.outputDirectory}

[ http://jira.codehaus.org/browse/MCLOVER-6?page=all ] Vincent Massol closed MCLOVER-6: Resolution: Fixed Fixed again versions after the jira move from "Maven 2" to "Maven 2.x Clover Plugin" > change outputDirectory in reports to default to > ${p

[jira] Updated: (MCLOVER-6) change outputDirectory in reports to default to ${project.reporting.outputDirectory}

[ http://jira.codehaus.org/browse/MCLOVER-6?page=all ] Vincent Massol updated MCLOVER-6: - Version: 2.0-alpha-1 Fix Version: 2.0 type: Improvement (was: Bug) set again versions after the jira move from "Maven 2" to "Maven 2.x Clover P

[jira] Reopened: (MCLOVER-6) change outputDirectory in reports to default to ${project.reporting.outputDirectory}

[ http://jira.codehaus.org/browse/MCLOVER-6?page=all ] Vincent Massol reopened MCLOVER-6: -- Reopen to set again versions after the jira move from "Maven 2" to "Maven 2.x Clover Plugin" > change outputDirectory in reports to default to > ${project.rep

[jira] Created: (MNGECLIPSE-15) Output folders are not set correctly by 'Update Sources' action

Output folders are not set correctly by 'Update Sources' action --- Key: MNGECLIPSE-15 URL: http://jira.codehaus.org/browse/MNGECLIPSE-15 Project: Maven 2.x Plug-in for Eclipse Type: Bug Reporter: YOKOT

[jira] Closed: (MCLOVER-1) clover has to be declared as project dependency to run clover:report

[ http://jira.codehaus.org/browse/MCLOVER-1?page=all ] Vincent Massol closed MCLOVER-1: Resolution: Fixed Fixed again versions after the jira move from "Maven 2" to "Maven 2.x Clover Plugin" > clover has to be declared as project dependency to run

[jira] Reopened: (MCLOVER-1) clover has to be declared as project dependency to run clover:report

[ http://jira.codehaus.org/browse/MCLOVER-1?page=all ] Vincent Massol reopened MCLOVER-1: -- Reopen to set again versions after the jira move from "Maven 2" to "Maven 2.x Clover Plugin" > clover has to be declared as project dependency to run clover:re

[jira] Updated: (MCLOVER-1) clover has to be declared as project dependency to run clover:report

[ http://jira.codehaus.org/browse/MCLOVER-1?page=all ] Vincent Massol updated MCLOVER-1: - Version: 2.0-alpha-1 Fix Version: 2.0 set again versions after the jira move from "Maven 2" to "Maven 2.x Clover Plugin" > clover has to be declared as pr

[jira] Closed: (MCLOVER-4) clover:check fails, even though coverage is 100%

[ http://jira.codehaus.org/browse/MCLOVER-4?page=all ] Vincent Massol closed MCLOVER-4: Resolution: Fixed Fixed again versions after the jira move from "Maven 2" to "Maven 2.x Clover Plugin" > clover:check fails, even though coverage is 100% > ---

[jira] Reopened: (MCLOVER-4) clover:check fails, even though coverage is 100%

[ http://jira.codehaus.org/browse/MCLOVER-4?page=all ] Vincent Massol reopened MCLOVER-4: -- Reopening to set again versions after the jira move from "Maven 2" to "Maven 2.x Clover Plugin" > clover:check fails, even though coverage is 100% > --

[jira] Updated: (MCLOVER-4) clover:check fails, even though coverage is 100%

[ http://jira.codehaus.org/browse/MCLOVER-4?page=all ] Vincent Massol updated MCLOVER-4: - Version: 2.0-alpha-1 Fix Version: 2.0 set again versions after the jira move from "Maven 2" to "Maven 2.x Clover Plugin" > clover:check fails, even though

[jira] Updated: (MCLOVER-3) classpath error

[ http://jira.codehaus.org/browse/MCLOVER-3?page=all ] Vincent Massol updated MCLOVER-3: - Version: 2.0-alpha-1 Fix Version: 2.0 set again versions after the jira move from "Maven 2" to "Maven 2.x Clover Plugin" > classpath error > -

Problems with JIRA Plug-in Projects

Hi, There are a few issues with the movement of the issues. So I'll list them and then we need to decide what to do: 1) I selected the retain option which I assumed would create the versions in new projects, but the affects/fix version information appears to have been lost. 2) I thought I

[jira] Commented: (MAVEN-1345) Upgrade to dom4j 1.4

[ http://jira.codehaus.org/browse/MAVEN-1345?page=comments#action_53816 ] Elliotte Rusty Harold commented on MAVEN-1345: -- Please do not use dom4j 1.4 or earlier. It has some license issues that weren't corrected until about 1.6. I have to check

[jira] Closed: (MEV-267) org.springframework is missing *.pom files in ibiblio

[ http://jira.codehaus.org/browse/MEV-267?page=all ] Carlos Sanchez closed MEV-267: -- Assign To: Carlos Sanchez Resolution: Fixed Uploaded to org.springframework > org.springframework is missing *.pom files in ibiblio > ---

[jira] Assigned: (SCM-113) Support persistent and transient clientspecs

[ http://jira.codehaus.org/browse/SCM-113?page=all ] mike perham reassigned SCM-113: --- Assign To: mike perham > Support persistent and transient clientspecs > > > Key: SCM-113 > URL: http://jira

[jira] Assigned: (SCM-114) Clientspec naming

[ http://jira.codehaus.org/browse/SCM-114?page=all ] mike perham reassigned SCM-114: --- Assign To: mike perham > Clientspec naming > - > > Key: SCM-114 > URL: http://jira.codehaus.org/browse/SCM-114 > Project: Maven SCM

[jira] Assigned: (SCM-119) Perforce provider should only append "/..." to view if necessary

[ http://jira.codehaus.org/browse/SCM-119?page=all ] mike perham reassigned SCM-119: --- Assign To: mike perham > Perforce provider should only append "/..." to view if necessary > > >

[jira] Commented: (MDEPLOY-13) Error while deploying when using scpexe protocol with non-default scp/ssh executables

[ http://jira.codehaus.org/browse/MDEPLOY-13?page=comments#action_53814 ] mike perham commented on MDEPLOY-13: Brett, can you give more specifics about the code that needs to be fixed? We are seeing this problem also when trying to use scpexe and I woul

[jira] Moved: (MRAR-1) maven-rar-plugin can not install the generated rar file to the local repository

[ http://jira.codehaus.org/browse/MRAR-1?page=all ] Jason van Zyl moved MNG-1681 to MRAR-1: --- Fix Version: (was: 2.0.1) Component: (was: maven-rar-plugin) Workflow: jira (was: Maven) Key: MRAR-1 (was: MNG-1681)

[jira] Moved: (MRESOURCES-7) resources and test resources not copied incrementally to target when filtering is off

[ http://jira.codehaus.org/browse/MRESOURCES-7?page=all ] Vincent Massol moved MNG-1042 to MRESOURCES-7: -- Fix Version: (was: 2.0 (RC)) Component: (was: maven-resources-plugin) Workflow: jira (was: Maven) Key:

[jira] Moved: (MRESOURCES-6) When filtering, properties defined in should be allowed as well.

[ http://jira.codehaus.org/browse/MRESOURCES-6?page=all ] Vincent Massol moved MNG-1194 to MRESOURCES-6: -- Fix Version: (was: 2.0.1) Component: (was: maven-resources-plugin) Workflow: jira (was: Maven) Key: MR

[jira] Moved: (MRESOURCES-3) When filtering, ${java.version} gets replaced with pom.version instead.

[ http://jira.codehaus.org/browse/MRESOURCES-3?page=all ] Vincent Massol moved MNG-1193 to MRESOURCES-3: -- Fix Version: (was: 2.0.1) Component: (was: Inheritence and Interpolation) (was: maven-resources-plugi

[jira] Moved: (MRESOURCES-5) Proposal for improved resource filtering

[ http://jira.codehaus.org/browse/MRESOURCES-5?page=all ] Vincent Massol moved MNG-788 to MRESOURCES-5: - Version: (was: 2.0-beta-1) Fix Version: (was: 2.0-beta-2) Component: (was: maven-resources-plugin)

[jira] Moved: (MRESOURCES-4) No way to specify encoding of files that are being filter in resoruces plugin

[ http://jira.codehaus.org/browse/MRESOURCES-4?page=all ] Vincent Massol moved MNG-1129 to MRESOURCES-4: -- Fix Version: (was: 2.0 (RC)) Component: (was: maven-resources-plugin) Workflow: jira (was: Maven) Key:

[jira] Moved: (MRESOURCES-1) Adding resources section to POM without directory element causes NullPointerException

[ http://jira.codehaus.org/browse/MRESOURCES-1?page=all ] Vincent Massol moved MNG-1147 to MRESOURCES-1: -- Version: (was: 2.0-beta-3) Fix Version: (was: 2.0 (RC)) Component: (was: maven-resources-plugin) Workfl

[jira] Moved: (MRESOURCES-2) "No such file or directory" when resource targetdirectory contains "../" and target/classes does not exist.

[ http://jira.codehaus.org/browse/MRESOURCES-2?page=all ] Vincent Massol moved MNG-1345 to MRESOURCES-2: -- Version: (was: 2.0) Fix Version: (was: 2.0.1) Component: (was: maven-resources-plugin) Workflow: jira

[jira] Moved: (MSOURCES-1) No resources directory is present in the generated jar

[ http://jira.codehaus.org/browse/MSOURCES-1?page=all ] Vincent Massol moved MNG-1748 to MSOURCES-1: Component: (was: maven-sources-plugin) Workflow: jira (was: Maven) Key: MSOURCES-1 (was: MNG-1748) Project: Maven 2

[jira] Created: (MPXDOC-186) Mailing list links break if the address starts with http

Mailing list links break if the address starts with http Key: MPXDOC-186 URL: http://jira.codehaus.org/browse/MPXDOC-186 Project: maven-xdoc-plugin Type: Bug Versions: 1.9.2 Reporter: Ortwin Glück

RE: JIRA Project for Maven 2.x Plug-ins

> -Original Message- > From: Jason van Zyl [mailto:[EMAIL PROTECTED] > Sent: mardi 20 décembre 2005 15:15 > To: Maven Developers List > Subject: Re: JIRA Project for Maven 2.x Plug-ins > > Vincent Massol wrote: > > Hi Jason, > > > > Great! > > > > Shouldn't we remove the JIRA components

Re: JIRA Project for Maven 2.x Plug-ins

Vincent Massol wrote: Hi Jason, Great! Shouldn't we remove the JIRA components for the plugins in the Maven 2 JIRA project? I think so. Deng and Allan were helping me transfer over the issues to the new project and that's complete so we go ahead and remove the components. Thanks -Vincent

[jira] Closed: (MEV-140) Tapestry POM missing dependencies for javassist (2.6), ognl (2.6.3), commons-fileupload (1.0)

[ http://jira.codehaus.org/browse/MEV-140?page=all ] Carlos Sanchez closed MEV-140: -- Assign To: Carlos Sanchez (was: Edwin Punzalan) Resolution: Fixed Used attached pom > Tapestry POM missing dependencies for javassist (2.6), ognl (2.6.3), > co

Site aggregation (Relocating discussion from confluence to dev)

Re discussion regarding site aggregation See: http://docs.codehaus.org/display/MAVEN/Sites+and+Inheritence for previous notes. Hi Brett, Re your last comments: 'The copy is done from the top level so it can run as an aggregator and the subprojects can be viewed as a single site and deployed a

[m2] custom plugin called multiple time with different configuration: problem

I have a site report/plugin that holds the common settings (actually all settings), it has the goal report I have for each specific report a subclass of that one that overrides a run() function (the only diffirence) if I use the this in the pom.xml, it uses the specific inputfile but if I do not

RE: JIRA Project for Maven 2.x Plug-ins

Hi Jason, Great! Shouldn't we remove the JIRA components for the plugins in the Maven 2 JIRA project? Thanks -Vincent > -Original Message- > From: Jason van Zyl [mailto:[EMAIL PROTECTED] > Sent: mardi 20 décembre 2005 03:33 > To: Maven Users List > Subject: JIRA Project for Maven 2.x Pl

[jira] Closed: (MAVENUPLOAD-642) iCal4j 0.9.18 - Maven bundle

[ http://jira.codehaus.org/browse/MAVENUPLOAD-642?page=all ] Carlos Sanchez closed MAVENUPLOAD-642: -- Assign To: Carlos Sanchez Resolution: Fixed > iCal4j 0.9.18 - Maven bundle > > > Key: MAVENUPLOAD-64

[jira] Closed: (MAVENUPLOAD-643) Upload ExtremeComponents 1.0.1-M3

[ http://jira.codehaus.org/browse/MAVENUPLOAD-643?page=all ] Carlos Sanchez closed MAVENUPLOAD-643: -- Assign To: Carlos Sanchez Resolution: Fixed > Upload ExtremeComponents 1.0.1-M3 > - > > Key: MAVE

[jira] Created: (MNG-1880) Add new pre and post phases to the integration-test phase

Add new pre and post phases to the integration-test phase - Key: MNG-1880 URL: http://jira.codehaus.org/browse/MNG-1880 Project: Maven 2 Type: Wish Components: Plugins and Lifecycle Versions: 2.0.1

[jira] Updated: (MPJAVADOC-68) Combined use of online and offline links

[ http://jira.codehaus.org/browse/MPJAVADOC-68?page=all ] Wouter Hermeling updated MPJAVADOC-68: -- Attachment: plugin.jelly.patch > Combined use of online and offline links > > > Key: MPJAVADOC-68 >

[jira] Commented: (MPJAVADOC-68) Combined use of online and offline links

[ http://jira.codehaus.org/browse/MPJAVADOC-68?page=comments#action_53806 ] Wouter Hermeling commented on MPJAVADOC-68: --- Hmm, i tried creating one for you, but: 1. The project.xml states that cvs is used, not svn 2. The connectionUrl in the project

[jira] Updated: (MRM-41) discover standalone POMs

[ http://jira.codehaus.org/browse/MRM-41?page=all ] John Tolentino updated MRM-41: -- Comment: was deleted > discover standalone POMs > > > Key: MRM-41 > URL: http://jira.codehaus.org/browse/MRM-41 > Project: Ma

[jira] Updated: (MRM-41) discover standalone POMs

[ http://jira.codehaus.org/browse/MRM-41?page=all ] John Tolentino updated MRM-41: -- Attachment: repository-manager.diff > discover standalone POMs > > > Key: MRM-41 > URL: http://jira.codehaus.org/browse/MRM-41 >

[jira] Reopened: (MPASPECTJ-21) Support AspectJ 5

[ http://jira.codehaus.org/browse/MPASPECTJ-21?page=all ] Carlos Sanchez reopened MPASPECTJ-21: - Assign To: (was: Carlos Sanchez) Updated to 1.5RC1, waiting for final > Support AspectJ 5 > - > > Key: MPASPECTJ-21 >

[jira] Updated: (MRM-41) discover standalone POMs

[ http://jira.codehaus.org/browse/MRM-41?page=all ] John Tolentino updated MRM-41: -- Attachment: (was: repository-manager.diff) > discover standalone POMs > > > Key: MRM-41 > URL: http://jira.codehaus.org/browse

[jira] Updated: (MRM-41) discover standalone POMs

[ http://jira.codehaus.org/browse/MRM-41?page=all ] John Tolentino updated MRM-41: -- Attachment: repository-manager.diff > discover standalone POMs > > > Key: MRM-41 > URL: http://jira.codehaus.org/browse/MRM-41 >

Improve methods to define the scope and packaging of dependencies (MNG-1732)

I'm back from vacation now, so if this won't start another holy war (like XML format) I have two questions on this issue: 1) Why is this a bad idea? 2) Assuming that this idea won't be done, any suggestions on how to configure the mapping of dependencies to RPM installation locations? A good dea

[jira] Created: (MPA-35) add Lukas Theussl to the PMC

add Lukas Theussl to the PMC Key: MPA-35 URL: http://jira.codehaus.org/browse/MPA-35 Project: Maven Project Administration Type: Task Reporter: Brett Porter Assigned to: Jason van Zyl Jason to add Lukas to the PMC roster in commi

Re: Moved: (MRELEASE-7) Release versioning does not work with dependencyManagement

[ http://jira.codehaus.org/browse/MRELEASE-7?page=all ] Jason van Zyl moved MNG-1728 to MRELEASE-7: --- Version: (was: 2.0.1) Component: (was: maven-release-plugin) Workflow: jira (was: Maven) Key: MRELEASE-7 (was: M

Re: Moved: (MRELEASE-36) Release plugin fails to update SNAPSHOTS in the dependencyManagement section

[ http://jira.codehaus.org/browse/MRELEASE-36?page=all ] Jason van Zyl moved MNG-1374 to MRELEASE-36: Version: (was: 2.0) Fix Version: (was: 2.0.1) Component: (was: maven-release-plugin) Workflow: jira (was:

[jira] Commented: (MSITE-11) PluginManagement config is not used by plugins enabled in the site generation phase

[ http://jira.codehaus.org/browse/MSITE-11?page=comments#action_53795 ] Indrajit Raychaudhuri commented on MSITE-11: Wonderful! So the idea in [#action_53690] _actually_ makes sense to me now and appears clean enough too. This also appears to

<    1   2