On 20 Jan 2009, at 16:08, Stamenkovic Florijan wrote:
On Jan 20, 2009, at 10:28, John Pollard wrote:
Many thanks for your reply. I was kind of aware that Eclipse did
something different when using incremental build; a recent post I
made gave an example where compiles worked on the incremental build
but not in ant. I should point out that this was all working before
I upgraded to recent versions of Eclipse and the nightly WOLips. So
the ant clean install did previously put the gif files into the
jar, or at least didn't remove them!
Yeah, I'd guess that earlier versions of the install target did not
do a clean -> compile -> bundle, but just compile -> bundle.
Actually the ant build is and was triggered from my own deployment
script which requests a clean install, so I don't think it was missing
the clean step before. I run this deployment process separately from
and outside of Eclipse.
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.
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.
I have not tried turning off the incremental builder, I just
assumed that coding is more pleasant with it on and didn't have a
reason that I knew of to change this before.
Yes, it is more pleasant. I have to wait for the ant build to do all
of it's stuff every time that I save any server side changes.
However, since my server projects are quite simple in general, this
works fine for me, and gives me results more consistent with the
final deployment. Though this may have improved with the latest
WOLips classpath handling.
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