[jira] Commented: (MECLIPSE-252) Error trying to create an EAR project that contains one web module. It doesn't point to the local project, but only tries to find it in the local and remote repositori

[ http://jira.codehaus.org/browse/MECLIPSE-252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=157046#action_157046 ] Michael Johns commented on MECLIPSE-252: I'll put in an enthusiastic vote for this one. We

[jira] Commented: (MECLIPSE-443) Only include **/*.java in Java source directories

[ http://jira.codehaus.org/browse/MECLIPSE-443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=156002#action_156002 ] Michael Johns commented on MECLIPSE-443: Yes, that's the default behavior of the compiler p

[jira] Commented: (MECLIPSE-423) NullPointerException when existing Manifest.MF file has no Class-Path element

[ http://jira.codehaus.org/browse/MECLIPSE-423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=155289#action_155289 ] Michael Johns commented on MECLIPSE-423: Barrie, I pulled down the source and had a look at

[jira] Commented: (SCM-406) scm tag does not work with Subversion 1.5.1

[ http://jira.codehaus.org/browse/SCM-406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=147686#action_147686 ] Michael Johns commented on SCM-406: --- I have a little color I can add to this discussion. We too use M

[jira] Created: (MRELEASE-362) Support tagging nested projects

Support tagging nested projects --- Key: MRELEASE-362 URL: http://jira.codehaus.org/browse/MRELEASE-362 Project: Maven 2.x Release Plugin Issue Type: Improvement Components: scm Affects Versions: 2.0

[jira] Created: (MJAVADOC-197) Provide flag to ignore errors

Provide flag to ignore errors - Key: MJAVADOC-197 URL: http://jira.codehaus.org/browse/MJAVADOC-197 Project: Maven 2.x Javadoc Plugin Issue Type: Improvement Affects Versions: 2.4 Reporter: Michael

[jira] Created: (MECLIPSE-456) Allow for manifest customization

Allow for manifest customization Key: MECLIPSE-456 URL: http://jira.codehaus.org/browse/MECLIPSE-456 Project: Maven 2.x Eclipse Plugin Issue Type: Improvement Affects Versions: 2.5.1 Reporter:

[jira] Commented: (MECLIPSE-370) Option to rely on transitive dependencies

[ http://jira.codehaus.org/browse/MECLIPSE-370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=134865#action_134865 ] Michael Johns commented on MECLIPSE-370: We encountered the following situation: - Projec

[jira] Created: (MCHANGES-111) Announcement Mojo doesn't respect Jira authentication settings

Announcement Mojo doesn't respect Jira authentication settings -- Key: MCHANGES-111 URL: http://jira.codehaus.org/browse/MCHANGES-111 Project: Maven 2.x Changes Plugin Issue Type: B

[jira] Updated: (MECLIPSE-443) Only include **/*.java in Java source directories

[ http://jira.codehaus.org/browse/MECLIPSE-443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Johns updated MECLIPSE-443: --- Attachment: MECLIPSE-443.2.patch First patch was incomplete. Sorry about that. > Only include *

[jira] Updated: (MECLIPSE-443) Only include **/*.java in Java source directories

[ http://jira.codehaus.org/browse/MECLIPSE-443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Johns updated MECLIPSE-443: --- Attachment: MECLIPSE-443.patch > Only include **/*.java in Java source directories >

[jira] Created: (MECLIPSE-443) Only include **/*.java in Java source directories

Only include **/*.java in Java source directories - Key: MECLIPSE-443 URL: http://jira.codehaus.org/browse/MECLIPSE-443 Project: Maven 2.x Eclipse Plugin Issue Type: Improvement Affects Ver

[jira] Updated: (MECLIPSE-442) Classpath container entries should come last in .classpath

[ http://jira.codehaus.org/browse/MECLIPSE-442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Johns updated MECLIPSE-442: --- Attachment: MECLIPSE-442.patch > Classpath container entries should come last in .classpath > ---

[jira] Commented: (MECLIPSE-442) Classpath container entries should come last in .classpath

[ http://jira.codehaus.org/browse/MECLIPSE-442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=132549#action_132549 ] Michael Johns commented on MECLIPSE-442: If it's desirable for some people that the entries

[jira] Created: (MECLIPSE-442) Classpath container entries should come last in .classpath

Classpath container entries should come last in .classpath -- Key: MECLIPSE-442 URL: http://jira.codehaus.org/browse/MECLIPSE-442 Project: Maven 2.x Eclipse Plugin Issue Type: Improveme

[jira] Commented: (MECLIPSE-439) Support filesets for clean goal

[ http://jira.codehaus.org/browse/MECLIPSE-439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=131625#action_131625 ] Michael Johns commented on MECLIPSE-439: I just dug into the source a little more, and I re

[jira] Created: (MECLIPSE-439) Support filesets for clean goal

Support filesets for clean goal --- Key: MECLIPSE-439 URL: http://jira.codehaus.org/browse/MECLIPSE-439 Project: Maven 2.x Eclipse Plugin Issue Type: Improvement Affects Versions: 2.5.1 Reporter: M

[jira] Updated: (MECLIPSE-430) Non-project EJB dependencies should not be placed in the .modulemaps file

[ http://jira.codehaus.org/browse/MECLIPSE-430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Johns updated MECLIPSE-430: --- Attachment: MECLIPSE-430.2.patch A byproduct of solving the problem presented in this issue is th

[jira] Updated: (MECLIPSE-432) RAD goal should support security-role element in application.xml

[ http://jira.codehaus.org/browse/MECLIPSE-432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Johns updated MECLIPSE-432: --- Attachment: MECLIPSE-432.3.patch Fix to make sure security-role nodes appear at the end of an upd

[jira] Updated: (MECLIPSE-432) RAD goal should support security-role element in application.xml

[ http://jira.codehaus.org/browse/MECLIPSE-432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Johns updated MECLIPSE-432: --- Attachment: MECLIPSE-432.2.patch Apologies, but my first patch was incomplete. This patch is to

[jira] Created: (MECLIPSE-433) Plugin could write out a .webspheredeploy for RAD

Plugin could write out a .webspheredeploy for RAD - Key: MECLIPSE-433 URL: http://jira.codehaus.org/browse/MECLIPSE-433 Project: Maven 2.x Eclipse Plugin Issue Type: Improvement Affects Ver

[jira] Created: (MECLIPSE-432) RAD goal should support security-role element in application.xml

RAD goal should support security-role element in application.xml Key: MECLIPSE-432 URL: http://jira.codehaus.org/browse/MECLIPSE-432 Project: Maven 2.x Eclipse Plugin Issue Typ

[jira] Created: (MECLIPSE-431) Non-project EJB dependencies need a version number in application.xml

Non-project EJB dependencies need a version number in application.xml - Key: MECLIPSE-431 URL: http://jira.codehaus.org/browse/MECLIPSE-431 Project: Maven 2.x Eclipse Plugin

[jira] Updated: (MECLIPSE-430) Non-project EJB dependencies should not be placed in the .modulemaps file

[ http://jira.codehaus.org/browse/MECLIPSE-430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Johns updated MECLIPSE-430: --- Attachment: MECLIPSE-430.patch You can of course ignore the C2PA comments. Those are there so I

[jira] Created: (MECLIPSE-430) Non-project EJB dependencies should not be placed in the .modulemaps file

Non-project EJB dependencies should not be placed in the .modulemaps file - Key: MECLIPSE-430 URL: http://jira.codehaus.org/browse/MECLIPSE-430 Project: Maven 2.x Eclipse Plugin

[jira] Updated: (MECLIPSE-429) WID requires that src/main/resources directory be the first resources directory listed

[ http://jira.codehaus.org/browse/MECLIPSE-429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Johns updated MECLIPSE-429: --- Attachment: MECLIPSE-429.patch You can ignore the @C2PA line, of course. That's just a comment I

[jira] Commented: (MECLIPSE-429) WID requires that src/main/resources directory be the first resources directory listed

[ http://jira.codehaus.org/browse/MECLIPSE-429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=130519#action_130519 ] Michael Johns commented on MECLIPSE-429: See http://www-1.ibm.com/support/docview.wss?rs=2

[jira] Created: (MECLIPSE-429) WID requires that src/main/resources directory be the first resources directory listed

WID requires that src/main/resources directory be the first resources directory listed -- Key: MECLIPSE-429 URL: http://jira.codehaus.org/browse/MECLIPSE-429 Project:

[jira] Commented: (MECLIPSE-423) NullPointerException when existing Manifest.MF file has no Class-Path element

[ http://jira.codehaus.org/browse/MECLIPSE-423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=130507#action_130507 ] Michael Johns commented on MECLIPSE-423: You'll also notice in the POM that we're using a c

[jira] Updated: (MECLIPSE-423) NullPointerException when existing Manifest.MF file has no Class-Path element

[ http://jira.codehaus.org/browse/MECLIPSE-423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Johns updated MECLIPSE-423: --- Attachment: pom.xml POM file for offending project. Note that this is by far the most complicate

[jira] Created: (MECLIPSE-423) NullPointerException when existing Manifest.MF file has no Class-Path element

NullPointerException when existing Manifest.MF file has no Class-Path element - Key: MECLIPSE-423 URL: http://jira.codehaus.org/browse/MECLIPSE-423 Project: Maven 2.x Eclipse

[jira] Created: (CONTINUUM-1630) Error attempting to delete project group

Error attempting to delete project group Key: CONTINUUM-1630 URL: http://jira.codehaus.org/browse/CONTINUUM-1630 Project: Continuum Issue Type: Bug Components: Database Affects Versions: