[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 reportingManagement/ idea in [#action_53690] _actually_ makes sense to me now and appears clean enough too.

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:

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] 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

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

[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] 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:

[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] 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] 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:

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

[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

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

[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),

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

[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

[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

[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: (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-6) When filtering, properties defined in projectproperties 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:

[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] 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

[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 Key:

[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:

[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] 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

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] 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 ---

[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] 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] 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] 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

[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:report

[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] 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:

[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

[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

[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

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 to decide

[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

[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] 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] 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] 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 errors

[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 builds

[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

[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-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 percentage

[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 be

[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] 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:

[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

[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] Updated: (MCLOVER-9) Locale problem in Clover plugin

[ http://jira.codehaus.org/browse/MCLOVER-9?page=all ] Vincent Massol updated MCLOVER-9: - 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 Locale problem in Clover plugin

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

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

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

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

[jira] Updated: (MCLOVER-10) Upgrade to Clover 1.3.10_01

[ http://jira.codehaus.org/browse/MCLOVER-10?page=all ] Vincent Massol updated MCLOVER-10: -- 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

[jira] Closed: (MCLOVER-10) Upgrade to Clover 1.3.10_01

[ http://jira.codehaus.org/browse/MCLOVER-10?page=all ] Vincent Massol closed MCLOVER-10: - Resolution: Fixed Fixed again versions after the jira move from Maven 2 to Maven 2.x Clover Plugin Upgrade to Clover 1.3.10_01

[jira] Reopened: (MCLOVER-10) Upgrade to Clover 1.3.10_01

[ http://jira.codehaus.org/browse/MCLOVER-10?page=all ] Vincent Massol reopened MCLOVER-10: --- Reopen to set again versions after the jira move from Maven 2 to Maven 2.x Clover Plugin Upgrade to Clover 1.3.10_01 ---

[jira] Updated: (MCLEAN-2) Delete additional directories and files including testOutputDirectory, outputDirectory, and directory

[ http://jira.codehaus.org/browse/MCLEAN-2?page=all ] ruel loehr updated MCLEAN-2: Attachment: MCLEAN-2.txt Delete additional directories and files including testOutputDirectory, outputDirectory, and directory

[jira] Commented: (MCLEAN-2) Delete additional directories and files including testOutputDirectory, outputDirectory, and directory

[ http://jira.codehaus.org/browse/MCLEAN-2?page=comments#action_53847 ] ruel loehr commented on MCLEAN-2: - I ran into the same situation and have attached a patch MCLEAN-2.txt as well. Delete additional directories and files including testOutputDirectory,

[jira] Commented: (MCLEAN-2) Delete additional directories and files including testOutputDirectory, outputDirectory, and directory

[ http://jira.codehaus.org/browse/MCLEAN-2?page=comments#action_53849 ] Dan Tran commented on MCLEAN-2: --- rather than removing directories, It is best to remove using FileSet(s) where we can exclude/includes files within a directory. Delete additional

[jira] Commented: (MJAVADOC-30) javadoc plugin does not work on war projects

[ http://jira.codehaus.org/browse/MJAVADOC-30?page=comments#action_53850 ] Matt Hicks commented on MJAVADOC-30: I downloaded Maven 2.0.1 and new repository plugins and I still see this behavior. Are there additional steps required or can we re-open

[jira] Commented: (MCLEAN-2) Delete additional directories and files including testOutputDirectory, outputDirectory, and directory

[ http://jira.codehaus.org/browse/MCLEAN-2?page=comments#action_53851 ] ruel loehr commented on MCLEAN-2: - Is there an example in any existing plugins where filesets are used? Delete additional directories and files including testOutputDirectory,

[jira] Commented: (CONTINUUM-354) Need a way to poll for new projects

[ http://jira.codehaus.org/browse/CONTINUUM-354?page=comments#action_53852 ] Matthew Beermann commented on CONTINUUM-354: No, CONTINUUM-330 didn't solve this. Here's why: 1. Add a new module/ to the parent project and check in. 2. Rebuild the

[jira] Commented: (MCLEAN-2) Delete additional directories and files including testOutputDirectory, outputDirectory, and directory

[ http://jira.codehaus.org/browse/MCLEAN-2?page=comments#action_53853 ] Dan Tran commented on MCLEAN-2: --- mavne-assembly-plugin uses its own generated FileSet maven-scm-plugin ( in maven-scm ) uses it s own ScmFileSet Delete additional directories and

[jira] Closed: (MNG-1690) [maven-ejb3-plugin] NPE in EJB3Mojo.java

[ http://jira.codehaus.org/browse/MNG-1690?page=all ] Stephane Nicoll closed MNG-1690: Resolution: Fixed Applied to ejb3 and par plugins ; Thanks. [maven-ejb3-plugin] NPE in EJB3Mojo.java Key:

[jira] Closed: (MNG-1691) [maven-par-plugin] NPE in ParMojo.java

[ http://jira.codehaus.org/browse/MNG-1691?page=all ] Stephane Nicoll closed MNG-1691: Resolution: Duplicate See MNG-1690. [maven-par-plugin] NPE in ParMojo.java -- Key: MNG-1691 URL:

[jira] Reopened: (MEAR-15) Support of sar files

[ http://jira.codehaus.org/browse/MEAR-15?page=all ] Stephane Nicoll reopened MEAR-15: - Building the roadmap for 2.1 Support of sar files Key: MEAR-15 URL: http://jira.codehaus.org/browse/MEAR-15

[jira] Closed: (MEAR-15) Support of sar files

[ http://jira.codehaus.org/browse/MEAR-15?page=all ] Stephane Nicoll closed MEAR-15: --- Resolution: Fixed Fix Version: 2.1 Support of sar files Key: MEAR-15 URL: http://jira.codehaus.org/browse/MEAR-15

[jira] Reopened: (MEAR-12) Make maven-ear-plugin feature complete against m1 version

[ http://jira.codehaus.org/browse/MEAR-12?page=all ] Stephane Nicoll reopened MEAR-12: - Make maven-ear-plugin feature complete against m1 version - Key: MEAR-12 URL:

[jira] Closed: (MEAR-12) Make maven-ear-plugin feature complete against m1 version

[ http://jira.codehaus.org/browse/MEAR-12?page=all ] Stephane Nicoll closed MEAR-12: --- Resolution: Fixed Fix Version: 2.0 Make maven-ear-plugin feature complete against m1 version -

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

[ http://jira.codehaus.org/browse/MPXDOC-186?page=all ] Lukas Theussl closed MPXDOC-186: Resolution: Fixed Fix Version: 1.10 Mailing list links break if the address starts with http

[jira] Closed: (MEAR-4) Some src/main/resources contents are not included in the package

[ http://jira.codehaus.org/browse/MEAR-4?page=all ] Stephane Nicoll closed MEAR-4: -- Resolution: Fixed Fix Version: 2.0 Some src/main/resources contents are not included in the package

[jira] Reopened: (MEAR-4) Some src/main/resources contents are not included in the package

[ http://jira.codehaus.org/browse/MEAR-4?page=all ] Stephane Nicoll reopened MEAR-4: Some src/main/resources contents are not included in the package Key: MEAR-4

[jira] Reopened: (MEAR-9) Add support for packaging .par and .ejb3 files in an .ear file

[ http://jira.codehaus.org/browse/MEAR-9?page=all ] Stephane Nicoll reopened MEAR-9: Add support for packaging .par and .ejb3 files in an .ear file -- Key: MEAR-9 URL:

[jira] Closed: (MEAR-9) Add support for packaging .par and .ejb3 files in an .ear file

[ http://jira.codehaus.org/browse/MEAR-9?page=all ] Stephane Nicoll closed MEAR-9: -- Resolution: Fixed Fix Version: 2.1 Add support for packaging .par and .ejb3 files in an .ear file --

[jira] Closed: (MEAR-6) Packaging plugins like war, ear does not check artifacts if they are tagged as optional

[ http://jira.codehaus.org/browse/MEAR-6?page=all ] Stephane Nicoll closed MEAR-6: -- Resolution: Fixed Fix Version: 2.1 Packaging plugins like war, ear does not check artifacts if they are tagged as optional

[jira] Reopened: (MEAR-5) application.xml generated incorrectly

[ http://jira.codehaus.org/browse/MEAR-5?page=all ] Stephane Nicoll reopened MEAR-5: application.xml generated incorrectly - Key: MEAR-5 URL: http://jira.codehaus.org/browse/MEAR-5

[jira] Reopened: (MEAR-6) Packaging plugins like war, ear does not check artifacts if they are tagged as optional

[ http://jira.codehaus.org/browse/MEAR-6?page=all ] Stephane Nicoll reopened MEAR-6: Packaging plugins like war, ear does not check artifacts if they are tagged as optional

[jira] Closed: (MEAR-5) application.xml generated incorrectly

[ http://jira.codehaus.org/browse/MEAR-5?page=all ] Stephane Nicoll closed MEAR-5: -- Resolution: Fixed Fix Version: 2.1 application.xml generated incorrectly - Key: MEAR-5 URL:

[jira] Closed: (MEAR-13) excluding resources in ear archive

[ http://jira.codehaus.org/browse/MEAR-13?page=all ] Stephane Nicoll closed MEAR-13: --- Resolution: Fixed Fix Version: 2.1 excluding resources in ear archive -- Key: MEAR-13 URL:

[jira] Reopened: (MEAR-2) EAR plugin ignores application XML setting

[ http://jira.codehaus.org/browse/MEAR-2?page=all ] Stephane Nicoll reopened MEAR-2: EAR plugin ignores application XML setting -- Key: MEAR-2 URL: http://jira.codehaus.org/browse/MEAR-2

[jira] Reopened: (MEAR-13) excluding resources in ear archive

[ http://jira.codehaus.org/browse/MEAR-13?page=all ] Stephane Nicoll reopened MEAR-13: - excluding resources in ear archive -- Key: MEAR-13 URL: http://jira.codehaus.org/browse/MEAR-13

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

[ http://jira.codehaus.org/browse/MPJAVADOC-68?page=comments#action_53857 ] Lukas Theussl commented on MPJAVADOC-68: The source repository is here: http://svn.apache.org/viewcvs.cgi/maven/maven-1/plugins/trunk/javadoc/ please check the main maven

[jira] Closed: (MEAR-10) need to set default bundleDir for all ear modules

[ http://jira.codehaus.org/browse/MEAR-10?page=all ] Stephane Nicoll closed MEAR-10: --- Resolution: Fixed Fix Version: 2.1 need to set default bundleDir for all ear modules - Key:

[jira] Closed: (MEAR-2) EAR plugin ignores application XML setting

[ http://jira.codehaus.org/browse/MEAR-2?page=all ] Stephane Nicoll closed MEAR-2: -- Resolution: Fixed Fix Version: 2.1 EAR plugin ignores application XML setting -- Key: MEAR-2 URL:

[jira] Reopened: (MEAR-10) need to set default bundleDir for all ear modules

[ http://jira.codehaus.org/browse/MEAR-10?page=all ] Stephane Nicoll reopened MEAR-10: - need to set default bundleDir for all ear modules - Key: MEAR-10 URL:

[jira] Updated: (MEAR-8) Add security role definitions to maven-ear-plugin

[ http://jira.codehaus.org/browse/MEAR-8?page=all ] Stephane Nicoll updated MEAR-8: --- Fix Version: 2.2 type: Improvement (was: Bug) Add security role definitions to maven-ear-plugin -

[jira] Reopened: (MEAR-1) Plugin configuration doesn't support .ejb3 and .par EJB modules

[ http://jira.codehaus.org/browse/MEAR-1?page=all ] Stephane Nicoll reopened MEAR-1: Plugin configuration doesn't support .ejb3 and .par EJB modules --- Key: MEAR-1 URL:

[jira] Closed: (MEAR-1) Plugin configuration doesn't support .ejb3 and .par EJB modules

[ http://jira.codehaus.org/browse/MEAR-1?page=all ] Stephane Nicoll closed MEAR-1: -- Resolution: Fixed Fix Version: 2.1 Plugin configuration doesn't support .ejb3 and .par EJB modules

[jira] Deleted: (MEAR-7) bundleDir

[ http://jira.codehaus.org/browse/MEAR-7?page=all ] Stephane Nicoll deleted MEAR-7: --- bundleDir -- Key: MEAR-7 URL: http://jira.codehaus.org/browse/MEAR-7 Project: Maven 2.x Ear Plugin Type: Bug

[jira] Updated: (MEAR-3) ear includes and excludes don't handle comma separated tokens

[ http://jira.codehaus.org/browse/MEAR-3?page=all ] Stephane Nicoll updated MEAR-3: --- Version: 2.1 2.0 Fix Version: 2.2 Summary: ear includes and excludes don't handle comma separated tokens (was: war includes and excludes

[jira] Commented: (MASSEMBLY-17) Unable to map a file in FileSet to another file name

[ http://jira.codehaus.org/browse/MASSEMBLY-17?page=comments#action_53858 ] Dan Tran commented on MASSEMBLY-17: --- OK, I am going to use Edwin's suggestion since most of code already there in FileSet handling. Unable to map a file in FileSet to another

Re: Problems with JIRA Plug-in Projects

Vincent Massol wrote: I'm working on restoring the clover plugin as I write. I think we can fix things by hands rather than do a dangerous restore (we won't know how many new issues were added after the last backup point). Cool, thanks. Stephane is fixing the EAR and RAR plugins. Shall I

Re: Problems with JIRA Plug-in Projects

EAR plugin is done, sorry for the noise. On 12/20/05, Jason van Zyl [EMAIL PROTECTED] wrote: Vincent Massol wrote: I'm working on restoring the clover plugin as I write. I think we can fix things by hands rather than do a dangerous restore (we won't know how many new issues were added

[continuum build - FAILED - update] Tue Dec 20 18:00:00 GMT 2005

Log: http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20051220.18.txt

[jira] Created: (MEAR-16) Packaging does not check artifacts if they are tagged as optional

Packaging does not check artifacts if they are tagged as optional -- Key: MEAR-16 URL: http://jira.codehaus.org/browse/MEAR-16 Project: Maven 2.x Ear Plugin Type: Bug Reporter: Stephane Nicoll

[jira] Moved: (MRAR-2) Packaging does not check artifacts if they are tagged as optional

[ http://jira.codehaus.org/browse/MRAR-2?page=all ] Stephane Nicoll moved MEAR-16 to MRAR-2: Fix Version: (was: 2.1) 2.1 Key: MRAR-2 (was: MEAR-16) Project: Maven 2.x Rar Plugin (was: Maven 2.x Ear

  1   2   >