Craig M. Brandenburg created IVY-1500:
-----------------------------------------

             Summary: Command-line Ivy '-confs' option doesn't accept 
comma-separated list of configurations
                 Key: IVY-1500
                 URL: https://issues.apache.org/jira/browse/IVY-1500
             Project: Ivy
          Issue Type: Bug
    Affects Versions: 2.4.0-RC1, 2.3.0
            Reporter: Craig M. Brandenburg


When using Ivy from the command line (by running {{java}} and passing in the 
Ivy jar through the {{-jar}} option), the {{-confs}} option doesn't accept a 
comma-separated list of configurations. Whereas, when using Ant, the 
{{<resolve>}} task attribute {{"conf"}} accepts a comma-separated list of 
configurations.

Here's the error when running from the command line.
{code}
$ java -DREPO_DIR=/home/cbrandenburg/art/research/ivy-tool/repo -jar 
/home/cbrandenburg/art/research/ivy-tool/ivy-2.4.0-rc1.jar -settings 
/home/cbrandenburg/art/research/ivy-tool/ivysettings.xml -confs foo,bar 
-retrieve art/[artifact]-[revision].[ext]

:: loading settings :: file = 
/home/cbrandenburg/art/research/ivy-tool/ivysettings.xml
:: resolving dependencies :: AgJunction#banana;working@antimony
        confs: [foo,bar]

:: problems summary ::
:::: ERRORS
        requested configuration not found in 
AgJunction#banana;working@antimony: [ 'foo,bar' ]


:: USE VERBOSE OR DEBUG MESSAGE LEVEL FOR MORE DETAILS
Exception in thread "main" java.lang.IllegalArgumentException: requested 
configuration not found in AgJunction#banana;working@antimony: [ 'foo,bar' ]
        at 
org.apache.ivy.core.resolve.ResolveEngine.getDependencies(ResolveEngine.java:556)
        at 
org.apache.ivy.core.resolve.ResolveEngine.resolve(ResolveEngine.java:236)
        at 
org.apache.ivy.core.resolve.ResolveEngine.resolve(ResolveEngine.java:197)
        at org.apache.ivy.Ivy.resolve(Ivy.java:508)
        at org.apache.ivy.Main.run(Main.java:311)
        at org.apache.ivy.Main.main(Main.java:219)

{code}

Individually resolving either configuration ({{foo}} or {{bar}}) works fine.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to