[apologies if u have read this on comp.lang.java.help .... I only just found
this group and thought it may be more appropriate for my query]
Hi
I am looking for some insight (or links) on how to possibly handle java code
management and deployment.
The situation is as follows:
I am writing some relatively small desktop applications.
It looks like Web Start would be an easy mechanism to deploy the
applications.
I can create a jnlp file that refers to the application jar file sitting on
a file server.
I can refer to any resources that the application needs , i.e. other jar
files, in the jnlp file.
I am using IntelliJ Idea to develop the applications.
I am using an ANT script to currently build and deploy the jar file to the
file server.
I have CVS.
Some questions that I am wondering:
How do I manage the development cycle along the lines of ---
1. check source code out of production
2. make changes
3. check in source code to test (is this a valid step?)
4. build code from test and deploy to test location
5. move source code from test to production
6. build code from production and deploy to production location
What structures do people use for dev/test/prod environments?
How do I manage common resources e.g. jdbc jar files?
One of the audit requirements we have is that developers are not allowed
write access to production source and not allowed to build production
binaries.
Thanks
Shane

Signature
shanemingins@yahoo.com.clothes
remove clothes before replying
"It is not the strongest of the species that survive, nor the most
intelligent, but the one most responsive to change." --- Charles Darwin
Jose Rubio - 10 Dec 2003 05:14 GMT
Read my reply on the comp.lang.java.help group.
Jose
> [apologies if u have read this on comp.lang.java.help .... I only just found
> this group and thought it may be more appropriate for my query]
[quoted text clipped - 40 lines]
> Thanks
> Shane