If you're talking now about WOLips plugins development alone I did
notice that more recently the woenvironment etc seem to be using
maven for the .classpath files. I don't know when/who but that'd be
your issue. It took me a few goes to clean the whole project import
tree before it all compiled properly. I assumed it was all working
for you seeing as this is the first I've heard of the problem .. and
I failed to mention it.
Yeah, I am talking wolips only ... I'll check this -- since everything
depends on woenv, that would explain why the whole plugin stack breaks
when this has an issue. It APPEARS to break every OTHER time i launch
eclipse, which is really strange behavior. It never seems to clean up
if do a clean build, but quitting and restarting fixes it (until the
next restart). Thanks for the lead ...
ms
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [email protected]