Even after doing that, and I could confirm that the WOFrameworks had
references to all correct and existing jars, I still had red x
problems ... deleting build, clean and rebuild all did not solve it.
Eventually a clean all projects, then restart Eclipse, then build all
got everything see the build paths properly. Is this normal? ... or
is this a side effect of the fact that we bundle jars into apple
style Frameworks?
On Apr 25, 2007, at 1:44 PM, Kieran Kelleher wrote:
> Either this is a pain in the head, or I am not seeing the
> 'refactoring' shortcut for switching out jars and automatically
> updating all project references.
>
> If I change the jars in a framework .... let's say I go form
> commons-lang-2.0.jar to commons-lang-2.3 or delete some jar like
> backport-util-concurrent.jar since I am now using java 1.5 and no
> longer need it, I find that I have to into every project that
> references the framework, right-click the WO Frameworks library,
> remove the framework from the referenced frameworks, click finish,
> then right-click the WO Frameworks library/Configure again and re-
> add the referenced framework back. Then after fixing all the
> project references, I have to do a full clean and rebuild on all
> affected projects.
>
> Any shortcut for this (removing a jar altogether in a framework or
> changing to a new version with a different jar name)?
This archive was generated by hypermail 2.0.0 : Wed Apr 25 2007 - 14:01:10 EDT