Re: Change Control and source versioning

Neill Harper wrote:

Does anybody have any tips for Change control and source checkout.
I'm using WDSC and we have an excellent package by MKS called Implementer
(or CM) that does very well for RPG, Synon etc, especially when it comes to
having multiple dev and testing environments. It looks like it can be used
for .class and .java but not for .jar.

<Vendor Response>
While MKS Implementer _CAN_ manage files in the IFS, for more robust control of PC/*nix type files, I suggest you take a look at MKS Source.

You can use MKS Source to manage check outs & check ins of your PC/*nix files in WDSC (using the Eclipse plug-in for MKS Source). After you have developed & tested the code, create a deployable artifact (jar, war, ear, etc.) you can then use MKS Implementer to deploy the application to your testing & production environments (either local or remote).

Both MKS Implementer and MKS Source are tightly integrated with our issue tracking system, MKS Integrity.

If you would like information on MKS Source and/or MKS Integrity, feel free to contact me privately and I'll be happy to have someone get in touch with you.
</Vendor Response>

david
(who works for MKS in addition to running these lists)