[
https://issues.apache.org/jira/browse/IVY-290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17906793#comment-17906793
]
Johan Corveleyn commented on IVY-290:
-------------------------------------
I second this feature request. I would find it very useful to be able to
restrict the buildlist target to a particular configuration.
We have worked around this limitation before in a similar situation as the
reporter of this issue (wanting to restrict the buildlist to "build" confs,
omitting "runtime" confs) by filtering them afterwards. But we have now run
into this problem again in a more difficult scenario:
* App A and B both depend on module M.
* App A is still on Java 8, while B has been migrated to Java 11. So we want to
compile A with javac 8 and B with javac 11.
* Module M depends on a module that has two variants: one for Java 8 (let's
call this module N-8) and one for Java 11 (let's call this module N-11).
* In the ivy.xml of M we "separate" the dependency on N with configurations (in
the "java11plus" configuration it picks up N-11).
* When building an App, our generic buildscripts start with a ivy:buildlist of
the main module. For A we'd like the buildlist to contain N-8, for B we'd like
it to contain N-11.
In this scenario, it would be great if we could pass an attribute "conf=X" to
ivy:buildlist, so we can have it return only the modules that follow that
configuration. Or perhaps it should be a multivalued field (conf=X,Y).
> Restriction for configuration to use in build order resolve in buildlist
> target
> -------------------------------------------------------------------------------
>
> Key: IVY-290
> URL: https://issues.apache.org/jira/browse/IVY-290
> Project: Ivy
> Issue Type: Improvement
> Components: Core
> Affects Versions: 1.4-RC1
> Reporter: Petri Rautakoski
> Priority: Major
>
> I have used build and runtime confs in ivy.xml files to separate
> dependencies. When I use buildlist target of IVY to resolve buid order I
> think it uses every dependency found from ivy.xml files. When I created other
> buildivy.xml file with only build time dependencies there and used
> buildivy.xml in ivyfilepath of buildlist target I was able to build all
> modules in right order.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
