;
>
>
> Jan
>
>
>
> Von: Dennis Putnam [mailto:d...@bellsouth.net]
> Gesendet: Donnerstag, 28. Februar 2019 10:53
> An: user@ant.apache.org
> Betreff: AW: Javac Run By Ant Script is Unable to Find External Jars
>
>
>
> I've figured out what the problem
...@bellsouth.net]
Gesendet: Donnerstag, 28. Februar 2019 10:53
An: user@ant.apache.org
Betreff: AW: Javac Run By Ant Script is Unable to Find External Jars
I've figured out what the problem is but I don't know what to do to fix it.
When I export the jar from Eclipse, it has this set of d
I've figured out what the problem is but I don't know what to do to fix
it. When I export the jar from Eclipse, it has this set of directories:
KCBSEvents
META-INF
mozilla
org
src
That is the one that works. When I build the jar using ant (below),
these are the directories present:
KCBSEvents
ME
;${lib.dir}/log4j-api-2.11.2.jar"/>
> unless:set="log4j-api.present"
>
> src="https://search.maven.org/remotecontent?filepath=org/apache/logging/log4j/log4j-api/2.11.2/log4j-api-2.11.2.jar";
> dest="${lib.dir}/log4j-api-2.11.2.jar" />
>
>
>
>
> includeantruntime="false">
>
>
https://search.maven.org/remotecontent?filepath=org/apache/logging/log4j/log4j-api/2.11.2/log4j-api-2.11.2.jar";
dest="${lib.dir}/log4j-api-2.11.2.jar" />
8-<--8-<------8-<------8-<--8-<--
> -Ursp
Could you post the content of the manifest file and your directory structure?
I suppose that the paths are not correct …
Jan
Von: Dennis Putnam [mailto:d...@bellsouth.net]
Gesendet: Montag, 25. Februar 2019 13:09
An: user@ant.apache.org
Betreff: Re: AW: Javac Run By Ant Script is Unable
My apologies again but I have not made any progress on this problem. Is
there perhaps a better forum I should be using at this point? I did make
one discovery. It appears that although the application works in Eclipse
when I try to export it to a runnable jar using the Eclipse wizard, the
resulting
I found an article on adding Maven dependencies to my ant script. While
I'm getting a successful build but the same exception when I run the
jar, I hope this is getting me closer. At least the pom.xml is in the
build. I am wondering if the added *fileset* is right and working. Here
is my latest:
Hi Jan,
Thanks. I'm using option 4. At least that is what my build file is
supposed to be doing. The problem is while the build is successful there
is something wrong with the jar produced. I suspect the Maven
dependencies are not linked in correctly in the compiled jar because the
pom.xml is not
If you have created your JAR the first step is done.
Starting the JAR could be done in several ways. Common is that you have to have
all external classes on the runtime classpath:
1. Hard coded start script.
Write a bash/bat-Script with the java command with all cp settings, e.g. (bat)
@ech
Ant's fetch.xml)
- use Ivy as dependency manager and use it to define the path's (see Ant's
check.xml)
Jan
> -Ursprüngliche Nachricht-
> Von: Dennis Putnam [mailto:d...@bellsouth.net]
> Gesendet: Montag, 18. Februar 2019 14:35
> An: user@ant.apache.org
> Betr
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
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
13 matches
Mail list logo
