What is relationship between eclipse .project file and SCM?
Hi folks.
I was reading this thread https://jazz.net/forums/viewtopic.php?t=18619
I realized that I don't fully understand how to deal with .project files.
Let's say I want to import files. I have to create a .project file so that eclipse can see the files and then I can use the import tool.
I can accept that. That's just how eclipse works.
But now what? Do I need to deliver that .project file? Why would I want to?
What relationship or relevance does the random .project file I created just for importing files into a component have to do with how that component will be used?
In the article I linked above, it says that I can "... remove the .project
file once you've put the file tree under source control. "
Is that removing the file from the repository (or hiding it or the equivalent of rmname in CC)?
What is the guidance on how to deal with .project files you create solely because eclipse needs a .project file as opposed to .project files you create for real work (if you know what I mean.)
Obviously RTC itself doesn't care about .project files since you can still share files in .NET or from the command line.
I'm sorry if this is confusing. I just realized today that I've been using RTC with eclipse but not fully understanding the relationship of the .project files when it comes to RTC.
Thanks
Andy
I was reading this thread https://jazz.net/forums/viewtopic.php?t=18619
I realized that I don't fully understand how to deal with .project files.
Let's say I want to import files. I have to create a .project file so that eclipse can see the files and then I can use the import tool.
I can accept that. That's just how eclipse works.
But now what? Do I need to deliver that .project file? Why would I want to?
What relationship or relevance does the random .project file I created just for importing files into a component have to do with how that component will be used?
In the article I linked above, it says that I can "... remove the .project
file once you've put the file tree under source control. "
Is that removing the file from the repository (or hiding it or the equivalent of rmname in CC)?
What is the guidance on how to deal with .project files you create solely because eclipse needs a .project file as opposed to .project files you create for real work (if you know what I mean.)
Obviously RTC itself doesn't care about .project files since you can still share files in .NET or from the command line.
I'm sorry if this is confusing. I just realized today that I've been using RTC with eclipse but not fully understanding the relationship of the .project files when it comes to RTC.
Thanks
Andy
2 answers
Whether or not you want to keep the .project file depends on whether you
want to use the Eclipse project views (like the project explorer or the
package explorer). If you do, then you'll want to keep that .project
file, so that when you load that tree into a sandbox, it is visible in
those explorer views. But if you just want to get the files onto disk,
and will then use non-Eclipse editors to perform modifications, then you
can either just "undo" the creation of the .project file before
delivering the "Share" change set (i.e. never put the .project file
under source control), or perform a subsequent change where you delete
(like a cleartool rmname) that .project file.
Cheers,
Geoff
On 8/3/2011 6:23 PM, amblerman wrote:
want to use the Eclipse project views (like the project explorer or the
package explorer). If you do, then you'll want to keep that .project
file, so that when you load that tree into a sandbox, it is visible in
those explorer views. But if you just want to get the files onto disk,
and will then use non-Eclipse editors to perform modifications, then you
can either just "undo" the creation of the .project file before
delivering the "Share" change set (i.e. never put the .project file
under source control), or perform a subsequent change where you delete
(like a cleartool rmname) that .project file.
Cheers,
Geoff
On 8/3/2011 6:23 PM, amblerman wrote:
Hi folks.
I was reading this thread
https://jazz.net/forums/viewtopic.php?t=18619
I realized that I don't fully understand how to deal with .project
files.
Let's say I want to import files. I have to create a .project file so
that eclipse can see the files and then I can use the import tool.
I can accept that. That's just how eclipse works.
But now what? Do I need to deliver that .project file? Why would I
want to?
What relationship or relevance does the random .project file I created
just for importing files into a component have to do with how that
component will be used?
In the article I linked above, it says that I can "... remove the
project
file once you've put the file tree under source control. "
Is that removing the file from the repository (or hiding it or the
equivalent of rmname in CC)?
What is the guidance on how to deal with .project files you create
solely because eclipse needs a .project file as opposed to .project
files you create for real work (if you know what I mean.)
Obviously RTC itself doesn't care about .project files since you can
still share files in .NET or from the command line.
I'm sorry if this is confusing. I just realized today that I've been
using RTC with eclipse but not fully understanding the relationship
of the .project files when it comes to RTC.
Thanks
Andy
Hi,
there is another possibler way to handle the .project files if you just want to load files on disk.
After the initial sharing of the data - which has to happen in an eclipse project unfortunately - you can choose to ignore (Team>Ignore) .project.
If you use the load option "Load the root folders of the components as projects" the data is loaded and dummy .project files are created. You can add those to the ignore ist, if they aren't already. This allows you to keep the .project files out of the SCM data but also allows you to load and use the files in SCM.
there is another possibler way to handle the .project files if you just want to load files on disk.
After the initial sharing of the data - which has to happen in an eclipse project unfortunately - you can choose to ignore (Team>Ignore) .project.
If you use the load option "Load the root folders of the components as projects" the data is loaded and dummy .project files are created. You can add those to the ignore ist, if they aren't already. This allows you to keep the .project files out of the SCM data but also allows you to load and use the files in SCM.