Re: migrate a project to eclipse 3.4.x and new wolips 3.4.x
Re: migrate a project to eclipse 3.4.x and new wolips 3.4.x
- Subject: Re: migrate a project to eclipse 3.4.x and new wolips 3.4.x
- From: David Holt <email@hidden>
- Date: Fri, 6 Mar 2009 10:11:42 -0800
Hi Paolo,
I think that this is all there is officially:
http://wolips.blogspot.com/
There are also some posts in the WOLips mailing list archive usually
with the subject including "new hotness" or Eclipse 3.4.1. I'll
include one I marked as relevant when I was doing the same:
HTH.
David
On 6-Mar-09, at 8:28 AM, Paolo Sommaruga wrote:
Hi,
I'am using eclipse 3.3.2 with wolips 3.3.5640, no wonder. There is
a guide, doc, or faq in order to migrate a wo project to eclipse
3.4.x and new wolips 3.4.x ?
Regards
Paolo Sommaruga
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
@mac.com
This email sent to email@hidden
From Kieran:
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
- 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
_______________________________________________
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