|
Tim, We use Ant to build our deployed application. It is a great tool that really helps to ensure that you don't mess up. Ant also works pretty well with CVS, which is what we use for change management. Originally, we deployed our site as a War file to test and development. When we realized that we only distribute one copy and the War file was just extra work, We backed off and deployed files and a Jar to production and files and classes to test. We eventually ended up deploying classes in all environment because it let us slip in changes more easily. Now that things have settled down, we could probably get by with the Jar combination but I don't see any real advantage. David Morris >>> Tim_Fenton@hen.invesco.com 01/22/02 04:50AM >>> We are nearing the point when we deploy our first Java programs in the iSeries/AS400 production environment and I wondered if anyone has advice on what models work. Our current thinking is that we will include all our classes in a single jar and that there would be a "production.jar", a "test.jar" and a "developing.jar" all contained in '/java' directory. By altering the classpath keyword on the RUNJVA command we will be able to pick up the relevant classes. Any comments/advice gratefully received...
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.