Re: ALL SOLVED, Re: having weird build and run issues...
Re: ALL SOLVED, Re: having weird build and run issues...
- Subject: Re: ALL SOLVED, Re: having weird build and run issues...
- From: Paul Yu <email@hidden>
- Date: Wed, 18 Jan 2012 14:16:15 -0500
Actually this is not truly a WO issue. This is best practices that allows a small development shop to do a lot of things with very low overhead of human resources. However, the people involved have to be good enough to setup these best practice things.
Converting from WO pre-wonder to Wonder-based takes a bit of a leap, but once done, Wonder provides so much more.
I would think learning to piece together a Java (non-WO) environment to do all the things that WO+EOF+Wonder provide would be a rather steep curve as well. And then you will run into walls that may be impossible to climb over.
On Wednesday, January 18, 2012 at 2:06 PM, Ramsey Gurley wrote:
I don't think anyone ever said the barrier to entry was low with WO ;-)
Ramsey
On Jan 18, 2012, at 10:12 AM, James Cicenia wrote:
Hmmm,,, now I understand all those Jenkins/Hudson emails....
Well I ran the ant command and it built all the libraries and everything is working as would be expected.
AND, all based upon Wonder Source. So that is very good.
I am now 100% Wonder All the Way (WAW)
First it was errest, than it was wonder,than migrations, than it was git., now it's jenkins. Hard to keep up with this legacy stuff.
Thanks
James
On Jan 18, 2012, at 10:30 AM, Ramsey Gurley wrote:
You have to build/install every framework before you can build your app. The ant install puts a newly built copy in your Library/Frameworks directory. It's a bit of a pain to do that. The easy way to manage builds is to set up a Jenkins build server (or use maven?). Building in Eclispe is for suckers ;-)
With Jenkins, you set up the build once and never have to worry about it again. You can also get the Jenkins batch task plugin and set up deployment scripts once, and never have to worry about those again either. The initial setup is a chore, but once it is done, it's one-click easy to deploy on demand. Building happens continuously by polling the source repository.
Ramsey
On Jan 18, 2012, at 9:12 AM, James Cicenia wrote:
Looks like Wonder binaries and Wonder Source didn't play well together.
So I deleted all the binaries and imported the couple dozen I needed.
That solved the ERXKeyFilter issue and it now works great in development.
BUT,
When I run a build it still gives me:
BUILD FAILED
/Users/jcicenia/Documents/workspace/BlessingsApp/build.xml:212: The framework name 'ERCoolComponents' does not exist.
It does exist I tell you!
James
_______________________________________________
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