SCM - V OUTPUT SHOWS V2.0.1 NOT 3.0.1
When using the scm -v command version 2.0.1 shows.
BROWSE /tmp/K351156.09:48:12.82.stdout.ispfudl Line 00000000 Col 001 080 Command ===> Scroll ===> CSR ********************************* Top of Data ********************************** ************************************************************************ * IBM's internal systems must only be used for conducting IBM's * * business or for purposes authorized by IBM management. * * Use is subject to audit at any time by IBM management. * ************************************************************************ com.ibm.team.filesystem.cli.client, version 2.1.0.v20101110_2353 Subcommands: load login logout create create/workspace create/baseline create/ com.ibm.teamz.filesystem.cli.client, version 1.1.0.v20101110_2353 Subcommands: allocatez listdefz loadz loadzXml create/dataset list/datasetdefi com.ibm.team.filesystem.cli.tools, version 2.1.0.v20101110_2353 Subcommands: tools.verify tools.validate tools.echo.stdin tools.configvalue to com.ibm.team.filesystem.cli.core, version 2.1.0.v20101110_2353 Subcommands: help version daemon daemon/start daemon/stop com.ibm.teamz.zimport.cli, version 2.1.0.v20101110_2353 Subcommands: zimport ******************************** Bottom of Data ******************************** Here is the .profile EDIT /u/K351156/.profile Columns 00001 00072 Command ===> Scroll ===> CSR ****** ***************************** Top of Data ****************************** 000001 export PATH=$PATH:/MVSPP/lpp/jazz/v3.0/scmtools/eclipse 000002 export JAVA_HOME=/MVSPP/lpp/java/J6.0.1 000003 export SCM_WORK=/u/JAZZ/ccm 000004 export PATH=$PATH:$JAVA_HOME/bin ****** **************************** Bottom of Data **************************** Why doesn't Version 3 show? |
2 answers
The plugin version's weren't updated and I believe it started reflecting from 3.0.1 onwards.
|
We have been flip flopping a bit on whether the plugin version should match the release number or whether we should be following the Eclipse guidelines as described here. From memory I believe that for v3.0.1 we were told to set the plugin version to 3.0.1. Personally I believe that the right way to go is the Eclipse way and we are now following these guidelines. So, this means that from the 4.0 release onwards you will again see that he plugin version number does not match the release version of the product.
|
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.