[jira] Work started: (MEAR-75) Incorrect file name in class path (in manifest) if specifying different bundleFileName for module

[ http://jira.codehaus.org/browse/MEAR-75?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on MEAR-75 started by Stephane Nicoll. > Incorrect file name in class path (in manifest) if specifying different > bundleFileName for module > --

[jira] Updated: (MEAR-75) Incorrect file name in class path (in manifest) if specifying different bundleFileName for module

[ http://jira.codehaus.org/browse/MEAR-75?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephane Nicoll updated MEAR-75: Assignee: Stephane Nicoll Fix Version/s: (was: 2.4) 2.3.3 Last reported bug

[jira] Closed: (MEAR-103) Filtered MANIFEST not added to generated EAR

[ http://jira.codehaus.org/browse/MEAR-103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephane Nicoll closed MEAR-103. Resolution: Fixed Fixed. Thanks for the test case! > Filtered MANIFEST not added to generated EAR > --

[jira] Work started: (MEAR-103) Filtered MANIFEST not added to generated EAR

[ http://jira.codehaus.org/browse/MEAR-103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on MEAR-103 started by Stephane Nicoll. > Filtered MANIFEST not added to generated EAR > > > Key: MEAR-103 >

[jira] Updated: (MEAR-103) Filtered MANIFEST not added to generated EAR

[ http://jira.codehaus.org/browse/MEAR-103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephane Nicoll updated MEAR-103: - Fix Version/s: 2.3.3 > Filtered MANIFEST not added to generated EAR > ---

[jira] Closed: (MEAR-95) Cannot set context-root to be the root context

[ http://jira.codehaus.org/browse/MEAR-95?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephane Nicoll closed MEAR-95. --- Assignee: Stephane Nicoll Resolution: Won't Fix At first, I thought that setting an empty context would

[jira] Updated: (MEAR-95) Cannot set context-root to be the root context

[ http://jira.codehaus.org/browse/MEAR-95?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephane Nicoll updated MEAR-95: Fix Version/s: (was: 2.3.3) > Cannot set context-root to be the root context > -

[jira] Updated: (MEAR-95) Cannot set context-root to be the root context

[ http://jira.codehaus.org/browse/MEAR-95?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephane Nicoll updated MEAR-95: Affects Version/s: 2.0 > Cannot set context-root to be the root context > --

[jira] Closed: (MEAR-104) wrong jboss-app.xml

[ http://jira.codehaus.org/browse/MEAR-104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephane Nicoll closed MEAR-104. Resolution: Fixed Fixed. Added it 057 > wrong jboss-app.xml > --- > > Key:

[jira] Closed: (MEAR-105) Unable to set some properties for jboss-app.xml

[ http://jira.codehaus.org/browse/MEAR-105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephane Nicoll closed MEAR-105. Resolution: Fixed Applied. Thanks Evgeny! > Unable to set some properties for jboss-app.xml >

[jira] Work started: (MEAR-105) Unable to set some properties for jboss-app.xml

[ http://jira.codehaus.org/browse/MEAR-105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on MEAR-105 started by Stephane Nicoll. > Unable to set some properties for jboss-app.xml > --- > > Key: MEAR-105

[jira] Reopened: (MNG-4054) Command Line interprets bogus options

[ http://jira.codehaus.org/browse/MNG-4054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Benedict reopened MNG-4054: I am reopening because Brett can confirm it, although it's no longer the exact bug I had. I actually tested ag

[jira] Updated: (MJAVADOC-228) Please add support for signing javadoc jar files.

[ http://jira.codehaus.org/browse/MJAVADOC-228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Schulte updated MJAVADOC-228: --- Attachment: maven-jarsigner-plugin.zip Ok! One last change. I added an additional argumen

[jira] Commented: (MNG-4054) Command Line interprets bogus options

[ http://jira.codehaus.org/browse/MNG-4054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=174177#action_174177 ] Brett Porter commented on MNG-4054: --- John, that does reproduce the error. it behaved like -X OXOXOXO

[jira] Commented: (MJAVADOC-228) Please add support for signing javadoc jar files.

[ http://jira.codehaus.org/browse/MJAVADOC-228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=174174#action_174174 ] Benjamin Bentmann commented on MJAVADOC-228: Sorry, I was pretty busy these days but ho

[jira] Reopened: (MAVENUPLOAD-2417) Sync maven-scm-provider-svnjava from code.google.com

[ http://jira.codehaus.org/browse/MAVENUPLOAD-2417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy reopened MAVENUPLOAD-2417: --- reopen issue as project deploiement will be moved to oss.sonatype.org. Just waiting for a

[jira] Closed: (MRELEASE-440) release:prepare fails due to svn "file exists" complaint

[ http://jira.codehaus.org/browse/MRELEASE-440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy closed MRELEASE-440. - Resolution: Fixed fixed in 2.0-beta-9 > release:prepare fails due to svn "file exists" complaint > -

[jira] Updated: (MRELEASE-442) scm tag phase ignores custom message

[ http://jira.codehaus.org/browse/MRELEASE-442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy updated MRELEASE-442: -- Assignee: Olivier Lamy Fix Version/s: 2.0-beta-10 > scm tag phase ignores custom message >

[jira] Updated: (SCM-460) tag command ignores custom message parameter

[ http://jira.codehaus.org/browse/SCM-460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy updated SCM-460: - Patch Submitted: (was: [Yes]) could you please provide a patch with using svn diff. Thanks > tag command ignore

[jira] Updated: (SCM-460) tag command ignores custom message parameter

[ http://jira.codehaus.org/browse/SCM-460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy updated SCM-460: - Assignee: Olivier Lamy Fix Version/s: 1.3 > tag command ignores custom message parameter > --

[jira] Closed: (MNG-4054) Command Line interprets bogus options

[ http://jira.codehaus.org/browse/MNG-4054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Casey closed MNG-4054. --- Assignee: John Casey Resolution: Cannot Reproduce I've tried this with Maven 2.1.0, 2.0.10, and 2.1.1-SNAPSHOT,

[jira] Created: (MAVENUPLOAD-2436) publication auto-sync request for hsqldb

publication auto-sync request for hsqldb Key: MAVENUPLOAD-2436 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2436 Project: Maven Upload Requests Issue Type: Wish Reporter: Blaine Simpso

[jira] Updated: (MNG-4112) Set property containing the currently executing maven version.

[ http://jira.codehaus.org/browse/MNG-4112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Casey updated MNG-4112: Fix Version/s: (was: 2.1.1) (was: 3.0-alpha-3) 2.2.0-M1 not a regress

[jira] Commented: (MSITE-402) Execution order of report plugins is arbitrary if inheritance is involved

[ http://jira.codehaus.org/browse/MSITE-402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=174148#action_174148 ] John Casey commented on MSITE-402: -- I've traced the handling of reports through POM inheritance (veri

[jira] Moved: (MSITE-402) Execution order of report plugins is arbitrary if inheritance is involved

[ http://jira.codehaus.org/browse/MSITE-402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Casey moved MNG-4118 to MSITE-402: --- Affects Version/s: (was: 2.1.0) (was: 2.0.10)

[jira] Updated: (MSOURCES-44) If project doesn't contain sources (contains only test sources) source:jar will fail

[ http://jira.codehaus.org/browse/MSOURCES-44?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ben Tatham updated MSOURCES-44: --- Attachment: failOnEmpty.patch Here is a simple patch to provide a "failOnEmpty" parameter that can be set

[jira] Commented: (MSOURCES-44) If project doesn't contain sources (contains only test sources) source:jar will fail

[ http://jira.codehaus.org/browse/MSOURCES-44?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=174132#action_174132 ] Ben Tatham commented on MSOURCES-44: We have the same issue, with some test-less projects (like

[jira] Created: (SUREFIRE-548) System properties not inherited

System properties not inherited --- Key: SUREFIRE-548 URL: http://jira.codehaus.org/browse/SUREFIRE-548 Project: Maven Surefire Issue Type: Bug Components: plugin Affects Versions: 2.4.2

[jira] Commented: (SUREFIRE-482) Surefire tries to run JUnit4 tests that contain no @Test annotations

[ http://jira.codehaus.org/browse/SUREFIRE-482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=174117#action_174117 ] Keith Wedinger commented on SUREFIRE-482: - I would also like to see surefire's JUnit 4.4 su

[jira] Updated: (MJAVADOC-228) Please add support for signing javadoc jar files.

[ http://jira.codehaus.org/browse/MJAVADOC-228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Schulte updated MJAVADOC-228: --- Attachment: maven-jarsigner-plugin.zip Added an archive parameter to support signing and

[jira] Commented: (MWAR-158) Overlaying breaks configuration of webXml with a fatal error

[ http://jira.codehaus.org/browse/MWAR-158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=174110#action_174110 ] Simone Pierazzini commented on MWAR-158: I think that the exception occurs because WarProjectPa

[jira] Created: (MSITE-401) site goal should fail on AptParseException

site goal should fail on AptParseException -- Key: MSITE-401 URL: http://jira.codehaus.org/browse/MSITE-401 Project: Maven 2.x Site Plugin Issue Type: Bug Affects Versions: 2.0 Reporter

[jira] Created: (MANTTASKS-144) "Error reading settings file" error is reported when settings.xml is deleted from maven/conf folder.

"Error reading settings file" error is reported when settings.xml is deleted from maven/conf folder. Key: MANTTASKS-144 URL: http://jira.codehaus.org/browse/MANTT

[jira] Commented: (MRELEASE-440) release:prepare fails due to svn "file exists" complaint

[ http://jira.codehaus.org/browse/MRELEASE-440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=174104#action_174104 ] Bjarte Nilsen commented on MRELEASE-440: I just tried with 2.0-beta-9 and the problem had g

[jira] Commented: (MRELEASE-440) release:prepare fails due to svn "file exists" complaint

[ http://jira.codehaus.org/browse/MRELEASE-440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=174098#action_174098 ] Bjarte Nilsen commented on MRELEASE-440: Same problem for me - on a multimodule project usi