Ive posted to this list before about my opposing view to workstation
driven devlelopment. Its not that I dont think its a good idea, its
great if you have the hardware, tools, and portable applications to
support it. BUT...
you can still get away with using a shared server!
our team (including
I agree with your point, but not completely ;)
That setting is what we also were doing in the past, for some sites.
Even though it works we had major issues when the server needs to be
restarted or a programmer just crash the all thing doing testing and
so on and so forth or a producer is
Developer
Aegeon Pty. Ltd.
www.aegeon.com.au
Phone: +613 8676 4223
Mobile: 0404 998 273
-Original Message-
From: cfaussie@googlegroups.com [mailto:[EMAIL PROTECTED] On Behalf
Of Pat Branley
Sent: Tuesday, 16 October 2007 11:29 PM
To: cfaussie
Subject: [cfaussie] Re: CF + Subversion best
Are are any of the people following this thread using subclipse in Eclipse?
From: [EMAIL PROTECTED]
To: cfaussie@googlegroups.com
Subject: [cfaussie] Re: CF + Subversion best practices ?
Date: Tue, 16 Oct 2007 06:28:58 -0700
Ive posted to this list before about my opposing view
:36 AM
To: cfaussie@googlegroups.com
Subject: [cfaussie] Re: CF + Subversion best practices ?
Are are any of the people following this thread using subclipse in Eclipse?
From: [EMAIL PROTECTED]
To: cfaussie@googlegroups.com
Subject: [cfaussie] Re: CF + Subversion best practices ?
Date: Tue
Mark Ireland wrote:
Are are any of the people following this thread using subclipse in
Eclipse?
Yes, we are. We also use TortoiseSVN at the desktop and had been using
that for some time before we moved to CFEclipse as our base dev environment.
We tried Subversive in Eclipse and had hassles
Andrew Scott wrote:
Shared development is not good, and why would you do it and force your
developers into putting up with other developers breaking code while you are
trying to do your job?
Downtime is a very good reason to be more productive and move to workstation
development.
Or,
We use subclipse as well.
From: cfaussie@googlegroups.com [mailto:[EMAIL PROTECTED] On Behalf Of Mark
Ireland
Sent: Wednesday, 17 October 2007 9:36 AM
To: cfaussie@googlegroups.com
Subject: [cfaussie] Re: CF + Subversion best practices ?
Are are any of the people following this thread using
Thanks Geoff,
i saw those links while ago hen I was doing some research on the
matter... very helpful ;)
On Oct 15, 3:52 pm, Geoff Bowers [EMAIL PROTECTED] wrote:
Andrea,
On Oct 15, 10:04 am, Andrea [EMAIL PROTECTED] wrote:
any extra ideas/ best practice I guess everyone has
IMO, the age of designers who only do photoshop or html is long gone...
maybe they could be trained to write their presentation layer stuff as
coldfusion pages and/or custom tags?
That aside, if you think option 3 will break your post-commit scripts,
why not use maven instead of ant, and
I'd have to agree. I've tried it a number of different ways, and the only
really feasible option is to make designers use source control. On both mac
and windows there are very easy to use ways to tie in source control through
your explorer windows or into dreamweaver etc etc but if you really
cool I never used maven before, I will definetely have a look at
it...
On Oct 15, 10:12 am, Haikal Saadh [EMAIL PROTECTED] wrote:
IMO, the age of designers who only do photoshop or html is long gone...
maybe they could be trained to write their presentation layer stuff as
coldfusion pages
Scott
Senior Coldfusion Developer
Aegeon Pty. Ltd.
www.aegeon.com.au
Phone: +613 8676 4223
Mobile: 0404 998 273
-Original Message-
From: cfaussie@googlegroups.com [mailto:[EMAIL PROTECTED] On Behalf
Of Andrea
Sent: Monday, 15 October 2007 10:33 AM
To: cfaussie
Subject: [cfaussie] Re: CF
Andrew...
That's exactly what I'm actually trying to achieve with solution
3... :)
I just do not want designers to have the need to install CF and apache
on their machines... designers will over-kill me ! .. that's why in
solution 3 they will work directly on the server (on a shared folder)
Andrea,
I'd recommend against the shared repository - I went that way with a team a
few years ago and it was very painful. You have the difficulties of user
tracking etc, and when you start using tags and branches properly everything
goes to hell, but primarily we found using the dev server
: +613 8676 4223
Mobile: 0404 998 273
From: cfaussie@googlegroups.com [mailto:[EMAIL PROTECTED] On Behalf
Of Toby Tremayne
Sent: Monday, 15 October 2007 11:16 AM
To: cfaussie@googlegroups.com
Subject: [cfaussie] Re: CF + Subversion best practices ?
Andrea,
I'd recommend against the shared
@googlegroups.com
Subject: [cfaussie] Re: CF + Subversion best practices ?
Andrea,
I'd recommend against the shared repository - I went that way with a team a
few years ago and it was very painful. You have the difficulties of user
tracking etc, and when you start using tags and branches
: 0404 998 273
From: cfaussie@googlegroups.com [mailto:[EMAIL PROTECTED] On Behalf
Of Toby Tremayne
Sent: Monday, 15 October 2007 11:16 AM
To: cfaussie@googlegroups.com
Subject: [cfaussie] Re: CF + Subversion best practices ?
Andrea,
I'd recommend against the shared repository
Andrea,
On Oct 15, 10:04 am, Andrea [EMAIL PROTECTED] wrote:
any extra ideas/ best practice I guess everyone has sort of
similar issues
Your best bet is to set up a local application environment for your
designers, and have them commit changes to the repository just like
your
19 matches
Mail list logo