🚀 go-pugleaf

Richard Chrenko <richard@solarenergy.ch> wrote:
> In the Jbuilder4 Archive Wizard, I can successfully create a JAR file of
> type <application>. However, even using the settings "content"::"include
> required classes and known resources" and "dependencies"::"never include
> any classes and resources" in the JAR file properties menu, it sucks in
> the .class files from all other packages which the application
> references. This appears to invalidate the entire concept of modular JAR
> files (i.e. one JAR file per package and referencing these via the
> Class-Path tag in the <application> JAR file's manifest).

Whose concept is this?  I've never heard it before. 

> Is this a bug in Jbuilder4, or is there a way to prevent .class files
> from other packages being included in the <application> JAR file?

JBuilder's archive wizard assumes that it is to build a complete,
standalone jar from everything found in the project which is required
by its main class.  If there are references to other classes in the
project, those will be included.

The only way to create jars with a package-to-jar relationship like
you're talking about is so place each package into a project of its
own.  

Or use the jar utility manually and do it yourself.


-- 
Joi Ellis (TeamB)               http://www.teamb.com/
No direct email, please.
For best results, post on news server newsgroups.borland.com!
Newsgroup Guidelines: http://www.borland.com/newsgroups/guide.html
Only posts which violate the rules in guide.html are subject to cancelation.