On 7/9/07, Tjeerd Verhagen <[EMAIL PROTECTED]> wrote:
> > > > I would go > > for the sollution that goes the internal / alternative way, only if the > > commons-cli package can't be found (in that case just drop the previous > > System.err as a warning). > > > Mmm, if we can work without commons cli, I don't think I'll preserve the > commons cli parsing. It would be twice as much code to maintain when you > change CLI options. > Mmmm, maybe there is a smart way to feed the commons-cli and the internal sulotion with the same data....
But commons cli is only used for parsing data, so I think trying to preserve both would be over complex. * <https://issues.apache.org/jira/browse/IVY-566>*Created a new Jira issue
(improvement): IVY-566 Check for package depencencies, before starting the stand alone ivy It contains a patch. for checking external dependencies (commons-cli) when starting Ivy as standalone application.
Great! I'll check that tomorrow. Should I also move / add the other path to this issue (The one that adds
Class-Path and Main-Class to the jar Manifest)?
I think the Manifest patch should go to yet another issue. Something like "update MANIFEST to make Ivy runnable with java -jar". Xavier -- Xavier Hanin - Independent Java Consultant http://xhab.blogspot.com/ http://incubator.apache.org/ivy/ http://www.xoocode.org/
