[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [epf-dev] EPFC version control with Perforce

Hi John,
RMC has support for workspace method libraries, I think this feature was added just for this reason, to improve scalability. The way to do it with EPF is I think to use export and import of plug-ins of process content. Plug-ins can be locked. So it is possible to developed them in one library and use them (read-only) in another. Depending on the situation this can be enough. For example how often you need to integrate. When you want to integrate often it will be cumbersome. I don't have specific ideas on how to improve on it. Might be hard to do. In EPF in library.xmi ties everything together. When you use the workspace method libraries there is no single library.xmi file. That looks like a nice approach, unfortunately not possible with EPF.
Cheers,
Onno

On Thu, Jan 26, 2012 at 10:51 AM, Allen, John <John.Allen@xxxxxxxxxxxxxxxxxxxx> wrote:

Hi Onno,

Do you have any views on the best way to limit the changes to the shared files when you're managing an internal process library consisting of multiple practices etc.

For instance might it be better to actually consider the individual practices as separate configuration management items, maintained in separate areas, and imported into the real EPF environment when the developer is working on them, before plugin export-ing them back into their own VCS area when finished.

i.e. don't try and maintain a fully integrated process library in the VCS system but rather assemble the library at publish time by importing the various parts

How does IBM go about making this work at scale?

Thanks,

John



From: epf-dev-bounces@xxxxxxxxxxx [mailto:epf-dev-bounces@xxxxxxxxxxx] On Behalf Of Onno van der Straaten
Sent: 20 January 2012 19:02
To: Eclipse Process Framework Project Developers List
Subject: Re: [epf-dev] EPFC version control with Perforce

Hi Matt,
There is Eclipse plugin for perforce it seems. See http://www.perforce.com/product/components/eclipse_plugin. I think this could be what you are looking for. In a similar way you can use EPFC with Git or Subversion. See for example the discussion about Git now some time ago http://dev.eclipse.org/mhonarc/lists/epf-dev/msg03635.html.
HTH,
Onno

On Fri, Jan 20, 2012 at 12:00 PM, Austin, Matthew <Matthew.Austin@xxxxxxxxxxxxxxxxxxxx> wrote:

Hello EPF Dev,

Are there any plans to enable EPFC to integrate directly with Perforce for version control? Perforce is currently our preferred VCS, and we are currently only managing to do series development. We would like to develop in parallel as straightforwardly as possible.

How easy would it be to create a plugin that would allow Perforce to work 'natively' with EPFC, in a similar way to how CVS/ClearCase seem to?

In the absence of a specific plugin, we are left with trying to break down our configuration management as described in the document "Using EPFC with a VCS", which appears to suggest a rather convoluted method of organising version control.

Any advice on the best way to manage EPFC with Perforce would be greatly appreciated.

Regards
Matt Austin

Please consider the environment before printing this email.
 
This message should be regarded as confidential. If you have received this email in error please notify the sender and destroy it immediately.
 
Statements of intent shall only become binding when confirmed in hard copy by an authorised signatory. 
 
The contents of this email may relate to dealings with other companies under the control of BAE Systems plc details of which can be found at http://www.baesystems.com/Businesses/index.htm.
 
Detica Limited is a BAE Systems company trading as BAE Systems Detica.
Detica Limited is registered in England and Wales under No: 1337451.
Registered office: Surrey Research Park, Guildford, Surrey, GU2 7YP, England.


_______________________________________________
epf-dev mailing list
epf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/epf-dev


Please consider the environment before printing this email.
 
This message should be regarded as confidential. If you have received this email in error please notify the sender and destroy it immediately.
 
Statements of intent shall only become binding when confirmed in hard copy by an authorised signatory. 
 
The contents of this email may relate to dealings with other companies under the control of BAE Systems plc details of which can be found at http://www.baesystems.com/Businesses/index.htm.
 
Detica Limited is a BAE Systems company trading as BAE Systems Detica.
Detica Limited is registered in England and Wales under No: 1337451.
Registered office: Surrey Research Park, Guildford, Surrey, GU2 7YP, England.


_______________________________________________
epf-dev mailing list
epf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/epf-dev