[jira] (MENFORCER-211) wildcard ignore in requireReleaseDeps

[ https://jira.codehaus.org/browse/MENFORCER-211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arne Brix updated MENFORCER-211: Description: the bannedDependencies rule allows one to specify artifact lists using wildcards: {code

[jira] (MENFORCER-211) wildcard ignore in requireReleaseDeps

[ https://jira.codehaus.org/browse/MENFORCER-211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arne Brix updated MENFORCER-211: Description: the bannedDependencies rule allows one to specify artifact lists using wildcards: org.a

[jira] (MENFORCER-211) wildcard ignore in requireReleaseDeps

Arne Brix created MENFORCER-211: --- Summary: wildcard ignore in requireReleaseDeps Key: MENFORCER-211 URL: https://jira.codehaus.org/browse/MENFORCER-211 Project: Maven Enforcer Plugin Issue Type

[jira] (MDEPLOY-131) use default repository when no url specified

[ https://jira.codehaus.org/browse/MDEPLOY-131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=354701#comment-354701 ] Arne Brix commented on MDEPLOY-131: --- I have a similar usecase. We use the replacer plugin to mod

[jira] (MDEP-374) dependency:tree -Dverbose isn't verbose anymore

Arne Brix created MDEP-374: -- Summary: dependency:tree -Dverbose isn't verbose anymore Key: MDEP-374 URL: https://jira.codehaus.org/browse/MDEP-374 Project: Maven 2.x Dependency Plugin Issue Type: Bu