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!
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.
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.
On 20 Jan 2009, at 14:11, Stamenkovic Florijan wrote:
I'll try to do some speculating based on what you say....
1. Your project relies on Eclipse's Incremental build to copy
the .gif resources to the bin output folder of your project
2. WOLips compile target does *not* copy those resources to bin, but
only compiles .java files
3. Your jarring of the client side code (added to the build.xml I
presume?) jars the content of the bin folder
If this is all true (and you could verify), then I guess the problem
in the situation is that WOCompile does not deal with anything
that's not a .java file. Ergo only java sources get compiled and
copied to the bin output folder. Which would be a fundamental
difference between Eclipse's incremental builder and the WOLips ant
Workarounds I can think of:
1. Separate your client and server projects. This is what I do,
however I do not do WebStart. If you are, this might be slightly
more difficult to do (though not at all impossible). However it
might not chime well with your deployment process.
2. Add some ant magic to your build.xml to manually copy .gif (and
other resources) to your bin output as a part of the ant build.
3. Continue with the hack that you are already doing.
4. David Avendasora and Mike Schrag have been working on WOJC
additions to the ant build process (which are AFAICS all WebStart
focused), so you might want to coordinate with them.
On a side note, the first thing I do for my new WO projects is turn
the Incremental builder off (in project properties). I rely solely
on WOLips ant, exactly to avoid this kind of confusion. However, I
think that the JC / WebStart additions to WOLips depend on it...
Hope this helps,
p.s. - also I'd be interested to hear how exactly are you setting up
your client/server code, perhaps we could discuss it...
On Jan 20, 2009, at 06:52, John Pollard wrote:
I have a framework with a classes.include.patternset that ensures
gif resource files are included in my jar (why I need this isn't
really relevant, but it is for accessing the image resources in a
java client application).
If I use Eclipse, Project, Clean on this framework, followed by
WOLips Ant Tools, Install then all is well, my gif files are
embedded in the installed framework's jar.
If however I then use my deployment script to do a command line ant
clean install, the gifs do not appear in the jar.
If I follow that with another WOLips Ant Tools, Install from within
Eclipse, the gifs are still missing. The only fix is to do an
Eclipse Project, Clean again.
A workaround is to drop the "clean" from the command line call to
I have WOLips nightly from about 2 weeks ago and Eclipse.
The ant command that drops the gifs is:
ant -lib /Developer/Applications/eclipse/plugins/
org.objectstyle.wolips.woproject.ant_3.4.5594/lib clean install
Thanks for any help.
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