ant-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Xavier Hanin (JIRA)" <>
Subject [jira] Resolved: (IVY-757) Make Ivy standalone runnable with no depedencies
Date Fri, 29 Feb 2008 16:46:51 GMT


Xavier Hanin resolved IVY-757.

    Resolution: Fixed

I've rewritten the command line parsing classes, adapted to our own usage only. Thus this
removes the dependency on commons-cli, and I was even able to make some improvements, like
grouping options by category to make the help easier to read.

Here is how the help now looks like:
usage: ivy
==== settings options
 -settings <settingsfile>     use given file for settings
 -cache <cachedir>            use given directory for cache
 -novalidate                  do not validate ivy files against xsd
 -m2compatible                use maven2 compatibility

==== resolve options
 -ivy <ivyfile>               use given file as ivy file
 -dependency <organisation> <module> <revision> use this instead of ivy
file to 
                              do the rest of the work with this as a dependency.
 -confs <configurations>      resolve given configurations

==== retrieve options
 -retrieve <retrievepattern>  use given pattern as retrieve pattern
 -sync                        in conjonction with -retrieve, does a synced retri

==== cache path options
 -cachepath <cachepathfile>   outputs a classpath consisting of all dependencies
                               in cache (including transitive ones) of the given
                               ivy file to the given cachepathfile

==== deliver options
 -deliverto <ivypattern>      use given pattern as resolved ivy file pattern

==== publish options
 -publish <resolvername>      use given resolver to publish to
 -publishpattern <artpattern> use given pattern to find artifacts to publish
 -revision <revision>         use given revision to publish the module
 -status <status>             use given status to publish the module

==== http auth options
 -realm <realm>               use given realm for HTTP AUTH
 -host <host>                 use given host for HTTP AUTH
 -username <username>         use given username for HTTP AUTH
 -passwd <passwd>             use given password for HTTP AUTH

==== launcher options
 -main <main>                 the FQCN of the main class to launch
 -args <ars>                  the arguments to runtime process
 -cp <cp>                     extra classpath, used only in combination with opt
                              ion main

==== message options
 -debug                       set message level to debug
 -verbose                     set message level to verbose
 -warn                        set message level to warn
 -error                       set message level to error

==== help options
 -?                           display this help
 -deprecated                  show deprecated options

When this was discussed in the mailing lists last time, it wasn't clear if everybody was ok
with these changes. So if you think it will add too much maintenance headaches or see any
other problem with this change I'm fine with discussing it further. 

But I really like how easy it is now to use Ivy in standalone mode. We could even think about
providing a small wrapper to be able to run "ivy" on the command line rather than "java -jar

> Make Ivy standalone runnable with no depedencies
> ------------------------------------------------
>                 Key: IVY-757
>                 URL:
>             Project: Ivy
>          Issue Type: Improvement
>            Reporter: Xavier Hanin
>            Assignee: Xavier Hanin
>             Fix For: 2.0-RC1
> We have discussed this several times, and I really think removing the dependency on commons-cli
would help use Ivy in standalone mode. It would also improve its ease of use as an application
> See also IVY-567.

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

View raw message