[jira] Updated: (MNG-3866) Plugin definitions from child and parent are not merged when version differs

[ http://jira.codehaus.org/browse/MNG-3866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann updated MNG-3866: --- Attachment: (was: plugin-model-container.patch) > Plugin definitions from child and parent are no

[jira] Updated: (MNG-3866) Plugin definitions from child and parent are not merged when version differs

[ http://jira.codehaus.org/browse/MNG-3866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann updated MNG-3866: --- Attachment: plugin-model-container.patch Proposed patch, using a dedicated PluginModelContainer. > P

[jira] Updated: (MNG-3866) Plugin definitions from child and parent are not merged when version differs

[ http://jira.codehaus.org/browse/MNG-3866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann updated MNG-3866: --- Attachment: plugin-model-container.patch > Plugin definitions from child and parent are not merged wh

[jira] Commented: (MNG-3871) war-dependency is not resolved from a remote repository

[ http://jira.codehaus.org/browse/MNG-3871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=155849#action_155849 ] Robert Scholte commented on MNG-3871: - For those interested: this issue was first addressed by me t

[jira] Commented: (MNG-3814) Reactor builds fail due to erroneous cycle in project sorting which does not consider versions

[ http://jira.codehaus.org/browse/MNG-3814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=155844#action_155844 ] Régis Décamps commented on MNG-3814: The problem occurs with any type of dependency. It can be a pl

[jira] Updated: (MNG-3380) MavenMetadataSource retrieves ResolutionGroup without consulting ManagedVersionMap, is problem when relocation

[ http://jira.codehaus.org/browse/MNG-3380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann updated MNG-3380: --- Description: Consider the following scenario: {code:xml} 4.0.0 root-groupId root-artifactId

[jira] Commented: (MAVENUPLOAD-2286) nez sync rule from sourceforge project

[ http://jira.codehaus.org/browse/MAVENUPLOAD-2286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=155811#action_155811 ] Christophe Lallement commented on MAVENUPLOAD-2286: --- maybe there is an error

[jira] Created: (MAVENUPLOAD-2287) New opensource library (swing) to sync with central repository: JBusyComponent

New opensource library (swing) to sync with central repository: JBusyComponent -- Key: MAVENUPLOAD-2287 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2287 Project: Maven Up

[jira] Created: (MAVENUPLOAD-2286) nez sync rule from sourceforge project

nez sync rule from sourceforge project -- Key: MAVENUPLOAD-2286 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2286 Project: Maven Upload Requests Issue Type: Wish Reporter: Christophe Lallem

[jira] Created: (MNG-3877) Reporting output directory not basedir aligned when queried from MavenProject

Reporting output directory not basedir aligned when queried from MavenProject - Key: MNG-3877 URL: http://jira.codehaus.org/browse/MNG-3877 Project: Maven 2 Issue Ty