Re: Eclipse: building an (non-j2EE) app jar file.
From: Jose Rubio (spam_at_airphoria.com)
Date: 12/13/03
- Next message: Peter Bradley: "Re: Netbeans: debugger"
- Previous message: Michael Amling: "Re: Netbeans: debugger"
- In reply to: P.Hill: "Eclipse: building an (non-j2EE) app jar file."
- Next in thread: P.Hill: "Re: Eclipse: building an (non-j2EE) app jar file."
- Reply: P.Hill: "Re: Eclipse: building an (non-j2EE) app jar file."
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Sat, 13 Dec 2003 21:32:05 GMT
The best approach is to keep them separate and include all of them in the
classpath of the application.
Jose
"P.Hill" <goodhill@xmission.com> wrote in message
news:braqv3$vq$1@terabinaries.xmission.com...
> I have a lovely Eclipse project with source and various referenced
libraries.
> I was playing the the Jar creation tool, but can't figure out one thing.
>
> 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
would
> certainly slow down project rebuilds wouldn't it?
>
> What is the reasonable clean approach using Eclipse to identify contents
of
> Jars that I want to place into my final build jar (it is not a J2EE war
file
> just a jar full of classes and resources)?
>
> -Paul
>
>
- Next message: Peter Bradley: "Re: Netbeans: debugger"
- Previous message: Michael Amling: "Re: Netbeans: debugger"
- In reply to: P.Hill: "Eclipse: building an (non-j2EE) app jar file."
- Next in thread: P.Hill: "Re: Eclipse: building an (non-j2EE) app jar file."
- Reply: P.Hill: "Re: Eclipse: building an (non-j2EE) app jar file."
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
|
