Author Topic: How use version control for Project Task, ... (Read 4265 times)

jiri.jansta · « **on:** November 28, 2007, 01:11:25 am »

Hi,
I use EA, 7.0.818 and version control (subversion) for all models from project. I don't know, how use version control for System (Project Tasks, Project Issues, Project Glossary). I know use versin control on package, but System isn't package. Than You for Idea.

JJ

thomaskilian · « **Reply #1 on:** November 28, 2007, 04:24:21 am »

If you don't use packages, how do you structure your project then

JohnDoe · « **Reply #2 on:** November 28, 2007, 10:54:35 am »

I guess this guy has the same problem that I have: If you use System panels (project tasks, project issues etc.), they are not saved in packages - they are System issues, not package or element issues.

These project issues/tasks/risks thing has some unfortunate effects. One of them is not being able to save them in a version control.

Regards
Bernd

thomaskilian · « **Reply #3 on:** November 28, 2007, 10:57:25 am »

Can't you save them as reference data and put them under VC?

JohnDoe · « **Reply #4 on:** November 28, 2007, 11:34:05 am »

There is always a workaround, but the question is, why are all those panel "project issues", "project tasks" etc. in the system, if you cant use them properly ??

All these panels are there, you can enter something, but even the documentation says, that there is no meaningful report available and you should use the Automation Interface to get your data out.

These panels are not very helpful at the moment.

Regards
Bernd

Arthur · « **Reply #5 on:** November 29, 2007, 01:56:58 am »

I guess JJ and Bernd has the same problem as we have. We use controlled packages for sharing models. The packages are version controlled in subversion. Every user has his/her own eap file. The downside of this is that there is no way (that we have heard of) of sharing issues, tasks, glossary etc. Exporting/importing reference data every time something is added or changed is far too cumbersome.

thomaskilian · « **Reply #6 on:** November 29, 2007, 02:25:58 am »

Quote

There is always a workaround, but the question is, why are all those panel "project issues", "project tasks" etc. in the system, if you cant use them properly ??

All these panels are there, you can enter something, but even the documentation says, that there is no meaningful report available and you should use the Automation Interface to get your data out.

These panels are not very helpful at the moment.

Regards
Bernd

Hi Bernd,
I asked the same question years ago when I started with EA. I came to the conclusion to not make use of these "gimmicks" and to stick with (more or less) proper UML elements which I Tag accordingly. Some of EA's concept had been developed out of the blue and not been removed later for "compatibility reasons" I guess.

The best advice I have: do not use each and every feature unless you have very good reason (you likely had, but now you have the headache).

JohnDoe · « **Reply #7 on:** November 29, 2007, 02:44:09 am »

Hi Thomas,

thanks for this important tipp !
It is a little boring to use features and fill in data, which shows up as a dead end.

@Sparx-People:
Could you please either take out those features or add some more functionality, please !?

Regards
Bernd

Jan Pacovsky · « **Reply #8 on:** November 29, 2007, 05:03:10 am »

I tried to solve this issue about one year ago. The conclusion was that "project related stuff" in EA (project issues, tasks, glossary, ...) cannot be synchronized with version control. You can only synchronize packages.

One possible solution was:
1) Each user has its own private model (eap replica) under version control.
2) There is one central shared model with project related stuff and each user synchronizes his/her replica in order to have up-to-date project related stuff.

Sparx Systems Forum

News: