• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Building for deployment
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Building for deployment


  • Subject: Re: Building for deployment
  • From: Henrique Gomes <email@hidden>
  • Date: Mon, 14 Dec 2009 18:20:25 +0000

On Dec 14, 2009, at 4:42 PM, Kieran Kelleher wrote:

> "receipt" ?

:-) Does it show that I'm not a native speaker?! I meant 'recipe'.



>
> 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....


> See Wonder/Build/build/generic.xml for details.
>
> HTH, Kieran
>
>
>
> 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
>

 _______________________________________________
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

  • Follow-Ups:
    • Re: Building for deployment
      • From: Lachlan Deck <email@hidden>
    • Re: Building for deployment
      • From: Patrick Robinson <email@hidden>
References: 
 >Building for deployment (From: Mark Wardle <email@hidden>)
 >Re: Building for deployment (From: Henrique Prange <email@hidden>)
 >Re: Building for deployment (From: Kieran Kelleher <email@hidden>)
 >Re: Building for deployment (From: Henrique Gomes <email@hidden>)
 >Re: Building for deployment (From: Kieran Kelleher <email@hidden>)

  • Prev by Date: Re: Building for deployment
  • Next by Date: Re: Building for deployment
  • Previous by thread: Re: Building for deployment
  • Next by thread: Re: Building for deployment
  • Index(es):
    • Date
    • Thread