On 22/02/2008, at 4:11 AM, Mike Schrag wrote:
>> Okay, I'll wait for that.
>>
>>> Until then, I strongly object in any changes in that area, as
>>> this stuff is known to break if you just look at it the wrong way.
>>
>> That's fine too, sure. We'll see how this will work out.
> The new code doesn't FIX this, btw ... It makes it more explicit.
> The new UI would just simply not let you pick JavaWOExtensions from
> System -- it would only show "JavaWOExtension Local
> Frameworks". This is part of the new approach for classpath
> management "less power = less confusing". The big problem right
> now is that the UI lets you pick System, then ignores you and picks
> Local instead. We can make it disable the checkbox next to the
> same-named ones lower in the tree in the current UI, though, at
> least to make it a little less confusing.
I'm happy for it to pick 'User' or 'Local' at runtime if that's
what's in place at runtime... (e.g., you want to test a new version
of a framework *before* everyone gets the update) but why should
WOLips enforce which framework is saved for the project -- so that it
mucks up svn for other users?
This is one of the annoying things at the moment - that when someone
else checks out a project that if the framework doesn't exist it's
silently removed from the classpath :-/
But the point of being able to select a particular framework (in a
particular location) is so that your build server, for example, will
use the right one.
with regards,
--Lachlan Deck
This archive was generated by hypermail 2.0.0 : Thu Feb 21 2008 - 17:39:43 EST