Re: Third Party Jar Project
Re: Third Party Jar Project
- Subject: Re: Third Party Jar Project
- From: John Pollard <email@hidden>
- Date: Thu, 31 Jul 2008 18:37:01 +0100
Lachlan,
Thanks. I created a webobjects framework and moved a single jar into
it as a test, adding it to the framework build path, ticking it for
export and adding the framework as a dependency to my application. In
development this worked a treat.
I then released the application and framework to a test server and
annoyingly it can't see packages that are in the jar. The framework
release looks fine with the jar inside it. The application
MacOSClassPath.txt appears to reference the jar within the framework
ok (the same way it successfully references jars in other frameworks).
I note you said to set an option to embed frameworks. In general we
release frameworks separately from applications so there is just one
version of any framework released and this is shared. Any thoughts on
tracking the problem down would be welcome. I'd better move to wo-admin.
John
On 30 Jul 2008, at 21:44, Lachlan Deck wrote:
On 30/07/2008, at 9:11 PM, John Pollard wrote:
I hope to create a framework that contains just third party jars
needed by my application. Up to now we've used /Library/Java/
Extensions for such jars or /Library/WebObjects/Extensions.
(pain will persist this way)
I have found this guidance:
http://wiki.objectstyle.org/confluence/display/WOL/Add+a+Jar+Dependency
When creating an Eclipse project for jars, what is the best option
of project type? Two candidates seem to stand out within the WOLips
section:
Jar Project (is this documented? google didn't seem to turn much
up)
No not documented, but I just created one to see what it has. It
quite simply is a cut down version of a Framework project (it's
build file only builds your java classes as a jar).
Not what you're looking for I'd suggest.
WebObjects Framework (possibly adds other bells and whistles that
aren't needed?
Yep - create one of these, add your jars to the Library folder. In
eclipse select them and right click > Build Path > Add to build
path. Then go to project > Properties > Build Path > Order and
Export tick the checkbox next to each of them to export them to
other projects.
Then go to project properties for your app and in its build path >
Projects choose add... and choose your framework.
Normal rules apply for ant building for your framework when wanting
to deploy your app (i.e., install your framework then build your app
setting the option to embed frameworks)
with regards,
--
Lachlan Deck
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden