Conor,
Thanks for the explanation, it makes perfect sense. I was pretty sure
there was a good reason to have the jars separated, but didn't pick up
on the classloader issue.
Dale
Conor MacNeill wrote:
On Tue, 30 Sep 2003 05:04 am, Dale Anson wrote:
I don't claim to understand the details of w
On Tue, 30 Sep 2003 05:10 am, Alexey N. Solofnenko wrote:
> Would not it be easier to provide something like antall.jar that
> includes all ANT jars in its manifest's classpath? It would solve my
> problems with ANT classloader.
>
No. It would only work if that manifest classpath included all the
On Tue, 30 Sep 2003 05:04 am, Dale Anson wrote:
> I don't claim to understand the details of what ant-launcher is supposed
> to do,
ant-launcher is supposed to setup an appropriate classloader hierarchy to
launch ant. In particular it is the minimal set of classes is required to be
on the class
Would not it be easier to provide something like antall.jar that
includes all ANT jars in its manifest's classpath? It would solve my
problems with ANT classloader.
- Alexey.
Steve Loughran wrote:
Dale Anson wrote:
It looks like either optional.jar or ant-launcher.jar are required in
addition t
[mailto:[EMAIL PROTECTED]
Gesendet: Montag, 29. September 2003 21:04
An: Ant Developers List
Betreff: Re: All those jars...!
I don't claim to understand the details of what ant-launcher is supposed
to do, but if I do:
cd ${ant.home}/lib
jar xf ant.jar
jar xf ant-launcher.jar
rm ant.ja
I don't claim to understand the details of what ant-launcher is supposed
to do, but if I do:
cd ${ant.home}/lib
jar xf ant.jar
jar xf ant-launcher.jar
rm ant.jar ant-launcher.jar
jar cfm ant.jar META-INF/MANIFEST.MF META-INF/LICENSE.txt images/ org/
rm -rf META-INF/ images/ org/
java -jar ant.jar
Dale Anson wrote:
It looks like either optional.jar or ant-launcher.jar are required in
addition to ant.jar, see below. It might be nice to put the classes from
ant-launcher.jar into ant.jar.
not possible, because the role of ant-launcher is to set up the
classpath to load ant.jar and the other
It looks like either optional.jar or ant-launcher.jar are required in
addition to ant.jar, see below. It might be nice to put the classes from
ant-launcher.jar into ant.jar.
cd ${ant.home}/lib
java -classpath ant.jar org.apache.tools.ant.Main
Exception in thread "main" java.lang.NoClassDefFoundE
On Mon, 29 Sep 2003 10:27 am, Dale Anson wrote:
> Woops -- never mind. If I get ant.jar and optional.jar from the same
> distribution in the path, the rest are optional, as they should be.
>
optional.jar is going away IIRC.
Conor
-
Woops -- never mind. If I get ant.jar and optional.jar from the same
distribution in the path, the rest are optional, as they should be.
Dale Anson wrote:
> I downloaded the binary Ant 1.6 alpha, from the 9/9/2003 nightly build.
> The 'lib' directory has 30+ jars. I regularly use Ant from within
I downloaded the binary Ant 1.6 alpha, from the 9/9/2003 nightly build.
The 'lib' directory has 30+ jars. I regularly use Ant from within jEdit.
Typically, I put a couple of soft link in my ${user.home}/.jedit/jars to
ant.jar and optional.jar, or on Windows, I copy ant.jar and optional.jar
into the
11 matches
Mail list logo