Code management & deployment

From: Shane Mingins (shanemingins_at_yahoo.com.clothes)
Date: 12/09/03 

Date: Tue, 9 Dec 2003 16:16:36 +1300

[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 

-- 
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

Relevant Pages

  • Code management & deployment
    ... I am writing some relatively small desktop applications. ... I can create a jnlp file that refers to the application jar file sitting on ... check in source code to test ... move source code from test to production ...
    (comp.lang.java.help)
  • Re: Code management & deployment
    ... "Shane Mingins" wrote in message ... > I am using an ANT script to currently build and deploy the jar file to the ... check in source code to test ... move source code from test to production ...
    (comp.lang.java.help)
  • Re: Code management & deployment
    ... > I am writing some relatively small desktop applications. ... > I am using an ANT script to currently build and deploy the jar file to the ... move source code from test to production ...
    (comp.lang.java.softwaretools)
  • Re: z/OS Cobol source libraries
    ... However, when I did, it seemed that most shops had 3rd product source code control systems - or at LEAST used SCLM. ... Production COBOL source code is stored in PDS libraries that are exclusively managed by Endevor. ... You must specify a "Processor" name when compiling a COBOL program into Endevor, because the processor script must be different for batch or CICS, for different COBOL compilers, for DB2 or non-DB2, and for Debugger support or no debugger support. ...
    (comp.lang.cobol)
  • java class differences
    ... Previous people took the source code and compiled it and then compared it to the class they extracted from the production ear file. ... Are there any logical explanations for these minor discrepancies, such as different versions of compilers or different versions of j2ee.jar and struts.jar files? ...
    (comp.lang.java)