I was able to work around the problem alluded to below with a little
experimentation and some aliasing. What I think found out in the
bargain is that one cannot exercise much control over the classpath
that is generated in an ant build from the built in woapplication task.
Specifically, any entries in ant.classpaths.wo.wolocalroot will occur
in random order in the generated classpath. In addition, all the
entries in the former will precede anything generated out of
ant.frameworks.wo.* whatever the ordering of task elements in
woapplication.
I found this a little surprising. I was expecting that ordering would
be preserved in both cases. It would be nice, in my opinion, to have
finer grained control over the generated classpath via the ant build.
That said, thanks to all who are making WOLips and Wonder possible. I
have made the transition from WO5.3/XCode to WO5.4/WOLips/Leo10.5
after working out a few kinks in addition to the above. I especially
like the Eclipse/WOLips environment (and have enjoyed the strongly
felt dialog from both sides). However, I haven't tackled the
EOGenerator variants yet. More to learn.
Thanks again,
Tom
On Nov 30, 2007, at 1:31 PM, Tom Woteki wrote:
> Hello:
>
> How can I set the classpath order that will be used at runtime in a
> deployment setting?
>
> I know how to do this for a development build using "Configure Build
> Path". In development mode my app runs fine because I have set the
> classpath order. However, when I deploy the generated classpath
> causes a problem.
>
> For deployment I have experimented with reordering the "framework"
> and "otherclasspath" elements in build.xml used by ant but this
> doesn't seem to have any effect on the order of things in the
> generated classpath. My app winds up using the wrong version of a
> class.
>
> Any help much appreciated.
>
> Thanks
> Tom
>
This archive was generated by hypermail 2.0.0 : Sat Dec 01 2007 - 17:49:58 EST