Sparx Systems Forum
Enterprise Architect => Suggestions and Requests => Topic started by: Bart Reyserhove on March 07, 2008, 09:51:48 pm
-
I have been testing the BETA 1 this morning, and especially the new version control feature: Add branch to version control.
btw, I tested this in combination with SVN.
Some remarks
1) Adding a tree of packages works nice and every package is exported separately but it seems that too much is exported to SVN. I see more directories in SVN than I have packages. Furthermore the naming of the directories in SVN is terrible. I see names like: "ea0","ea1", "ea2", instead of for example the name of the packages.
2) Deleting a checked out package does not work. I need to check in the package first? I think this behavior is weird, but I'm not sure it is specifically related to the beta.
3) I would love to have a feature: Check out branch. This could be specifically useful when merging baselines. Otherwise I have to manually check out each package...
4) Deleting packages: the corresponding files and directories in SVN are not deleted.
Bart
-
Hi Bart,
First, this should go into a bug report directly to Sparx. You'll find the correct link on the beta download page.
Here are some things to think about.
Are you having this problem with beta 1 (build 825) or beta 2 (build 826)? Your thread title and introductory line mention both.
1: The issue with package count looks like it needs to be addressed. I do not know if the naming system is something EA does or not.
2: The delete function might be just the way it works, I really don't know. Perhaps the philosophy is that you cannot delete what's not there, and it isn't really there until it is checked back in...
3: I think this feature has been requested before. On large models this can be a real PITA.
4: As mentioned above.
Remember that it is now the weekend in the Land of AUS, but get the report in now. Sparx has to make a decision on whether another beta build is needed before production. If you are using beta 2 - or if you've seen bugs in beta 1 that are still in beta 2 - then we definitely want to get them fixed before they get into production!
David
-
I created bug reports for the issues.
1) The naming system is something EA does, but it just gives meaningless names instead of e.g. using the name of the package.
2) It might be "by design" but it means that anyone can delete a locked package...
3) Indeed a PITA and strange enough you do have "Check in branch" :-?
-
I hear you Bart! On all three.
EDIT: But see Michael's post below.
-
1) Adding a tree of packages works nice and every package is exported separately but it seems that too much is exported to SVN. I see more directories in SVN than I have packages. Furthermore the naming of the directories in SVN is terrible. I see names like: "ea0","ea1", "ea2", instead of for example the name of the packages.
This behaviour is by design, and only applies to "Add branch to Version Control". The rationale is that FAT32 filesystems have a limit of 65,534 files per directory, so 16 directories (ea0 - eaF) increases the storage capacity by 16 (the moment we say to ourselves "Who would have that many files?" is the moment someone posts on the forum saying that its a problem :P).
Package files are named using the last 12 characters of the GUID as it is the only unique identifier that can be used (you can have many similar named packages in a project, or even within a package itself). This isn't normally a problem if you're adding files individually (as you can just change the filename), but in a batch process everything needs to be unique to be automatic.
2) Deleting a checked out package does not work. I need to check in the package first? I think this behavior is weird, but I'm not sure it is specifically related to the beta.
The reason behind this is that if you local delete an item that is checked out to you, you will still retain the checkout lock. Consequently noone will be able to checkout the file themselves (as it is checked out to you), and you won't be able to check it back in as you've deleted it.
3) I would love to have a feature: Check out branch. This could be specifically useful when merging baselines. Otherwise I have to manually check out each package...
This functionality is the natural complement to "Add Branch to VC" and "Check In Branch" and is in the development pipeline.
4) Deleting packages: the corresponding files and directories in SVN are not deleted.
When you delete version controlled things from EA, you're only deleting them from your local project, as other people may still want the package to exist (Remember that in a version controlled situation all users have their own EAP files which they are free to customise to their own liking). Currently the only way to completely remove a package from version control is to do it manually through the version control system.
-
Thanks for the answers, they certainly clarify things.
About the "check out branch". You say that it is in the development pipeline. Any chance that this makes it to v7.1?
-
Bart,
I know Check In Branch made it, but I'm not sure about checking out.
There was some talk about this in a post or two, both since 7.1 production was released. [But the thread itself might have been older.] Search the forum and you should find them.
David