[
https://issues.apache.org/jira/browse/IVY-1191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12866173#action_12866173
]
Maarten Coene commented on IVY-1191:
------------------------------------
Could you try with '!' instead of '-'?
It might work, but I cannot test it at the moment...
> Allow configuration exclusion for resolve/retrieve/publish/etc
> --------------------------------------------------------------
>
> Key: IVY-1191
> URL: https://issues.apache.org/jira/browse/IVY-1191
> Project: Ivy
> Issue Type: New Feature
> Affects Versions: 2.1.0
> Reporter: Phil Clay
> Priority: Minor
>
> For specifying confs for resolve/retrieve/publish, you can either
> * explicitly specify confs (e.g. "build,deploy,test"), or
> * specify all (e.g. "*"), or
> * specify all public (e.g. "*(public)"), or
> * specify all private (e.g. "*(private)")
> All of these work on the principle of inclusion. i.e. only include those
> configurations I have specified.
> I would like the ability to select confs based on exclusion. i.e. Include
> everything, except the ones I have explicitly stated.
> The reason is that our build process, by default, builds a LOT of stuff. Our
> developers have the options of turning off certain things to make the builds
> faster. (For example, our build publishes instrumented artifacts for
> gathering code coverage data during qa cycles. It would be nice to be able
> to turn off the "instrumented" conf without having to know how to turn on
> everything but the "instrumented" conf)
> I'll propose one option. (There are probably several ways to do this...)
> In the conf string, use the - character to indicate exclusion. For example:
> * conf="*,-instrumented" would include everything except the instrumented
> conf
> * conf="*(public),-instrumented" would include all public confs except the
> instrumented conf
> * conf="build,deploy,test,instrumented,-instrumented" would only include
> build, deploy, test. I'd like this case to be handled, so we can have a
> default inclusion string (which may include everything "*", or be a specific
> list of inclusions "build,deploy,test,instrumented"), but also be able to
> negate certain confs simply by concatinating an exclusion string
> "-instrumented".
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
