For now, I added "classpath" as a valid option (committed), so you can give it a try.
On Mon, Oct 13, 2008 at 12:28 PM, Stefano Kismet Lenzi <[EMAIL PROTECTED]> wrote: > On Mon, Oct 13, 2008 at 11:15, Stuart McCulloch <[EMAIL PROTECTED]> wrote: >> 2008/10/13 Alin Dreghiciu <[EMAIL PROTECTED]> >>> >>> I will have to revert your patch. > > I also found out that my patch was avoiding the vmo option to be parsed. > >>> Actually the problem is that the the option is "classPath" not >>> "classpath" (capital P). >>> Now we can argue that is not very intuitive and error prone, fact that I >>> agree. >>> So, if you change the option to "classPath" it should work. >>> Alternatively you can use the other shortcut witch is similar to >>> classPath named "cp". >>> >>> So guys, what do you say: shall I change the --classPath option to >>> classpath? I guess it will eliminate future problems like this and is >>> less confusing. The only downside I see that some people already uses >>> that. >>> Actually a simpler solution is to use both -classpath and --classPath. >> >> +1 for classpath and classPath as I didn't spot that either... >> actually, perhaps make argument names case-insensitive? > > +1 for case insensitive on all args if it is applied. > > _______________________________________________ > general mailing list > general@lists.ops4j.org > http://lists.ops4j.org/mailman/listinfo/general > -- Alin Dreghiciu http://www.ops4j.org - New Energy for OSS Communities - Open Participation Software. http://www.qi4j.org - New Energy for Java - Domain Driven Development. http://malaysia.jayway.net - New Energy for Projects - Great People working on Great Projects at Great Places _______________________________________________ general mailing list general@lists.ops4j.org http://lists.ops4j.org/mailman/listinfo/general
