On 15/12/2009, at 5:20 AM, Henrique Gomes wrote:
> On Dec 14, 2009, at 4:42 PM, Kieran Kelleher wrote:
>
>> In any case, Wonder uses build properties to decide where the various
>> directories are.
>>
>> You can put a file named "build.properties" in the Wonder root directory to
>> dictate the build properties which includes the target directory or pass a
>> build.properties on the command line to override wonder's build properties.
>
> Yes, the problem is the amount of properties. I have hudson building wonder
> in ${WORKSPACE}/Root. And the other jobs using the artifacts from the wonder
> build, expanding the tar.gz on {WORKSPACE}/Root.
> That's all fine for the build server. On my mac I just wanted a simple -local
> switch to have wonder install the frameworks on ~/Library/Frameworks. I
> seldom require them like that, and dislike putting stuff in /Library if it is
> just for a quick test.
> In those cases I manually cp -r from the build directory....
Just to reiterate the point that Henrique Prange made - should you choose to
use maven you can define all of the necessary dependencies *once* for the
project and it will build everywhere... no additional hoops to jump through via
additional shell scripts or ensuring that the same versions of frameworks are
installed in the same places etc
with regards,
--
Lachlan Deck
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [email protected]
