Re: Eclipse 3.4.1
Re: Eclipse 3.4.1
- Subject: Re: Eclipse 3.4.1
- From: Ramsey Gurley <email@hidden>
- Date: Tue, 14 Oct 2008 00:09:14 -0400
On Oct 13, 2008, at 11:55 PM, Mike Schrag wrote:
I tried upgrading to Eclipse 3.4.1, upgraded to the WOLips nightly
build and downloaded and installed the lastest Wonder-latest-
frameworks-5.4. Now, when I open my workspace I don't see my
WOFrameworks folder, and neither does eclipse since nothing in the
ERX framework compiles. What can I do to get my frameworks back
into my project? I tried looking at the filters, but there are
only two listed, *.class and .*
Even when I try to open Eclipse 3.3 my frameworks can no longer be
seen. Why would upgrading have blasted my project's framework
setup? And why was I dumb enough to try this in the first place :-(
WOLips 3.4 has an entirely new classpath system. Touching a WOLips
3.3 project with WOLips 3.4 will cause the .classpath file to be
upgraded, and it is not backwards compatible. WO Frameworks are no
longer handled as a single classpath container, rather each
framework is now managed independently as its own classpath
container (which more closely matches reality), and they each appear
as Libraries in your build path. As far as ERX not compiling, I'm
not sure what version of the source you have, but given that the
trunk of Wonder has been upgraded to WOLips 3.4, and I check it out
all the time, I can assure you that it compiles without any errors
under WOLips 3.4 straight out of SVN. If you're using WO 5.4, you
will need to change the build path of WOOGNL to remove Sources_53
and add Sources_54, but other than that, things should work fine.
That said, nightly is not "stable" for a reason. If you're using
nightly, you should really either be on the wolips mailing list or
you should read the wolips blog (http://wolips.blogspot.com/2008/09/its-alive.html
), so you know what you're getting yourself into. There are
SUBSTANTIAL changes to the way things work in the new WOLips that
you need to be aware of.
ms
You make it sound so scary! :-)
I take it that it's stable enough though...? The only reason I'm
updating is because the new .classpath files were pushed into the
repository. I took that as an 'all clear' :-) Everything looks fine
so far (knock on wood). Any gotcha's that we should be aware of??
Ramsey
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden