×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
Neill Harper skrev:
I was wondering what most people do? Do you keep everything in jars or just
point your class path to a big folder with all of the classes in it.
Most non-trivial projects end up consisting of a _LOT_ of classes.
Having these as individual class-files in the filesystem may grow very
large, but is perfectly doable. Zipping them together in jar-files is
what most people do for deployed projects (as opposed to projects under
development). The name of the jar file then typically is on the form
"project-x.y.z.jar" where x.y.z is the version number (date or build
number is typical, or a major+minor+subminor releasenumber), which allow
you to manage these reasonably.
I would suggest that this is the graniuity you use for deployement and
you should be able to put these in as binary resources in your
management system.
From WSDCi there is an "Export" -> "Jar" option which is quite usable.
When you get a little more experienced, I'd be happy to elaborate on
your options :)
/Thorbjørn
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
