Hi Mark,
On Dec 18, 2009, at 12:02 PM, Mark Wardle wrote:
Dear all,
Thank you to all who replied to this - both on and off list.
The problem was that I was (in development) building in eclipse and
setting the java build path with the required projects (including my
own frameworks and Wonder'
Dear all,
Thank you to all who replied to this - both on and off list.
The problem was that I was (in development) building in eclipse and
setting the java build path with the required projects (including my
own frameworks and Wonder's), and *not* have anything listed in the
"Libraries" tab (exce
On Dec 15, 2009, at 6:02 AM, David Avendasora wrote:
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 additi
You know, one the really good things about WO is the humor in this community.
:-)
Thanks, now I feel archaic instead of ignorant :-)
HG
On Dec 14, 2009, at 7:24 PM, Patrick Robinson wrote:
> Oh, I dunno - perhaps you simply enjoy archaic word meanings. According to
> the OED, under "receipt
On Dec 14, 2009, at 3:58 PM, Lachlan Deck wrote:
> 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 "buil
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
On Dec 14, 2009, at 1:32 PM, Henrique Gomes wrote:
> 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
Oh, I dunno - perhaps you simply enjoy archaic word meanings.
According to the OED, under "receipt, n.":
13. gen. The formula of a preparation, or an account of the
means, for bringing about some end; (in extended use) the means for
attaining an end. Cf. RECIPE n. 3. Now arch.
:-)
-
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 roo
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
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 ro
"receipt" ?
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
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 devel
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 setupWond
My build.xml installs all dependent frameworks locally. Wonder is
installed locally from the same working copy as the wonder workspace
projects are linked to. A bash script then runs my project's
build.xml, copies the tar.gz's remotely to one relay server, then
executes commands via ssh to
Hi Mark,
On 13/12/09 20:00, Mark Wardle wrote:
What's the recommended way of creating sane builds - particularly
using PW and your own frameworks from source and making everything
work as automatically as possible?
I used to speak like that before I started using Maven [1]. Have you
ever he
On 14/12/2009, at 8:30 AM, Mark Wardle wrote:
> I'm pulling my hair out trying to get a WOA that contains all embedded
> frameworks - including WO54, project wonder and my own.
This should be almost a push-button exercise with the latest tools. I do this
all the time.
> Naturally, during devel
Hi all,
I'm pulling my hair out trying to get a WOA that contains all embedded
frameworks - including WO54, project wonder and my own.
Naturally, during development, everything just works from within
Eclipse. In particular, I have Project Wonder building from within
Eclipse also.
I assumed it wo
18 matches
Mail list logo
