Upgrading from Eclipse 3.3.2 to 3.4.1
Upgrading from Eclipse 3.3.2 to 3.4.1
- Subject: Upgrading from Eclipse 3.3.2 to 3.4.1
- From: Gaastra Dennis - WO Lists <email@hidden>
- Date: Fri, 31 Oct 2008 13:33:18 -0700
Dear List,
1) Will these instructions also work if you don't use Wonder; in
particular, the temporary Wonder Application/Framework projects?
2) Is 3.4.1 supported by a stable WOLips release?
3) What does the "New Hotness" stand for?
With Kind Regards,
Dennis Gaastra
On 28-Oct-08, at 5:08 PM, Chuck Hill wrote:
On Oct 28, 2008, at 5:03 PM, Mr. Frank Cobia wrote:
On Oct 14, 2008, at 6:45 AM, Kieran Kelleher wrote:
Here is the rough checklist for upgrading ... (in my case I have
Wonder source linked into my workspace ... and I use WO 5.3.3)
- Every project's build.properties needs to have project.name and
project.name.lowercase defined
- Check Build Path Order and put ERExtensions at the top of the
build order (that is important!)
- Do a pre-upgrade commit of everything to svn
- Turn off autobuild
- Upgrade to Eclipse 3.4.1 and latest WOLips Nightly (New Hotness)
and close Eclipse without building
I know this is probably a stupid question with an easy answer, but
I will ask it anyway. Is there a way to upgrade Eclipse 3.3 to
3.4.1 within Eclipse or do I have to download a new copy of Eclipse?
You have to download a new copy. You can use the new copy with your
existing workspace, it will upgrade it.
Chuck
- Download and install latest Wonder
- Reopen your 3.4 workspace
- Create a new temporary WonderApplication project
- Replace your old application build.xml files with new one from
temp project
- Replace your old application woproject/*.patternsets with new
ones from temp project
- Create a new temporary WonderFramework project
- Replace your old framework build.xml files with new one from
temp project
- Replace your old framework woproject/*.patternsets with new ones
from temp project
- Delete your old woproject/ant path whatever files in all projects
- Right-click application projects -> Properties -> Turn on
embedding (the more embed checkboxes you turn on, the less fire
Future You will be playing with ;-) )
- Clean/Rebuild all
- Test app(s)
- Commit to svn
If you have build issues, open Build Path and check the Order of
Frameworks and push ERExtensions to the top (Mike, possibly the
automatic upgrade should do this anyway if ERExtensions is in the
classpath?)
HTH, Kieran
On Oct 14, 2008, at 12:09 AM, Ramsey Gurley wrote:
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 _______________________________________________
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
_______________________________________________
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
_______________________________________________
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
--
Chuck Hill Senior Consultant / VP Development
Practical WebObjects - for developers who want to increase their
overall knowledge of WebObjects or who are trying to solve specific
problems.
http://www.global-village.net/products/practical_webobjects
_______________________________________________
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
_______________________________________________
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