[jira] Reopened: (MSITE-579) SCM URLs Incorrect for Multi-Module Build Where Module Name != artifactId

[ http://jira.codehaus.org/browse/MSITE-579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Carman reopened MSITE-579: Re-opening because having it stated in documentation doesn't justify this as being reasonable. SCM URLs

[jira] Commented: (MSITE-579) SCM URLs Incorrect for Multi-Module Build Where Module Name != artifactId

[ http://jira.codehaus.org/browse/MSITE-579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=263030#action_263030 ] James Carman commented on MSITE-579: I don't think this should just be acceptable and written off

[jira] Commented: (MSITE-579) SCM URLs Incorrect for Multi-Module Build Where Module Name != artifactId

[ http://jira.codehaus.org/browse/MSITE-579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=263034#action_263034 ] James Carman commented on MSITE-579: I've linked the issue you mentioned, Joerg. It's nice to see

[jira] Created: (MSITE-579) SCM URLs Incorrect for Multi-Module Build Where Module Name != artifactId

SCM URLs Incorrect for Multi-Module Build Where Module Name != artifactId - Key: MSITE-579 URL: http://jira.codehaus.org/browse/MSITE-579 Project: Maven 2.x and 3.x Site Plugin

[jira] Commented: (MAVENUPLOAD-2810) Please Upload Metastopheles 1.2 Release

[ http://jira.codehaus.org/browse/MAVENUPLOAD-2810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=261300#action_261300 ] James Carman commented on MAVENUPLOAD-2810: --- Brian, Okay, which one is it? I

[jira] Created: (MAVENUPLOAD-2809) -rsync_ssh request for metastopheles.sourceforge.net

-rsync_ssh request for metastopheles.sourceforge.net Key: MAVENUPLOAD-2809 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2809 Project: Maven Upload Requests Issue Type: Wish

[jira] Commented: (MAVENUPLOAD-2809) -rsync_ssh request for metastopheles.sourceforge.net

[ http://jira.codehaus.org/browse/MAVENUPLOAD-2809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=246377#action_246377 ] James Carman commented on MAVENUPLOAD-2809: --- Sorry, I was trying to clone my previous

[jira] Closed: (MAVENUPLOAD-2809) -rsync_ssh request for metastopheles.sourceforge.net

[ http://jira.codehaus.org/browse/MAVENUPLOAD-2809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Carman closed MAVENUPLOAD-2809. - Resolution: Fixed -rsync_ssh request for metastopheles.sourceforge.net

[jira] Created: (MAVENUPLOAD-2810) Please Upload Metastopheles 1.2 Release

Please Upload Metastopheles 1.2 Release --- Key: MAVENUPLOAD-2810 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2810 Project: Maven Upload Requests Issue Type: Task Reporter: James Carman

[jira] Commented: (MRELEASE-458) Branch Does Not Honor updateWorkingCopyVersions Setting

[ http://jira.codehaus.org/browse/MRELEASE-458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=182856#action_182856 ] James Carman commented on MRELEASE-458: --- I verified it. This seems to be working correctly

[jira] Created: (MRELEASE-458) Branch Does Not Honor updateWorkingCopyVersions Setting

Branch Does Not Honor updateWorkingCopyVersions Setting --- Key: MRELEASE-458 URL: http://jira.codehaus.org/browse/MRELEASE-458 Project: Maven 2.x Release Plugin Issue Type: Bug

[jira] Commented: (MRELEASE-458) Branch Does Not Honor updateWorkingCopyVersions Setting

[ http://jira.codehaus.org/browse/MRELEASE-458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=182753#action_182753 ] James Carman commented on MRELEASE-458: --- I was using 2.0-beta-7: plugin

[jira] Commented: (MAVENUPLOAD-2040) rsync_ssh request for domdrides.sourceforge.net

[ http://jira.codehaus.org/browse/MAVENUPLOAD-2040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=135427#action_135427 ] James Carman commented on MAVENUPLOAD-2040: --- What is the normal turn-around time on

[jira] Commented: (MAVENUPLOAD-2040) rsync_ssh request for domdrides.sourceforge.net

[ http://jira.codehaus.org/browse/MAVENUPLOAD-2040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=133150#action_133150 ] James Carman commented on MAVENUPLOAD-2040: --- Proof that I own org.domdrides:

[jira] Created: (MAVENUPLOAD-2040) rsync_ssh request for domdrides.sourceforge.net

rsync_ssh request for domdrides.sourceforge.net --- Key: MAVENUPLOAD-2040 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2040 Project: maven-upload-requests Issue Type: Wish

[jira] Commented: (MPLUGIN-102) The 2.4 Release Breaks Previously-Working Builds

[ http://jira.codehaus.org/browse/MPLUGIN-102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_128141 ] James Carman commented on MPLUGIN-102: -- Because I followed the directions here when I created it:

[jira] Commented: (MPLUGIN-102) The 2.4 Release Breaks Previously-Working Builds

[ http://jira.codehaus.org/browse/MPLUGIN-102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_128157 ] James Carman commented on MPLUGIN-102: -- But, it's not a jar module. It's an archetype. It seems like there might be

[jira] Commented: (MPLUGIN-102) The 2.4 Release Breaks Previously-Working Builds

[ http://jira.codehaus.org/browse/MPLUGIN-102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_128168 ] James Carman commented on MPLUGIN-102: -- Ok, so the old documentation was wrong? That means that there are probably

[jira] Issue Comment Edited: (MPLUGIN-102) The 2.4 Release Breaks Previously-Working Builds

[ http://jira.codehaus.org/browse/MPLUGIN-102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_128168 ] jwcarman edited comment on MPLUGIN-102 at 3/21/08 11:00 AM: Ok, so the old documentation

[jira] Commented: (MPLUGIN-102) The 2.4 Release Breaks Previously-Working Builds

[ http://jira.codehaus.org/browse/MPLUGIN-102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_128215 ] James Carman commented on MPLUGIN-102: -- I like it! Thanks. The 2.4 Release Breaks Previously-Working Builds

[jira] Created: (MPLUGIN-102) The 2.4 Release Breaks Previously-Working Builds

The 2.4 Release Breaks Previously-Working Builds Key: MPLUGIN-102 URL: http://jira.codehaus.org/browse/MPLUGIN-102 Project: Maven 2.x Plugin Tools Issue Type: Bug Components: Plugin

[jira] Commented: (MENFORCER-25) Not actually possible to use the enforce-plugin-versions rule

[ http://jira.codehaus.org/browse/MENFORCER-25?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_127906 ] James Carman commented on MENFORCER-25: --- So, what if one of my rules is that I can't use snapshots? Not actually

[jira] Updated: (MPLUGIN-102) The 2.4 Release Breaks Previously-Working Builds

[ http://jira.codehaus.org/browse/MPLUGIN-102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Carman updated MPLUGIN-102: - Attachment: archetype-test.zip Here's an example project. The 2.4 Release Breaks Previously-Working

[jira] Commented: (MPLUGIN-102) The 2.4 Release Breaks Previously-Working Builds

[ http://jira.codehaus.org/browse/MPLUGIN-102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_127933 ] James Carman commented on MPLUGIN-102: -- By the way, the Tapestry folks also ran into this issue. Have a look:

[jira] Commented: (MPLUGIN-102) The 2.4 Release Breaks Previously-Working Builds

[ http://jira.codehaus.org/browse/MPLUGIN-102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_127932 ] James Carman commented on MPLUGIN-102: -- Yes, I'm currently in the process of locking down all versions of our

[jira] Updated: (MPLUGIN-102) The 2.4 Release Breaks Previously-Working Builds

[ http://jira.codehaus.org/browse/MPLUGIN-102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Carman updated MPLUGIN-102: - Attachment: debug.log The 2.4 Release Breaks Previously-Working Builds

[jira] Commented: (MENFORCER-14) Enforcer Plugin Messes Up Dependencies

[ http://jira.codehaus.org/browse/MENFORCER-14?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_103863 ] James Carman commented on MENFORCER-14: --- I would disagree that changing enforce-once to enforce is a fix. That is

[jira] Created: (MENFORCER-14) Enforcer Plugin Messes Up Dependencies

Enforcer Plugin Messes Up Dependencies -- Key: MENFORCER-14 URL: http://jira.codehaus.org/browse/MENFORCER-14 Project: Maven 2.x Enforcer Plugin Issue Type: Bug Reporter: James Carman

[jira] Issue Comment Edited: (MNG-3128) Enforcer Plugin Messes Up Dependencies

[ http://jira.codehaus.org/browse/MNG-3128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_103802 ] James Carman edited comment on MNG-3128 at 8/1/07 1:18 PM: --- I am moving this to the Maven Enforcer

[jira] Closed: (MNG-3128) Enforcer Plugin Messes Up Dependencies

[ http://jira.codehaus.org/browse/MNG-3128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Carman closed MNG-3128. - Resolution: Incomplete Enforcer Plugin Messes Up Dependencies --

[jira] Created: (MNG-3128) Enforcer Plugin Messes Up Dependencies

Enforcer Plugin Messes Up Dependencies -- Key: MNG-3128 URL: http://jira.codehaus.org/browse/MNG-3128 Project: Maven 2 Issue Type: Bug Components: Plugins and Lifecycle Affects Versions: