🚀 go-pugleaf

Roy:

Generally you don't stick other peoples classes in your own app jar
file.  These go off on the classpath somewhere.  This makes it easy to
comply with the "worst case" license agreement (some state that a 3rd
party must be deployed in its original container and in its entirety)
and, more importantly, it becomes much easier to swap out 3rd party
libraries as they change.  It can also make it possible to deliver
smaller chunks to your end users in a web deployment situation;
especially when you have to update a couple of your own classes and
everything stays the same.

You can, as you've seen, change this functionality if you like.

Libraries, in general, serve as a way to discretely manage your project
resources.  The Archive Wizard simply leverages a small piece of this
functionality.

-Rich

roymcbrayer wrote:
> 
> I guess I am missing the big picture here.  If the archive excludes the libraries, then what function do libraries server.  Do I need to set up a directory structure on the application machine that includes the library files.  This is not just directed to IPWorks.  I have had the same problem every time I try to deploy third party class files.  Source files are no problem but class files are not found.  What do I do with the class files included in the library if they are not included in the archive builder?
> 
> Thanks,
> 
> Roy
> Joi Ellis <joi@artoo.gyles19.visi.com> wrote:
> >Roy McBrayer <roymcbrayer@austin.rr.com> wrote:
> >
> >> I'm not sure why it can't find the IPWorks library.  If I include it
> >> as a required library for the project, shouldn't JBuilder include all
> >> of the required files in the jar?  I am specifying that all classes and
> >> resources for IPWorks be included in the jar.  I encountered this problem
> >> before with trying to use class files in a third party package and have
> >> never been able to figure out how to integrate them into a project in
> >> JBuilder so that they can be found at run time.  I thought that was what
> >> the library functionality provided.  Can anyone explain this?
> >
> >By default, the archive builder excludes everything in required libraries.
> >You have to visit the node's properties | dependencies tab and change
> >this behavior.  However, beware that doing so may violate the license
> >agreement with IP*Works.  I can't find the reference, but I think that
> >jar is a developer license only, not a deployment license.
> >
> >For using the app's manifest to control the classpath, see here:
> >http://www.visi.com/~gyles19/cgi-bin/fom.cgi?file=252
> >
> >> Roy
> >
> >> John McGrath  [TeamB] <ng-b@JPMcGrath.net> wrote:
> >>>On 30 Nov 2001 11:59:30 -0800, Roy McBrayer wrote:
> >>>
> >>>> It works fine from within JBuilder but will not work with the
> >>>> jar from the command line.
> >>>
> >>>> $ java -jar mailtest.jar
> >>>> Exception in thread "main" java.lang.NoClassDefFoundError
> >>>
> >>>It cannot find the IPWorks library.  You can specify it with the java
> >>>-classpath option.
> >>>
> >>>There is also a mechanism for specifying required libraries in the
> >>>manifest, but I have not used it.
> >>>
> >>>--
> >>>Regards,
> >>>
> >>>John McGrath [TeamB]
> >>>
> >>>---------------------------------------------------
> >>>Before sending me e-mail, please read:
> >>>    http://www.JPMcGrath.net/newsgroups/e-mail.html
> >