Having them named the same will prevent them from getting both... and
you can easily get both as the default templates include
JavaWOExtensions all by themself.
So there is a slew of issues here:
- JavaWOExtensions is included by default (even when you define
wonder.project=true)
- you'd have a ton of CP ordering problems fo you have different names
We should either:
- stop building JavaWOExtensions
- replace the system version
- provide a different launch jar, which can handle dependencies in a
serious way (which I assume will get me the "uh, but we're working on
this for WO X" message)
- don't care
I'd choose door number 4. As this is not really a problem as both
should be identical and installing Wonder will definitely fix this.
Cheers, Anjo
Am 21.02.2008 um 20:08 schrieb Mike Schrag:
> My point here is that you either want JavaWOExtensions or you want
> ERJavaWOExtensions NOT both. Renaming the framework would let you
> choose which one you want. If you include both, you're screwed and
> on your own, but I don't know why you would.
>
> On Feb 21, 2008, at 2:06 PM, Anjo Krank wrote:
>
>> Dude. The components are named the same. So not only you'd have
>> confusion and work updating classpath for dozens of projects, but
>> also confusion about which framework WOTable comes from....
>>
>> Cheers, Anjo
>>
>> Am 21.02.2008 um 19:57 schrieb Mike Schrag:
>>
>>>> I was considering if we should either leave it out from wonder or
>>>> overwrite the system frameworks. Both have severe consequences,
>>>> either for existing or future users... damned if you do, damned
>>>> if you don't...
>>> I wasn't saying it was a bad idea to bring it in, but I think it
>>> should be renamed ERJavaWOExtensions. It's _relatively_ painless
>>> for users -- you just have to update your build path for the change.
>>>
>>> ms
>>>
>>
>
>
This archive was generated by hypermail 2.0.0 : Thu Feb 21 2008 - 14:20:59 EST