Hi,
I'm recommending that we place third party jars in a framework. The
for projects that need them then simply add the framework to the class
path.
I'm recommending that as a better solution to putting the third party
jars in /Library/WebObjects/Extensions. I remember that as a best
practice although I'm not 100% clear on the benefits. I listed the
following. Please someone correct me if I'm wrong or missing something:
------------
The problem with jars in /Library/WebObjects/Extensions is that they
are loaded whether you want / need them or not. They may cause
conflicts if you open a project that already has that jar in it or one
of its frameworks. You are not managing those dependencies from
eclipse as you should. You may deploy an app that works well in your
development environment and then find out at deployment time that it
needs a jar that you had in your /Library/WebObjects/Extensions.
You don't have these problems if you put the jars in a framework and
then add the framework to the class path of the project that needs the
classes in the jars.
-----------
Is this accurate? Am I missing something? :-)
Thanks,
Ricardo
_______________________________________________
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]
