[jira] [Commented] (MENFORCER-211) wildcard ignore in requireReleaseDeps
[
https://issues.apache.org/jira/browse/MENFORCER-211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15374190#comment-15374190
]
Dariusz Kordonski commented on MENFORCER-211:
-
I can confirm that wildcards mixed with strings don't seem to work. Pure
wildcards as reported in this issue work for us however. E.g. both excludes
below will work (exact match, pure wildcard):
{code}
com.atlassian.plugins:atlassian-plugins-core
{code}
{code}
com.atlassian.plugins:*
{code}
But the following will not be detected (mixed string and wildcards), despite
being documented as a valid exclusion pattern:
{code}
com.atlassian.plugins:atlassian-plugins-*
{code}
We are using version 1.4.0
> wildcard ignore in requireReleaseDeps
> -
>
> Key: MENFORCER-211
> URL: https://issues.apache.org/jira/browse/MENFORCER-211
> Project: Maven Enforcer Plugin
> Issue Type: Improvement
>Affects Versions: 1.3.1
>Reporter: Arne Brix
>Priority: Minor
> Fix For: waiting-for-feedback
>
>
> the bannedDependencies rule allows one to specify artifact lists using
> wildcards:
> {code:xml}
> org.apache.*:maven-*:*
> {code}
> we are using the requireReleaseDeps rule for our release builds.
> We would like to exclude dependencies with scope test because they don't
> contribute to the final artifact.
> We tried the syntax documented for bannedDependencies, but it didn't work:
> {code:xml}
>
>
>
> No Snapshots Allowed!
> true
>
> *:*:*:*:test
>
>
>
> true
>
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MENFORCER-211) wildcard ignore in requireReleaseDeps
[
https://issues.apache.org/jira/browse/MENFORCER-211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15374196#comment-15374196
]
Dariusz Kordonski commented on MENFORCER-211:
-
Actually disregard my comment, our case is {{bannedDependencies}} rule, which
is different. I'll raise a separate bug.
> wildcard ignore in requireReleaseDeps
> -
>
> Key: MENFORCER-211
> URL: https://issues.apache.org/jira/browse/MENFORCER-211
> Project: Maven Enforcer Plugin
> Issue Type: Improvement
>Affects Versions: 1.3.1
>Reporter: Arne Brix
>Priority: Minor
> Fix For: waiting-for-feedback
>
>
> the bannedDependencies rule allows one to specify artifact lists using
> wildcards:
> {code:xml}
> org.apache.*:maven-*:*
> {code}
> we are using the requireReleaseDeps rule for our release builds.
> We would like to exclude dependencies with scope test because they don't
> contribute to the final artifact.
> We tried the syntax documented for bannedDependencies, but it didn't work:
> {code:xml}
>
>
>
> No Snapshots Allowed!
> true
>
> *:*:*:*:test
>
>
>
> true
>
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (MENFORCER-256) BannedDependencies does not work with wildcard strings
Dariusz Kordonski created MENFORCER-256:
---
Summary: BannedDependencies does not work with wildcard strings
Key: MENFORCER-256
URL: https://issues.apache.org/jira/browse/MENFORCER-256
Project: Maven Enforcer Plugin
Issue Type: Bug
Affects Versions: 1.4
Reporter: Dariusz Kordonski
Wildcards mixed with strings don't seem to work with BannedDependencies,
despite being documented as a valid exclusion pattern here:
http://maven.apache.org/enforcer/enforcer-rules/bannedDependencies.html.
Pure wildcards (for the entire component) seem to work, though. E.g. both
excludes below will work (exact match, pure wildcard):
{code}
com.atlassian.plugins:atlassian-plugins-core
{code}
{code}
com.atlassian.plugins:*
{code}
But the following will not be detected (mixed string and wildcards), despite
being documented as a valid exclusion pattern:
{code}
com.atlassian.plugins:atlassian-plugins-*
{code}
We are using version 1.4.0
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
