Re: JavaClient Common classes
Re: JavaClient Common classes
- Subject: Re: JavaClient Common classes
- From: David Avendasora <email@hidden>
- Date: Wed, 25 Mar 2009 13:47:27 -0400
On Mar 25, 2009, at 1:07 PM, Stamenkovic Florijan wrote:
Have you thought about adding project templates to WOLips for
JavaClient apps (server and client)?
Or a built-in library that would add all the standard
WebServerResources jars to the classpath like the "WebObjects
Frameworks" one does for the server?
I isolate client side libs as Eclipse classpath variables. However,
I believe there is room for improvement. Not sure if it can be
standardized... Might be possible. Something like a "WOJC classpath
container" becoming a part of WOLips.
Personally, I think the better solution is to have WOLips build
process aware that client-side jars exist in the first place! If you
add a Framework or Project to your Build Path, both the incremental
and the ant (and maven) builds should automatically pick up the
WebServerResources/Java/*.jar files and put them on the class path.
Right now, it only puts the server-side jars (Resources/java/*jar) on
the class path.
Dave
_______________________________________________
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