[jira] Updated: (IVY-557) Remove dependency on commons-cli

["Tjeerd Verhagen (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/IVY-557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tjeerd Verhagen updated IVY-557:
--------------------------------

    Attachment: patch_build.xml_add_main_and_path_20070708.txt

There is another way to solve the dependecies problem of a 'main' jar depending on other jars. Through the MANIFEST.MF, in which the (main) key 'Class-Path' can be specified. The value of this key should hold the path's to the other needed jars. For Ivy this means, it can reference to the 'commons-cli.jar' (and maybe other / extra jars in the future).

In addition to this I also added the key 'Main-Class', which makes it possible to just 'run the jar', as:
java -jar ivy-core.jar
No additioinal path to the class 'org.apache.ivy.Main' is needed any longer.


To read more about these keys, see paragraph 'Main Attributes':
http://java.sun.com/j2se/1.4.2/docs/guide/jar/jar.html
http://java.sun.com/j2se/1.4.2/docs/guide/jar/jar.html#Main%20Attributes


> Remove dependency on commons-cli
> --------------------------------
>
>                 Key: IVY-557
>                 URL: https://issues.apache.org/jira/browse/IVY-557
>             Project: Ivy
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Xavier Hanin
>            Priority: Minor
>         Attachments: patch_build.xml_add_main_and_path_20070708.txt
>
>
> ATM to launch Ivy on the command line there is a mandatory dependency on commons-cli. This makes it much less easy to use Ivy command line (a simple java -jar would be enough without this dependency). Therefore removing this dependency by parsing args manually would help using the Ivy CLI more easily and more frequently.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.