| Author |
Message
|
| sammm |
 Posted: Wed Jan 29, 2014 3:45 am Post subject: IIB .project files and Source Control |
 |
|
Newbie
Joined: 13 Jun 2013
Posts: 8
|
In most other environments and projects you typically wouldn't checkin '.project' type files into source control.
i have a situation where i may need this but i wanted some advice first. We have some well developed flows (APPs , LIBs etc) on our 'trunk' and we need to branch to create another version.
However as our '.project' files aren't in SVN at the moment trying to then develop against that branch is problematic as we have no project defs for those flows to open.
So the question is do we simply check the .project files in or is there another way to use the branch code and recreate the projects in IIB - i've had a look but cant find a way.
Thanks
Martin |
|
| Back to top |
|
 |
| McueMart |
| Posted: Wed Jan 29, 2014 4:12 am Post subject: |
|
|
Chevalier
Joined: 29 Nov 2011
Posts: 490
Location: UK...somewhere
|
| Where I work we check the .project files in and I dont see any real problem with it. The .project files include dependencies to other projects in them which is pretty vital! |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Jan 29, 2014 5:42 am Post subject: Re: IIB .project files and Source Control |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| sammm wrote: |
| In most other environments and projects you typically wouldn't checkin '.project' type files into source control. |
Why not? What's the issue? I've typically done that.
| sammm wrote: |
| So the question is do we simply check the .project files in or is there another way to use the branch code and recreate the projects in IIB - i've had a look but cant find a way. |
I think the basic question is why in the other environments you don't check in project files. What leads you to that procedure?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| sammm |
| Posted: Wed Jan 29, 2014 5:46 am Post subject: |
|
|
Newbie
Joined: 13 Jun 2013
Posts: 8
|
with some other toolsets the project files have 'location' or library specific information within them making them non-portable across a dev team so it's often been the case that these sorts of files get 'ignored' SVN etc.
In this case i'm guessing thats not going to be an issue.
Thanks for the help,
Martin |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Jan 29, 2014 6:01 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| sammm wrote: |
| with some other toolsets the project files have 'location' or library specific information within them making them non-portable across a dev team so it's often been the case that these sorts of files get 'ignored' SVN etc. |
This is also true to some extent with the Eclipse project files, which IIB extends for good & sufficient reason. Developers need to be aware that, if they're working in this kind of shared environment, they do not modify their workspace in a way that makes it incompatible with those of their associates.
It's not my understanding SVN doesn't ignore .project files by default. It's not my rememberance that ClearCase et al ignore them either.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
|
|
