Sharing Working sets
Hi,
Is it possible to share a Eclipse Working set within the team ?
I understand that adding the psf (that holds the workset definition)
file into Jazz SCM is one option, but then you first must export the
workset definition to a file in the local file system, and vice versa to
import it back. Any more elegant solution available?
Working with Beta2
/Lars
Is it possible to share a Eclipse Working set within the team ?
I understand that adding the psf (that holds the workset definition)
file into Jazz SCM is one option, but then you first must export the
workset definition to a file in the local file system, and vice versa to
import it back. Any more elegant solution available?
Working with Beta2
/Lars
4 answers
Hi,
Is it possible to share a Eclipse Working set within the team ?
I understand that adding the psf (that holds the workset definition)
file into Jazz SCM is one option, but then you first must export the
workset definition to a file in the local file system, and vice versa to
import it back. Any more elegant solution available?
Working with Beta2
/Lars
Hi,
In the documentation here: https://jazz.net/jazzdocs/index.jsp?topic=/com.ibm.team.scm.doc/topics/c_streams.html I found the following information:
"Streams and components are not defined in an Eclipse workspace, although loading a component into an Eclipse workspace defines it as an Eclipse working set, which you can select in the Navigator, Package Explorer, or Project Explorer views."
I'm not sure if there is any other way then the one you described and the one in the documentation.
kind regards,
Jakub
You may be mixing-up a "team project-set" with a purely UI concept of a "working-set. A team project-set can be exported to a .psf file while working-sets are part of your preferences.
The team project-set was added to eclipse to augment SCM systems which didn't make it easy to bootstrap and get the right line-up of projects. In Jazz we recommend you setup a stream with the component/projects your team members need to work on and they can simply create their own repo workspace and load it. When a repo workspace is loaded, we automatically create a working-set for each component that is loaded, as the documentation quote above mentions.
It may be possible that we could leverage the team project-set feature in Eclipse, but this hasn't been investigated since it seems initially to provide little value over what we already have with components, streams and repository workspaces
The team project-set was added to eclipse to augment SCM systems which didn't make it easy to bootstrap and get the right line-up of projects. In Jazz we recommend you setup a stream with the component/projects your team members need to work on and they can simply create their own repo workspace and load it. When a repo workspace is loaded, we automatically create a working-set for each component that is loaded, as the documentation quote above mentions.
It may be possible that we could leverage the team project-set feature in Eclipse, but this hasn't been investigated since it seems initially to provide little value over what we already have with components, streams and repository workspaces
Hi,
The thing is that we are synching our Jazz Repository with ClearCase, so
all our Eclipse projects ends up in the same Jazz Component.
So to simulate the logical partioning of our components we have created
a set of 'Java Working Sets'. Simply by switching working set we then
can have the same functionallity as Jazz components (or at least
visually). It would be very handy to be able to share these working sets
with other team members.
But I guess that this is more a general issue because we would also like
to share other settings that is defined on a Eclipse Workspace level
(templates, compiler settings, indentation rules etc)
BR
Lars
jlemieux skrev:
The thing is that we are synching our Jazz Repository with ClearCase, so
all our Eclipse projects ends up in the same Jazz Component.
So to simulate the logical partioning of our components we have created
a set of 'Java Working Sets'. Simply by switching working set we then
can have the same functionallity as Jazz components (or at least
visually). It would be very handy to be able to share these working sets
with other team members.
But I guess that this is more a general issue because we would also like
to share other settings that is defined on a Eclipse Workspace level
(templates, compiler settings, indentation rules etc)
BR
Lars
jlemieux skrev:
You may be mixing-up a "team project-set" with a purely UI
concept of a "working-set. A team project-set can be exported to
a .psf file while working-sets are part of your preferences.
The team project-set was added to eclipse to augment SCM systems which
didn't make it easy to bootstrap and get the right line-up of
projects. In Jazz we recommend you setup a stream with the
component/projects your team members need to work on and they can
simply create their own repo workspace and load it. When a repo
workspace is loaded, we automatically create a working-set for each
component that is loaded, as the documentation quote above mentions.
It may be possible that we could leverage the team project-set feature
in Eclipse, but this hasn't been investigated since it seems initially
to provide little value over what we already have with components,
streams and repository workspaces
Hi,
The thing is that we are synching our Jazz Repository with ClearCase, so
all our Eclipse projects ends up in the same Jazz Component.
So to simulate the logical partioning of our components we have created
a set of 'Java Working Sets'. Simply by switching working set we then
can have the same functionallity as Jazz components (or at least
visually). It would be very handy to be able to share these working sets
with other team members.
But I guess that this is more a general issue because we would also like
to share other settings that is defined on a Eclipse Workspace level
(templates, compiler settings, indentation rules etc)
BR
Lars
jlemieux skrev:
The thing is that we are synching our Jazz Repository with ClearCase, so
all our Eclipse projects ends up in the same Jazz Component.
So to simulate the logical partioning of our components we have created
a set of 'Java Working Sets'. Simply by switching working set we then
can have the same functionallity as Jazz components (or at least
visually). It would be very handy to be able to share these working sets
with other team members.
But I guess that this is more a general issue because we would also like
to share other settings that is defined on a Eclipse Workspace level
(templates, compiler settings, indentation rules etc)
BR
Lars
jlemieux skrev:
You may be mixing-up a "team project-set" with a purely UI
concept of a "working-set. A team project-set can be exported to
a .psf file while working-sets are part of your preferences.
The team project-set was added to eclipse to augment SCM systems which
didn't make it easy to bootstrap and get the right line-up of
projects. In Jazz we recommend you setup a stream with the
component/projects your team members need to work on and they can
simply create their own repo workspace and load it. When a repo
workspace is loaded, we automatically create a working-set for each
component that is loaded, as the documentation quote above mentions.
It may be possible that we could leverage the team project-set feature
in Eclipse, but this hasn't been investigated since it seems initially
to provide little value over what we already have with components,
streams and repository workspaces
Comments
Often when working on defects I will create a working set, named after the defect. To the working set I add the relevant files, folders and projects - not just project. It would be very useful to share that working set in the defect, so that anyone who subsequently works on or looks at the defect would have the option of importing the working set to their eclipse workspace.