Bugzilla – Bug 6243
deployed gridshib jars in GT4.2
Last modified: 2008-09-11 20:45:22
You need to log in before you can comment on or make changes to this bug.
Some of the GridShib for GT JAR files end up $GLOBUS_LOCATION/lib instead of $GLOBUS_LOCATION/lib/common. For example, after deploying GS4GTv0.6.0 into GT4.2.0, the following JARs end up in $GLOBUS_LOCATION/lib: gridshib-gt-echo-0_6_0.jar gridshib-gt-echo-0_6_0_stubs.jar gridshib-gt-service-unittests-0_6_0.jar gridshib-gt-service-unittests-0_6_0_stubs.jar I believe these JARs belong in $GLOBUS_LOCATION/lib/common with the rest of the GS4GT JAR files.
Since the EchoService has two separate source directories, this is easy to fix in gt/echoservice/java/source/build.xml: <property name="build.lib.basedir" location="build/lib"/> <property name="build.lib.dir" location="${build.lib.basedir}/common"/> <property name="garjars.id" value="garjars"/> <fileset dir="${build.lib.basedir}" id="garjars"/> <target name="jar" depends="compile"> <jar destfile="${build.lib.dir}/${jar.name}" basedir="${build.dest}"/> </target>
Patched gt/service/java/test/build.xml so that it behaved just like gt/interceptors/java/source/build.xml.
Committed the patched build files to CVS HEAD. These patches will be distributed with GS4GTv0.6.1RC2.
