On Jan 20, 2009, at 12:28, John Pollard wrote:
Although this is client side code, it is already in its own
separate project, so doesn't get any special client-side treatment
other than this gif bundling within the jar which is just done
using patternset rules, so nothing special within build.xml. My
jnlp is manually edited and managed and my deployment scripts copy
the jar to the appropriate place for java web start access.
So, you have a separate client side project... I think that is a
good way of handling it, I also keep my client side stuff separate.
However, I don't understand then the ant build confusion. Is your
client side project a WOLips project, or just a standard Java
project? Or an ant based Java project? Also, where are those .gif
resources located? In which project I mean...
A WOLips project. The .gif resources were in the same folder as
the .java files.
Yeah, that's what I thought. I guess that can be tricky, as the
desired results (for a client app, as opposed to a WO server app) are
different. I use a standard Java app project for my client stuff, and
the FatJar plugin to generate the end product jar, and the manifest
file and all. I also have all sorts of resources in my source tree,
and no problems bundling them all into a jar. However, in client
projects I only rely on the incremental builder (combined with
FatJar), no ant.
If your client side project is a WOLips project, may I ask why? How
do you have it set up?
Probably for no good reason, just copying processes used with other
non-client projects. At least the patternset stuff was useful in
allowing me to include the gifs in the jars.
Hm, I never tried doing that. Just always used Java projects with
added client side libs.
F
_______________________________________________
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]
