TestMaker JAR Issues

[fcohen]

This enhancement cleans-up the TestMaker supporting JAR files.

William Martinez wrote:

We needed to package the Selenium things into TM and that means adding it to the build and also to the installers. There we found some problems:

1. The installers are packaging at least two sets of jars (one for TM and another one for TestNetwork?) containing the same jars (BTW, those are scattered in 4 to 6 places). This is because originally TestNetwork? was a gui less version of TM. The problem we face with this is that we are keeping two places where the jars should be placed, and we are facing synch problems due to this when we install. If following the same, we will need to add another set of jars twice, and keep updating the jars twice whenever denali guys relase it next SelenuimUnit? incarnation.

2. The buld.xml and the installers had some synch problems too. The build.xml for instance, was copying jars from one place to the other one even before the jar was created. There is also a cross dependency (loop): TM needs the Testnetwork.jar to build its testmaker.jar, and testnework needs the testmaker.jar to build its testnetwork.jar. Cyclic dependencies.

3. After any tool addition, we spent several hours, even days, getting the classpath in order again. This is because the new tool will add a new version of a jar that we already have. If we put our version before the tool version, we may get problems for the tool not having its own jar version. If done the other way, the tool's jar first, it will work but then other tools will break. This means, inevitable, we will rearrange the testmaker.bat and .sh, the installers and the build.xml.

So, and just to clarify, we are not actually cleaning the jars. That is a task that is mandatory but will take time, and I may have some ideas to solve that involving changing the legacy Testmaker infraestructure. But we need to talk that later and for TM 6.0.

Right now, we need to adjust the build.xml and the installers. That means a find/replace to make TM use the Lib at TestNetwork?, and make SOAPUI use its own jars instead of using ours. Also, instead of having 6 places where to find the jars, we copy them all to just one directory to easy the reference in the installers.

Luis Carlos already did that, since it was a copy of jar files and a replace of the path in the xmls. All is building correctly and working, he only needs to check the installers.

These changes will add the new centralized jars location and the updates to the config files. LC also created a tag in the CVS to be able to rollback just in case, although the change does not impact more that four files and no files were removed or added (just moved somewhere else).