[jira] Commented: (MDEP-106) Unpacking primary artifact from sibling module uses repository rather than reactor

[ https://jira.codehaus.org/browse/MDEP-106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=273301#comment-273301 ] Matt Ryall commented on MDEP-106: - Thanks for the update, Stephen. Unpacking primary artifact from

[jira] Commented: (MDEP-106) Unpacking primary artifact from sibling module uses repository rather than reactor

[ http://jira.codehaus.org/browse/MDEP-106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=223878#action_223878 ] Samuel Le Berrigaud commented on MDEP-106: -- If you want to unpack dependencies that are in the

[jira] Commented: (MDEP-106) Unpacking primary artifact from sibling module uses repository rather than reactor

[ http://jira.codehaus.org/browse/MDEP-106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=223701#action_223701 ] Dennis Lundberg commented on MDEP-106: -- As mentioned in MNG-2877, this doesn't seem to be a bug in

[jira] Commented: (MDEP-106) Unpacking primary artifact from sibling module uses repository rather than reactor

[ http://jira.codehaus.org/browse/MDEP-106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=223853#action_223853 ] Brian Fox commented on MDEP-106: It conceivably could be fixed in the plugin to check the reactor, but