Default workspace location in RTC 3.0.1 Eclipse Client (Win)
The RTC 3.0.1 Eclipse Client zip (for Windows) no longer provides a default workspace location of @user.home/workspace when prompted for workspace location after initial invokation of client. Previous versions of the RTC Eclipse client did (e.g. 2.0 and 2.0.0.2). Any "base" installation of Eclipse does as well. This is a definite change in behavior. The 3.0.1 Eclipse Client now provides the client installation path/workspace as the default workspace location whereas before it was always @user.home/workspace. We have traced the difference down to a missing entry in 'config.ini' as follows:
client->eclipse->configuration->config.ini: ... osgi.instance.area.default=@user.home/workspace ... We almost view this as a bug in the RTC 3.0.1 Eclipse Client package for Windows. Creating the workspace below the installation path of client would fail for anyone who does not possess Administrator Rights on their PC (as is the case in large enterprise environments such as ours). Should I go ahead and submit a Defect work item? Thanks --Tim |
2 answers
The RTC 3.0.1 Eclipse Client zip (for Windows) no longer provides a default workspace location of @user.home/workspace when prompted for workspace location after initial invokation of client. Previous versions of the RTC Eclipse client did (e.g. 2.0 and 2.0.0.2). Any "base" installation of Eclipse does as well. This is a definite change in behavior. The 3.0.1 Eclipse Client now provides the client installation path/workspace as the default workspace location whereas before it was always @user.home/workspace. We have traced the difference down to a missing entry in 'config.ini' as follows: Hi Tim Yes, please file this as a bug (and in general, if you think something is wrong - add a work item) anthony |
Thanks Anthony. I have filed Defect 176647 (Found In = 3.0.1). Here is link to Defect:
https://jazz.net/jazz/web/projects/Rational%20Team%20Concert#action=com.ibm.team.workitem.viewWorkItem&id=176647 --Tim |
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.