Hi Lachlan,
On Jan 4, 2006, at 3:56 PM, Lachlan Deck wrote:
I prefer to use the classpath to control versions.
I long ago abandoned /Library/Frameworks and /Library/WebObjects/
Extensions for deployment. As soon as you have multiple deployed
apps with multiple framework / jar versions you have a mess.
Hmm.
I either do what Guido said and package all this in the .woa
bundle, or have directories for these specific to one or a few
apps. Thus I can update one without fear of altering others.
Aha, a little archive search: the Project Wonder perl script seems
to be the best fit for this.
http://cvs.sourceforge.net/viewcvs.py/*checkout*/wonder/Wonder/
Utilities/woaFrameworkMerger/Readme.html
perl. Don't much care for the taste of perl :-), but it does what I
was trying to describe. The only possible addition is to also copy
the contents of /Library/WebObjects/Extensions to
App.woa/
Contents/
Extensions/
That way the only shared jars are the JDBC etc in /Library/Java/
Extensions.
Chuck
--
Coming in 2006 - an introduction to web applications using WebObjects
and Xcode http://www.global-village.net/wointro
Practical WebObjects - for developers who want to increase their
overall knowledge of WebObjects or who are trying to solve specific
problems. http://www.global-village.net/products/practical_webobjects
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [email protected]
