Hello Hudson builders,
I watched Mike Schrag's session on Hudson from WOWODC09, and got Hudson up and
running in fairly short order building an application project. Thanks Mike!
I'm interested to know how the Hudson users around here handle framework
dependencies for their application projects
Thanks for the information Denis. That helps, I was wondering should I use
commons-lang!!!
Cheers,
Shravan Kumar. M
From: Denis Frolov
To: Shravan Kumar. M
Cc: WO Dev Group
Sent: Thu, July 29, 2010 10:31:26 PM
Subject: Re: Encode
I honestly have no idea. That is an interesting question.
Chuck
On Jul 30, 2010, at 6:55 PM, Ken Anderson wrote:
> I'm just not sure what kind of control you have over the firewall with these
> cloud servers...
>
>
> On Jul 30, 2010, at 8:48 PM, Chuck Hill wrote:
>
>>
>> On Jul 30, 2010, a
I'm just not sure what kind of control you have over the firewall with these
cloud servers...
On Jul 30, 2010, at 8:48 PM, Chuck Hill wrote:
>
> On Jul 30, 2010, at 5:42 PM, Ken Anderson wrote:
>
>> Does everyone run apache and WO on the same machine? No DMZ?
>
> That depends on the size
On 31/07/2010, at 9:18 AM, Mark Ritchie wrote:
> On 30/Jul/2010, at 2:01 PM, Farrukh Ijaz wrote:
>> That's why when you know your build is stable, just tag it with a name such
>> as something-stable under tags folder in your svn structure. So next time
>> you need to produce the same build just
On Jul 30, 2010, at 5:42 PM, Ken Anderson wrote:
> Does everyone run apache and WO on the same machine? No DMZ?
That depends on the size of the installation. Usually Apache and some of the
instances can co-exist. You can run Apache on each machine and put a load
balancer in front. For lo
Does everyone run apache and WO on the same machine? No DMZ? I'm still not
clear on how these cloud servers are supposed to work regarding separation...
Ken
On Jul 29, 2010, at 1:35 AM, Lon Varscsak wrote:
> I have a dedicated box on rackspace too...it's pricey, but solid as a rock.
> WO/ap
On 30/Jul/2010, at 2:01 PM, Farrukh Ijaz wrote:
> That's why when you know your build is stable, just tag it with a name such
> as something-stable under tags folder in your svn structure. So next time you
> need to produce the same build just checkout the project from tag instead of
> trunk and
On Jul 30, 2010, at 4:27 PM, David Holt wrote:
On 2010-07-30, at 1:04 PM, Ramsey Gurley wrote:
On Jul 30, 2010, at 3:58 PM, David Holt wrote:
On 2010-07-30, at 12:26 PM, Ramsey Gurley wrote:
On Jul 30, 2010, at 2:51 PM, David Holt wrote:
Hi all,
I would like to display one propertyK
Sent from my iPad
On 30-Jul-2010, at 9:12 PM, Mark Ritchie wrote:
>> And *I* wouldn't store the binary, only all assets that are needed to create
>> it: woproject binary, WO systems libs, Wonder libs, etc.
>> After all, the tgz is next to worthless in a year or two, unless you can
>> actuall
On 2010-07-30, at 1:04 PM, Ramsey Gurley wrote:
>
> On Jul 30, 2010, at 3:58 PM, David Holt wrote:
>
>>
>> On 2010-07-30, at 12:26 PM, Ramsey Gurley wrote:
>>
>>> On Jul 30, 2010, at 2:51 PM, David Holt wrote:
>>>
Hi all,
I would like to display one propertyKey for a recursiv
On Jul 30, 2010, at 3:58 PM, David Holt wrote:
On 2010-07-30, at 12:26 PM, Ramsey Gurley wrote:
On Jul 30, 2010, at 2:51 PM, David Holt wrote:
Hi all,
I would like to display one propertyKey for a recursive
relationship and the rule doesn't seem to work as it does for a
normal relatio
On 2010-07-30, at 12:26 PM, Ramsey Gurley wrote:
> On Jul 30, 2010, at 2:51 PM, David Holt wrote:
>
>> Hi all,
>>
>> I would like to display one propertyKey for a recursive relationship and the
>> rule doesn't seem to work as it does for a normal relationship to a
>> different entity. Do I ne
On Jul 30, 2010, at 2:51 PM, David Holt wrote:
Hi all,
I would like to display one propertyKey for a recursive relationship
and the rule doesn't seem to work as it does for a normal
relationship to a different entity. Do I need to do something
special for this case? The rule I am using ha
Hi all,
I would like to display one propertyKey for a recursive relationship and the
rule doesn't seem to work as it does for a normal relationship to a different
entity. Do I need to do something special for this case? The rule I am using
has no effect and I am not sure why.
100 (entity.name
Hey!
On 30/Jul/2010, at 10:57 AM, Anjo Krank wrote:
> Since it's a tgz, I wouldn't count on the diffs being much smaller than the
> actual file...
Hrm, that's an interesting point. Has anyone ever measured?
> And *I* wouldn't store the binary, only all assets that are needed to create
> it: wo
Found the bug in EOMdelDOC.
Firefox (and IE, ugh) choke on the following constructs:
should be
and also
should be
Safari and Opera handle all forms.
I've modified the necessary templates and submitted them as a bug report
to objectstyles.
Since it's a tgz, I wouldn't count on the diffs being much smaller than the
actual file...
And *I* wouldn't store the binary, only all assets that are needed to create
it: woproject binary, WO systems libs, Wonder libs, etc.
After all, the tgz is next to worthless in a year or two, unless you c
Hey!
On 30/Jul/2010, at 7:34 AM, Farrukh Ijaz wrote:
> On 30-Jul-2010, at 3:57 PM, Valerio Luccio wrote:
>> Farrukh Ijaz wrote:
>>> At first place I would avoid svning the tar as it is a binary file and even
>>> a minor change will change the binary and I guess every time the commit
>>> will re
On 30-Jul-2010, at 3:57 PM, Valerio Luccio wrote:
> Farrukh Ijaz wrote:
>> At first place I would avoid svning the tar as it is a binary file and even
>> a minor change will change the binary and I guess every time the commit will
>> recognize it as new file will commit the whole tar instead of
Farrukh Ijaz wrote:
At first place I would avoid svning the tar as it is a binary file and even a
minor change will change the binary and I guess every time the commit will
recognize it as new file will commit the whole tar instead of differences, as a
result it will start eating repository di
At first place I would avoid svning the tar as it is a binary file and even a
minor change will change the binary and I guess every time the commit will
recognize it as new file will commit the whole tar instead of differences, as a
result it will start eating repository disk space very fast. I
22 matches
Mail list logo
