;
>
>
> 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">
>
>
ile 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 S
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:
use references:
>
> …
>
>
>
>
>
>
>
> You mave have a look at
> http://ant.apache.org/manual/tutorial-HelloWorldWithAnt.html
>
>
>
>
>
> Jan
>
>
>
>
>
> Von: Dennis Putnam [mailto:d...@bellsouth.net]
> Gesendet: Diensta
ences:
…
You mave have a look at
http://ant.apache.org/manual/tutorial-HelloWorldWithAnt.html
Jan
Von: Dennis Putnam [mailto:d...@bellsouth.net]
Gesendet: Dienstag, 19. Februar 2019 15:40
An: user@ant.apache.org
Betreff: Re: Javac Run By Ant Script is Unable to Find External
Hi Jaikiran,
Thanks for the reply. Here is my command:
/bin/ant -v -Dmember.number=$number -Dmember.name=\"$name\" -f
makejar.xml
I assume it is using ant's java task based on the build file
(makejar.xml). I'm a bit confused. Doesn't all the necessary classpath
info come from the build x
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
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 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
neric
> includes="**.*.jar"/>
>
> Eclipse:
> Ant: not used (I think this controlls the "export behaviour" for
> inter-project dependencies)
>
> So combined (and tuned):
>
>
>
>
>
>
>
>
>
>
&
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
ort behaviour" for
inter-project dependencies)
So combined (and tuned):
Jan
> -Ursprüngliche Nachricht-
> Von: Matt Bertolini [mailto:viper2...@gmail.com]
> Gesendet: Sonntag, 17. Februar 2019 18:45
> An: Ant Users List
> Betreff: Re: Javac
Hi Dennis,
I think you might be mixing up Eclipse concepts and Ant concepts and that
might be causing some extra confusion. Based on your original email, the
compiler is having issues finding your third-party dependencies. I believe
Jaikiran is correct in saying that the task needs to be given so
I apologize for being a pest but this is a problem I cannot resolve on
my own. The more I read the more confusing it gets. It seems like there
are thousands of ways to accomplish what I want but none make any more
sense than what I have. Is there no one that can help me debug this
problem or at lea
Hi Jaikiran,
Thanks for the reply. I thought the classpath parameter defaulted to
"basedir"/.classpath. In any case I made the following change:
Unfortunately that didn't help. The ant output is exactly the same. FWIW
here is .classpath:
Hi Dennis,
On 13/02/19 11:56 PM, Dennis Putnam wrote:
>
I don't see any classpath being passed to the javac task in your build
script. You should be passing a classpath containing your jars that are
required to compile the source. There's more than one way to do that.
The javac task manual has
I had a working ant script until I made a number of source changes to my
Java project via Eclipse and egit. I obviously somehow inadvertently
changed something, somewhere, that is causing javac to not find
libraries (perhaps pushed something via git that is not part of the
source). There are some M
22 matches
Mail list logo
