You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@ant.apache.org by "Phil Clay (JIRA)" <ji...@apache.org> on 2010/05/11 16:47:42 UTC
[jira] Created: (IVY-1191) Allow configuration exclusion for
resolve/retrieve/publish/etc
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.
[jira] Commented: (IVY-1191) Allow configuration exclusion for
resolve/retrieve/publish/etc
Posted by "Phil Clay (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IVY-1191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12866570#action_12866570 ]
Phil Clay commented on IVY-1191:
--------------------------------
I take it back. I'm seeing some weird behavior when using '!'
The delivered ivy.xml file is correct (i.e. the negated confs are not present).
However, the actual artifacts for the included confs are not being published.
When I get some time, I'll try to isolate the problem and a scenario to test.
> 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.
[jira] Issue Comment Edited: (IVY-1191) Allow configuration
exclusion for resolve/retrieve/publish/etc
Posted by "Phil Clay (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IVY-1191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12866570#action_12866570 ]
Phil Clay edited comment on IVY-1191 at 5/12/10 9:58 AM:
---------------------------------------------------------
I take it back. I'm seeing some weird behavior when using '!'
The delivered ivy.xml file is correct (i.e. the negated confs are not present).
However, the actual artifacts for the included confs are not being published (I'm testing the publish task).
When I get some time, I'll try to isolate the problem and a scenario to test.
was (Author: philsttr):
I take it back. I'm seeing some weird behavior when using '!'
The delivered ivy.xml file is correct (i.e. the negated confs are not present).
However, the actual artifacts for the included confs are not being published.
When I get some time, I'll try to isolate the problem and a scenario to test.
> 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.
[jira] Commented: (IVY-1191) Allow configuration exclusion for
resolve/retrieve/publish/etc
Posted by "Phil Clay (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IVY-1191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12866220#action_12866220 ]
Phil Clay commented on IVY-1191:
--------------------------------
Woo hoo! '!' works.
I couldn't find where this is documented. So, I guess this bug just becomes a request to update the documentation.
If I find any problems with '!', I'll open a new bug.
Thanks.
> 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.
[jira] Commented: (IVY-1191) Allow configuration exclusion for
resolve/retrieve/publish/etc
Posted by "Maarten Coene (JIRA)" <ji...@apache.org>.
[ 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.