Re: Eclipse: building an (non-j2EE) app jar file.
From: P.Hill (goodhill_at_xmission.com)
Date: 12/17/03
- Next message: Vincent Cate: "Target VM Microsoft? or Java Lint to check for MS VM compatibility?"
- Previous message: Michael Deathya: ""ant install" error using tomcat"
- In reply to: Jose Rubio: "Re: Eclipse: building an (non-j2EE) app jar file."
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Wed, 17 Dec 2003 10:25:47 -0700
Jose Rubio wrote:
> The best approach is to keep them separate and include all of them in the
> classpath of the application.
> "P.Hill" <goodhill@xmission.com> wrote in message
>>What is the best way to instruct it to build a jar with all
>>of the .classes from various libraries (i.e. Junit, whatever
>>JDBC I using etc.)
[...]
>>
>>It seems kludgie to unzip all such jars into a resource directory, it
Just to clarify the details, I think you are saying that the best way to play
with Eclipse is to take any library I want to be in my non-j2EE application jar
and
(1) drop it from the list of libraries in the class path
(2) unsip the classes into some extra dir (maybe workspace/<project>/libclasses)
(3) identify this DIRECTORY as a source directory in the project (it will find
no sources, but it will move non-source out and into the bin dir when building)
This will result in a bigger and better set of classes in my bin and thus in the
final jar.
Are these the details of what you are suggesting?
-Paul
- Next message: Vincent Cate: "Target VM Microsoft? or Java Lint to check for MS VM compatibility?"
- Previous message: Michael Deathya: ""ant install" error using tomcat"
- In reply to: Jose Rubio: "Re: Eclipse: building an (non-j2EE) app jar file."
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|