[jira] Closed: (MSITE-460) error when using Maven 3.x with maven-site-plugin 3.x

[ http://jira.codehaus.org/browse/MSITE-460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy closed MSITE-460. -- Resolution: Fixed Fix Version/s: 3.0-alpha-1 fix [rev 905460|http://svn.apache.org/viewvc?rev=905460&vi

[jira] Moved: (MSITE-460) error when using Maven 3.x with maven-site-plugin 3.x

[ http://jira.codehaus.org/browse/MSITE-460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy moved MPLUGIN-167 to MSITE-460: Affects Version/s: (was: 2.5.1) 3.0-alpha-1

[jira] Commented: (SCM-530) Add support for git submodules to git SCM provider

[ http://jira.codehaus.org/browse/SCM-530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=208839#action_208839 ] Chas Emerick commented on SCM-530: -- FYI, Hudson's [git plugin|http://wiki.hudson-ci.org/display/HUDSON/

[jira] Created: (SCM-530) Add support for git submodules to git SCM provider

Add support for git submodules to git SCM provider -- Key: SCM-530 URL: http://jira.codehaus.org/browse/SCM-530 Project: Maven SCM Issue Type: New Feature Components: maven-scm-provid

[jira] Closed: (MNG-4554) [regression] plugin updates are requested on every build regardless of policies

[ http://jira.codehaus.org/browse/MNG-4554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann closed MNG-4554. -- Resolution: Fixed Assignee: Benjamin Bentmann Fixed in [r905424|http://svn.apache.org/viewvc?view

[jira] Commented: (MRELEASE-517) Release should have parameters to update the parent pom and then resolve dependencies appropriately

[ http://jira.codehaus.org/browse/MRELEASE-517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=208826#action_208826 ] Wendy Smoak commented on MRELEASE-517: -- You could try using the scm plugin to commit the chang

[jira] Created: (MRELEASE-517) Release should have parameters to update the parent pom and then resolve dependencies appropriately

Release should have parameters to update the parent pom and then resolve dependencies appropriately --- Key: MRELEASE-517 URL: http://jira.codehaus.org/browse/MRELEASE

[jira] Issue Comment Edited: (MNG-3139) The skin does not exist: Unable to determine the release version

[ http://jira.codehaus.org/browse/MNG-3139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=208823#action_208823 ] Thomas J. Harris edited comment on MNG-3139 at 2/1/10 11:59 AM: This de

[jira] Issue Comment Edited: (MNG-3139) The skin does not exist: Unable to determine the release version

[ http://jira.codehaus.org/browse/MNG-3139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=208823#action_208823 ] Thomas J. Harris edited comment on MNG-3139 at 2/1/10 11:58 AM: This de

[jira] Issue Comment Edited: (MNG-3139) The skin does not exist: Unable to determine the release version

[ http://jira.codehaus.org/browse/MNG-3139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=208823#action_208823 ] Thomas J. Harris edited comment on MNG-3139 at 2/1/10 11:50 AM: This de

[jira] Commented: (MNG-3139) The skin does not exist: Unable to determine the release version

[ http://jira.codehaus.org/browse/MNG-3139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=208823#action_208823 ] Thomas J. Harris commented on MNG-3139: --- This defect is occurring again as of February 1st, 2010.

[jira] Issue Comment Edited: (MRELEASE-514) release:branch hit remoteTagging problem

[ http://jira.codehaus.org/browse/MRELEASE-514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=208822#action_208822 ] werner mueller edited comment on MRELEASE-514 at 2/1/10 11:39 AM: --

[jira] Commented: (MRELEASE-514) release:branch hit remoteTagging problem

[ http://jira.codehaus.org/browse/MRELEASE-514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=208822#action_208822 ] werner mueller commented on MRELEASE-514: - a similar issue was solved in MRELEASE-427 since

[jira] Commented: (MRELEASE-427) Add a mojo parameter for using the new remote tagging for svn scm provider (to prevent issue with svn > 1.5.0)

[ http://jira.codehaus.org/browse/MRELEASE-427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=208821#action_208821 ] werner mueller commented on MRELEASE-427: - an issue related to branching was created: MRELE

[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-tabpanel&focusedCommentId=208814#action_208814 ] Peter Janes commented on MRELEASE-458: -- updateWorkingCopyVersions=false appears to work again

[jira] Commented: (MNG-2199) Version ranges not supported for parent artifacts

[ http://jira.codehaus.org/browse/MNG-2199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=208812#action_208812 ] Joost den Boer commented on MNG-2199: - Don't agree with Todor. Using relative path is not a solutio

[jira] Closed: (MPDF-38) Allow selective report inclusion

[ http://jira.codehaus.org/browse/MPDF-38?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lukas Theussl closed MPDF-38. - Resolution: Not A Bug Assignee: Lukas Theussl Inclusion of reports is configured just like for the site plug

[jira] Commented: (WAGON-297) Wagon SCM does not automatically create missing directories during deployment

[ http://jira.codehaus.org/browse/WAGON-297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=208796#action_208796 ] Maria Odea Ching commented on WAGON-297: {quote} * the multiple levels of try/catch is a bit s

[jira] Created: (MASSEMBLY-468) Sharing assembly descriptor across sub modules does not work if parent defines assembly and submodule want to add own assembly

Sharing assembly descriptor across sub modules does not work if parent defines assembly and submodule want to add own assembly -- Key: MASSEMBLY-468

[jira] Updated: (MASSEMBLY-467) Sharing assembly descriptor across sub modules does not work if invoked from parent project - bad resolve of the classpath

[ http://jira.codehaus.org/browse/MASSEMBLY-467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann updated MASSEMBLY-467: Fix Version/s: (was: 2.2-beta-6) Could be another occurrence of MNG-1323. > Shari

[jira] Created: (MANTTASKS-173) Value of project.build.finalName is not resolved

Value of project.build.finalName is not resolved Key: MANTTASKS-173 URL: http://jira.codehaus.org/browse/MANTTASKS-173 Project: Maven 2.x Ant Tasks Issue Type: Bug Components: pom ta

[jira] Closed: (MASSEMBLY-467) Sharing assembly descriptor across sub modules does not work if invoked from parent project - bad resolve of the classpath

[ http://jira.codehaus.org/browse/MASSEMBLY-467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kek closed MASSEMBLY-467. - Resolution: Cannot Reproduce Fix Version/s: 2.2-beta-6 The problem is on other place, so I close this bug and

[jira] Closed: (MAVENUPLOAD-2714) lambico artifacts upload

[ http://jira.codehaus.org/browse/MAVENUPLOAD-2714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juven Xu closed MAVENUPLOAD-2714. - Resolution: Fixed > lambico artifacts upload > > > Key:

[jira] Commented: (MAVENUPLOAD-2714) lambico artifacts upload

[ http://jira.codehaus.org/browse/MAVENUPLOAD-2714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=208771#action_208771 ] Lucio Benfante commented on MAVENUPLOAD-2714: - I opened a new issue on the Sonatype