Manifest Class-Path is always taken into account Steve. Yes, I prefer just the warning. --DD
On 7/7/06, Steve Loughran <[EMAIL PROTECTED]> wrote:
[EMAIL PROTECTED] wrote: >> Bug: 39153 >> Add notes (log+manual) that <java> does not handle >> jar+classpath together (more exactly Java itself does not). > > > On the other hand we could convert the jar-attribute to a path element, > so > <java jar="one.jar" fork="true"> > <classpath> > <pathelement path="two.jar"/> > </classpath> > </java> > > becomes to > <java mainclass="---" fork="true"> > <classpath> > <pathelement path="one.jar"/> > <pathelement path="two.jar"/> > </classpath> > </java> > > Unless they also want the manifest classloader stuff, of course. How about having <java> itself warn users? --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
