i'd like to second Celeste's approach - our engineers generally have a
complete development environment (including Oracle and MS SQL Server) on
their laptops. We have a shared development and testing/staging server on
our LAN - the shared development box for our HTML/Javascript/Shockwave
developers, the staging/testing machine for client review and QA. Everyone
checks their work into version control at lease daily, and the tech lead
does a complete pull from version control to the shared servers every day or
so.
This approach works remarkably well for a range of app-server environments:
Java/JSP, ColdFusion, ASP/COM.
re: restarting JRun when classes change - on your local (Windosw) machine
you can simply keep the Services control panel open and restart the JRun
Defal Server as needed.
re: cleaning out compiled JSP - we sometimes use a "restartclean" shell
script/batch file that stops JRun, deletes all the files in WEB-INF/jsp, and
starts JRun. Not an inconvenience at all.
regards,
Joe
Joe Niski | Senior Software Engineer/Internet Architect
Nine Dots
503.548.2176
Portland . Irvine . San Francisco . Toronto
[EMAIL PROTECTED]
> -----Original Message-----
> From: Haseltine, Celeste [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, August 02, 2001 8:25 AM
> To: JRun-Talk
> Subject: RE: bean newbie question
>
>
> Jay,
>
> I don't know about your development environment, but I require all
> developers to install the free version of JRUN on their local
> development
> machines. Everyone is also required to update their local
> source code from
> source safe upon notice, so that every developer has the same product
> framework to work with. This way, each individual can work
> on his segment
> of the product using his local copy of JRUN and IIS as the
> server on his
> local machine. Upon completion of development and local
> testing by the
> individual developer, his source code is uploaded to both
> source safe and to
> a development server upon approval of his lead. This is
> usually done on a
> weekly basis. This way, our testing department can test the
> entire product
> on a development server that every developer is mapped to.
> We can also use
> the development server to discuss and view code during meetings.
>
> I do not advocate using a development server for a large
> group of developers
> to actually develop on together. It's too easy for one
> person to make a
> change that subsequently "breaks" the product for everyone
> else, and brings
> the development process to a halt. By having a "development"
> environment
> installed on each persons computer, every programmer can
> proceed at his/her
> pace, and we can control when "changes" are uploaded to the
> development
> server. This way, the entire development server rarely goes down, and
> development process can proceed on schedule.
>
> I would be interested in any input from anyone else out there
> that has come
> up with a better software management/development process for web
> applications than the one I outlined above.
>
> Celeste
>
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
