Home » Eclipse Projects » Eclipse Platform » More on Eclipse and ClearCase
|
Re: More on Eclipse and ClearCase [message #152853 is a reply to message #152774] |
Tue, 04 November 2003 20:09 ![Go to previous message Go to previous message](theme/Solstice/images/up.png) ![Go to next message Go to next message](theme/Solstice/images/down.png) |
Eclipse User![Friend of Eclipse Friend](/donate/web-api/friends_decorator.php?email=) |
|
|
|
Originally posted by: wegener.cboenospam.com
Mikael Petterson wrote:
> Hi,
> A while ago I got some help from David Wegener (see below).
> I followed his instructions, thanks David, and I now have an environment
> setup for me.
> We use different versions of the same java source tree (using labels in
> the config spec). Each version is a release with specific functionality.
> Here are my follow-up questions:
> * Lets say that we have made a couple of releases and that we must go back
> to release and make corrections ( not too unusual).The person making the
> correction does he/she have to make an import into the workspace again of
> the older version. That is, the most current proejct is contained in the
> workspace and when other versions is needed we import them?
My suggestion would be to create a separate workspace for making changes
to an old version. If you use the Rational plugin, you can then use the
Add existing WSAD project to workspace. This keeps your work separate and
helps prevent confusion when looking at code in the editor.
> * If we make any changes to the common perferences/settings in the dot
> files then we have to import project again or ....?
If you have the dot files under Clearcase control, then checking the files
in will make them available to everyone who can see them in their config
spec. Stopping and restarting Eclipse should pick and of these changes up.
> All help is very much appreciated.
> //Mikael Petterson
> Ps. Is this the right forum for my questions.
|
|
|
Re: More on Eclipse and ClearCase [message #153009 is a reply to message #152853] |
Wed, 05 November 2003 14:09 ![Go to previous message Go to previous message](theme/Solstice/images/up.png) ![Go to next message Go to next message](theme/Solstice/images/down.png) |
mikael petterson![Friend of Eclipse Friend](/donate/web-api/friends_decorator.php?email=mikael.petterson%40ericsson.com) Messages: 73 Registered: July 2009 |
Member |
|
|
Hi Dave,
I am getting more confused.
Question 1.
===========
I tried to download the clearcase plug-in from rational. When I click the
link you sent me I get the following in the browser window:
http://www-140.ibm.com/developerworks/rational
Then I click the following link:
Add-ins, plug-ins, and scripts
ClearCase
Plug-ins - Get the IBM Rational ClearCase SCM adapters for Eclipse 2.0 for
both Windows and Linux.
I am using Solaris 8 and it seems like the plugin does not work with my
os?!
Question 2
==========
You suggest to have a separate workspace when I make changes to an old
version. I don't get the whole picture.
I have the following source tree in clearcase:
/vobs/rbs/sw/rbssw1/boam_subsys/src/se/ericsson.......
If I create the boam project one time and set workspace to
/vobs/rbs/sw/rbssw1/boam_subsys a directory called boam will be created and
it will contain .classpath and .project files ( all dot files). I make
elements of them all and check them in.
When a team member shall work with the project boam the config spec sets
which version that the user will "see". Then the user starts up the
eclipse with the -data /vobs/rbs/sw/rbssw1/boam_subsys as workspace and
imports the project boam.
Is this ok to do or what could be the drawbacks and what is your advice to
handle it ( please refer to my example).
Is there another way to make sure that the .project .classpath will be
loaded each time we work on a a specific increment (decided by config
spec.)?
I appreciate your advice and it is valuble for the credability of eclipse.
Regards,
//Mikael
Dave Wegener wrote:
> Mikael Petterson wrote:
> > Hi,
> > A while ago I got some help from David Wegener (see below).
> > I followed his instructions, thanks David, and I now have an environment
> > setup for me.
> > We use different versions of the same java source tree (using labels in
> > the config spec). Each version is a release with specific functionality.
> > Here are my follow-up questions:
> > * Lets say that we have made a couple of releases and that we must go back
> > to release and make corrections ( not too unusual).The person making the
> > correction does he/she have to make an import into the workspace again of
> > the older version. That is, the most current proejct is contained in the
> > workspace and when other versions is needed we import them?
> My suggestion would be to create a separate workspace for making changes
> to an old version. If you use the Rational plugin, you can then use the
> Add existing WSAD project to workspace. This keeps your work separate and
> helps prevent confusion when looking at code in the editor.
> > * If we make any changes to the common perferences/settings in the dot
> > files then we have to import project again or ....?
> If you have the dot files under Clearcase control, then checking the files
> in will make them available to everyone who can see them in their config
> spec. Stopping and restarting Eclipse should pick and of these changes up.
> > All help is very much appreciated.
> > //Mikael Petterson
> > Ps. Is this the right forum for my questions.
|
|
|
Re: More on Eclipse and ClearCase [message #153147 is a reply to message #153009] |
Wed, 05 November 2003 17:35 ![Go to previous message Go to previous message](theme/Solstice/images/up.png) ![Go to next message Go to next message](theme/Solstice/images/down.png) |
Eclipse User![Friend of Eclipse Friend](/donate/web-api/friends_decorator.php?email=) |
|
|
|
Originally posted by: wegener.cboenospam.com
Mikael Petterson wrote:
> Hi Dave,
> I am getting more confused.
> Question 1.
> ===========
> I tried to download the clearcase plug-in from rational. When I click the
> link you sent me I get the following in the browser window:
> http://www-140.ibm.com/developerworks/rational
> Then I click the following link:
> Add-ins, plug-ins, and scripts
> ClearCase
> Plug-ins - Get the IBM Rational ClearCase SCM adapters for Eclipse 2.0 for
> both Windows and Linux.
> I am using Solaris 8 and it seems like the plugin does not work with my
> os?!
> Question 2
> ==========
> You suggest to have a separate workspace when I make changes to an old
> version. I don't get the whole picture.
> I have the following source tree in clearcase:
> /vobs/rbs/sw/rbssw1/boam_subsys/src/se/ericsson.......
> If I create the boam project one time and set workspace to
> /vobs/rbs/sw/rbssw1/boam_subsys a directory called boam will be created and
> it will contain .classpath and .project files ( all dot files). I make
> elements of them all and check them in.
> When a team member shall work with the project boam the config spec sets
> which version that the user will "see". Then the user starts up the
> eclipse with the -data /vobs/rbs/sw/rbssw1/boam_subsys as workspace and
> imports the project boam.
> Is this ok to do or what could be the drawbacks and what is your advice to
> handle it ( please refer to my example).
> Is there another way to make sure that the .project .classpath will be
> loaded each time we work on a a specific increment (decided by config
> spec.)?
We work with ClearCase under Windows, so we use it a little differently.
We have multiple views active at a time, each mapped to its own drive
letter. In this mode, each view has its own directory structure and you
can work on both simultaneously by bringing up different instances of
Eclipse each pointing to a different workspace.
I have also seen people switch which view is assigned to their workspace
drive letter. This works as well. However, you have to make sure that
you bring down eclipse prior to making the change. When you bring Eclipse
back up, you need to perform a refresh for the project. The refresh will
make sure that everything is built properly.
You should be able to work similarly to this second method. One thing I
would recommend is to not have your workspace residing in your ClearCase
view. Define you workspace to be in a separate location within your home
directory. When you define your project, uncheck the Use Default Location
and point to the ../boam directory. The workspace location is for
personal preferences that really shouldn't be in ClearCase. The project
location is what you want in ClearCase.
As long as the .project and .classpath files are ClearCase elements, the
config spec should insure that you are looking at the version that is
appropriate for your specific increment. Eclipse will read these files
each time it starts up. After switching the config spec, you should
perform a Rebuild All. Without it, you could have old class files that
are left from compiles under the old config spec.
> I appreciate your advice and it is valuble for the credability of eclipse.
> Regards,
> //Mikael
> Dave Wegener wrote:
> > Mikael Petterson wrote:
> > > Hi,
> > > A while ago I got some help from David Wegener (see below).
> > > I followed his instructions, thanks David, and I now have an environment
> > > setup for me.
> > > We use different versions of the same java source tree (using labels in
> > > the config spec). Each version is a release with specific functionality.
> > > Here are my follow-up questions:
> > > * Lets say that we have made a couple of releases and that we must go
back
> > > to release and make corrections ( not too unusual).The person making the
> > > correction does he/she have to make an import into the workspace again of
> > > the older version. That is, the most current proejct is contained in the
> > > workspace and when other versions is needed we import them?
> > My suggestion would be to create a separate workspace for making changes
> > to an old version. If you use the Rational plugin, you can then use the
> > Add existing WSAD project to workspace. This keeps your work separate and
> > helps prevent confusion when looking at code in the editor.
> > > * If we make any changes to the common perferences/settings in the dot
> > > files then we have to import project again or ....?
> > If you have the dot files under Clearcase control, then checking the files
> > in will make them available to everyone who can see them in their config
> > spec. Stopping and restarting Eclipse should pick and of these changes up.
> > > All help is very much appreciated.
> > > //Mikael Petterson
> > > Ps. Is this the right forum for my questions.
|
|
|
Re: More on Eclipse and ClearCase [message #153274 is a reply to message #153009] |
Wed, 05 November 2003 23:19 ![Go to previous message Go to previous message](theme/Solstice/images/up.png) ![Go to next message Go to next message](theme/Solstice/images/down.png) |
Eclipse User![Friend of Eclipse Friend](/donate/web-api/friends_decorator.php?email=) |
|
|
|
Originally posted by: matt_conway.nospam.i2.com
As far as I know, the Rational plugin does not work on platforms other
than windows. The plugin I wrote does have unix support, and you can
get it at:
http://sf.net/projects/eclipse-ccase
The most recent relased version does not work with eclipse 3.0, but the
CVS head does - I'll probably do another realse soon, but till then if
you need 3.0 support, you can either build it yourself, or check the
forums for the SF project since a user has packaged up an interim
release for 3.0
Matt
|
|
|
Re: More on Eclipse and ClearCase [message #153302 is a reply to message #153147] |
Wed, 05 November 2003 23:43 ![Go to previous message Go to previous message](theme/Solstice/images/up.png) ![Go to next message Go to next message](theme/Solstice/images/down.png) |
Eclipse User![Friend of Eclipse Friend](/donate/web-api/friends_decorator.php?email=) |
|
|
|
Originally posted by: neil.neil.swingler.name
"Dave Wegener" <wegener@cboenospam.com> wrote in message
news:bobcct$knb$1@eclipse.org...
> Mikael Petterson wrote:
>
> > I am using Solaris 8 and it seems like the plugin does not work with my
> > os?!
>
See Matt's post. His plugin works very well. I have assembled a build from
CVS head to work with 3.0M4:
http://neil.swingler.name/eclipse
> You should be able to work similarly to this second method. One thing I
> would recommend is to not have your workspace residing in your ClearCase
> view. Define you workspace to be in a separate location within your home
> directory. When you define your project, uncheck the Use Default Location
> and point to the ../boam directory. The workspace location is for
> personal preferences that really shouldn't be in ClearCase. The project
> location is what you want in ClearCase.
>
> As long as the .project and .classpath files are ClearCase elements, the
> config spec should insure that you are looking at the version that is
> appropriate for your specific increment. Eclipse will read these files
> each time it starts up. After switching the config spec, you should
> perform a Rebuild All. Without it, you could have old class files that
> are left from compiles under the old config spec.
>
There is no need to rebuild all. Refresh always works in my experience.
We also use multiple workspaces when working with multiple views.
You can import the file from the fully qualified location:
e.g.. /view/...
Another tip is to use the linked folder mechanism to build the class
files outside of the dynamic view. This made our builds 3 times
faster.
--
Neil Swingler
|
|
|
Re: More on Eclipse and ClearCase [message #153724 is a reply to message #153147] |
Thu, 06 November 2003 19:18 ![Go to previous message Go to previous message](theme/Solstice/images/up.png) |
mikael petterson![Friend of Eclipse Friend](/donate/web-api/friends_decorator.php?email=mikael.petterson%40ericsson.com) Messages: 73 Registered: July 2009 |
Member |
|
|
Dave Wegener wrote:
> Mikael Petterson wrote:
> > Hi Dave,
> > I am getting more confused.
> > Question 1.
> > ===========
> > I tried to download the clearcase plug-in from rational. When I click the
> > link you sent me I get the following in the browser window:
> > http://www-140.ibm.com/developerworks/rational
> > Then I click the following link:
> > Add-ins, plug-ins, and scripts
> > ClearCase
> > Plug-ins - Get the IBM Rational ClearCase SCM adapters for Eclipse 2.0 for
> > both Windows and Linux.
> > I am using Solaris 8 and it seems like the plugin does not work with my
> > os?!
> > Question 2
> > ==========
> > You suggest to have a separate workspace when I make changes to an old
> > version. I don't get the whole picture.
> > I have the following source tree in clearcase:
> > /vobs/rbs/sw/rbssw1/boam_subsys/src/se/ericsson.......
> > If I create the boam project one time and set workspace to
> > /vobs/rbs/sw/rbssw1/boam_subsys a directory called boam will be created and
> > it will contain .classpath and .project files ( all dot files). I make
> > elements of them all and check them in.
> > When a team member shall work with the project boam the config spec sets
> > which version that the user will "see". Then the user starts up the
> > eclipse with the -data /vobs/rbs/sw/rbssw1/boam_subsys as workspace and
> > imports the project boam.
> > Is this ok to do or what could be the drawbacks and what is your advice to
> > handle it ( please refer to my example).
> > Is there another way to make sure that the .project .classpath will be
> > loaded each time we work on a a specific increment (decided by config
> > spec.)?
> We work with ClearCase under Windows, so we use it a little differently.
> We have multiple views active at a time, each mapped to its own drive
> letter. In this mode, each view has its own directory structure and you
> can work on both simultaneously by bringing up different instances of
> Eclipse each pointing to a different workspace.
> I have also seen people switch which view is assigned to their workspace
> drive letter. This works as well. However, you have to make sure that
> you bring down eclipse prior to making the change. When you bring Eclipse
> back up, you need to perform a refresh for the project. The refresh will
> make sure that everything is built properly.
> You should be able to work similarly to this second method. One thing I
> would recommend is to not have your workspace residing in your ClearCase
> view. Define you workspace to be in a separate location within your home
> directory. When you define your project, uncheck the Use Default Location
> and point to the ../boam directory. The workspace location is for
> personal preferences that really shouldn't be in ClearCase. The project
> location is what you want in ClearCase.
Ok! I think working like method 2 is fine.
I will have a workspace for each increment in my home directory like this:
/home/eraonel/increment2
/home/eraonel/increment3
/home/eraonel/increment4 and so forth.
This is also true for my fellow members. So when they make an import of
the boam project ( for a let's say increment 3) it will be put in their
workspace
/home/userid/increment3.
The boam directory will contain all COPIES of dot files (.project and
classpath) that are checkedin in clearcase?
So if there is a change of let's say path to jar's (change in .classpath)
in a specific increment it means that all team mates must reimport the
boam project or .....?
Thanks again.
//Mikael
> As long as the .project and .classpath files are ClearCase elements, the
> config spec should insure that you are looking at the version that is
> appropriate for your specific increment. Eclipse will read these files
> each time it starts up. After switching the config spec, you should
> perform a Rebuild All. Without it, you could have old class files that
> are left from compiles under the old config spec.
> > I appreciate your advice and it is valuble for the credability of eclipse.
> > Regards,
> > //Mikael
> > Dave Wegener wrote:
> > > Mikael Petterson wrote:
> > > > Hi,
> > > > A while ago I got some help from David Wegener (see below).
> > > > I followed his instructions, thanks David, and I now have an
environment
> > > > setup for me.
> > > > We use different versions of the same java source tree (using labels in
> > > > the config spec). Each version is a release with specific
functionality.
> > > > Here are my follow-up questions:
> > > > * Lets say that we have made a couple of releases and that we must go
> back
> > > > to release and make corrections ( not too unusual).The person making
the
> > > > correction does he/she have to make an import into the workspace again
of
> > > > the older version. That is, the most current proejct is contained in
the
> > > > workspace and when other versions is needed we import them?
> > > My suggestion would be to create a separate workspace for making changes
> > > to an old version. If you use the Rational plugin, you can then use the
> > > Add existing WSAD project to workspace. This keeps your work separate
and
> > > helps prevent confusion when looking at code in the editor.
> > > > * If we make any changes to the common perferences/settings in the dot
> > > > files then we have to import project again or ....?
> > > If you have the dot files under Clearcase control, then checking the
files
> > > in will make them available to everyone who can see them in their config
> > > spec. Stopping and restarting Eclipse should pick and of these changes
up.
> > > > All help is very much appreciated.
> > > > //Mikael Petterson
> > > > Ps. Is this the right forum for my questions.
|
|
|
Goto Forum:
Current Time: Sat Aug 24 00:34:05 GMT 2024
Powered by FUDForum. Page generated in 0.03996 seconds
|