> From: Stefan Bodewig [mailto:[EMAIL PROTECTED] > > > From: Conor MacNeill <[EMAIL PROTECTED]> > > We could add back optional.jar as a manifest-only class-path jar to > > collect all the other optional jars together. > > OK.
I thought of that too, even started writing it too, but it would not have worked in my particular case, since that classpath was used both for compiling and running, and Javac ignores the Class-Path: entry of the Manifest... > > This could be provided in lib or even a "legacy" dir for those who > > want to use it. > > I'd rather move it to a separate dir so that people have to move it > knowing what they do instead of picking it up by surprise. If backward-compatibility is concerned, it should live in ant/lib, and be called optional.jar... With the Javac-related-uses caveat I have above, which could be documented. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
