We should add hacked classes to the bootstrap classpath.
Uli
Am 10.11.2007 um 15:52 schrieb Mike Schrag:
>>>
>> I understand the problem and the solution, but I think that providing
>> the ability to order entries on the classpath is a quick hack
>> around a
>> problem that goes far deeper -- properly solving the problem means
>> that
>> you need to handle dependencies like OSGi does, or maybe the upcoming
>> Java module system (although I am not sure how that works in detail).
> I believe in the grand scheme you are absolutely right ... I think
> NSBundle is the source of a lot of confusing problems in WO because
> of this. However, I also think that possibly the only reason the
> problem of ordering exists is because of Project Wonder and that it
> does some dirty things overriding core framework classes. Does
> anyone have any other examples of CP ordering being an issue other
> than Wonder? I wonder (no pun intended :) ) if we can address this
> in an easier way and just define a " load framework first" option on
> frameworks. I think the only reason you need ordering is to make
> one (or more) frameworks come before the core. Beyond that, I think
> it really IS more like an OSGi bundle that does not overlap.
>
> ms
>
This archive was generated by hypermail 2.0.0 : Mon Nov 12 2007 - 03:48:57 EST