Re: Building for deployment
Re: Building for deployment
- Subject: Re: Building for deployment
- From: Kieran Kelleher <email@hidden>
- Date: Mon, 14 Dec 2009 13:46:40 -0500
I think if you just pass the -Dlocal.root=/Users/username/ or sth like
that to override the /Library/Frameworks property in Wonder's ant
build properties, it should just install there I would think. Check
wonder's generic.xml for the exact property name that determines the
install local root dir.
HTH, Kieran
On Dec 14, 2009, at 1:32 PM, Henrique Gomes wrote:
On Dec 14, 2009, at 4:17 PM, David Avendasora wrote:
Hi Henrique,
The big drawback to having Hudson install wonder in a location
like /Library/Frameworks or ~/Library/Frameworks is that you can
only have one version of wonder installed at a time.
What if you have one version of your app that builds against an
older version like 9692 but in development you want to use the head?
I have some substantially modified shell scripts for setting up
Wonder builds in Hudson (based off Mike's original) that allow you
to specify the version of wonder you want and it will build and
install it in a repository instead of the system or user directories.
They are written to work with OS X, but I don't think they'd have
to be modified much, if at all, for linux.
Here's the repository: http://wonova.svn.beanstalkapp.com/repos/Hudson/WonderBuilder/
You should be able to create a new Hudson job, then replace the
config.xml file for it with the one in the repository and that
should get you a job that allows you to specify the version of WO,
Wonder, and the install location (Repository).
If you want to change the script to install Wonder directly in the
local or user directory, then feel free. Look at the lines that set:
1) wonder.framework.install.root
2) web.framework.install.root.
I may include a version of the script that does that as well.
If you were in the Washington DC area tomorrow night, I'll be
presenting on this setup at WONoVA... it's just a quick hop across
the pond, right?
Right! For some definition of "quick" :-)
Thank you, on my build server I'm doing things very similar, but
I'll check the possibility of specifying the desired wonder version.
I had that on a earlier build setup (non hudson) but lately I just
take the latest and although I never had problems it can sure be
improved.
My only question is on those rare situations that I want to do ant
builds on my mac, a simple way to stuff the wonder frameworks on ~/
Library/Frameworks would be nice. I'll have a look at those
properties but always had the impression that all you could is to
coerce wonder into a separate 'root'
Henrique Gomes
Dave
On Dec 14, 2009, at 10:48 AM, Henrique Gomes wrote:
On Dec 14, 2009, at 2:29 PM, Kieran Kelleher wrote:
Wonder is installed locally from the same working copy as the
wonder workspace projects are linked to
Can you share the receipt for that? Right now I use a hudson build
server ( linux ) for the builds with all the complication of
setupWonder.sh but I was always curious if there is a simple
switch to make
$ ant frameworks.install
install on the user domain like ~/Library/Frameworks
Thanks,
Henrique Gomes
_______________________________________________
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
David Avendasora
Senior Software Engineer
K12, Inc.
*****
WebObjects Documentation Wiki : http://wiki.objectstyle.org/confluence/display/WO/
*****
WebObjects API: http://developer.apple.com/legacy/mac/library/documentation/MacOSXServer/Reference/WO54_Reference/index.html
*****
_______________________________________________
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