Matt is correct: you are mixing Eclipse and Ant definitions.
So here some points by me:
* There is no default behaviour of . You have to specify the paths the
compiler should use by yourself.
* means, that the file or directory
".classpath" should be used for classpath. But the .classpath-file i
Hi Matt,
Thanks for that information. Since this used to work I guess somewhere
along the line I must have deleted that classpath info. I will give this
a try. In the mean time does this mean I don't need the zipfileset
elements if I include those jars in the path element? Or do I still need
both
Hi Jan,
Thanks. Things are starting to come together in my head. If I
understand, ant doesn't need the Eclipse .classpath at all and only the
classpath suggested by Matt is used by ant, right?
On 2/18/2019 8:11 AM, Jan Matèrne (jhm) wrote:
> Matt is correct: you are mixing Eclipse and Ant definit
Hi Matt and Jan,
Thanks to both of you as I am closer but I think I am still missing a
piece. I am now getting a successful build but the resulting jar is not
finding the classes in the external jars. When I run the jar I get this
exception:
Exception in thread "main" java.lang.NoClassDefFoun
Yes.
Eclipse uses .project and .classpath.
Ant uses build.xml (and an often used file build.properties).
In contrast to Maven or Gradle Ant doesn't come with a built in dependency
manager.
So just declaring "I need JUnit 4.12" doesn't work.
- place the jars by yourself in a directory (e.g. "/libs
Hi Dennis,
I think you are almost there to get this working. How are you running
this Java application? Are you using Ant's java task? What does it look
like? Just like you did with javac, the java task will need to know what
classpath to use while running the application. As long as you setup
you
