EA and Subversion : n-1 release?

[spxea]

Hello,

I use EA 7.1 and svn (1.4.6).

I put different packages of an EA model under svn. All seems to be ok: I can check-out, check-in without any pb.

Now I would like to get release n-1 of a package, and make it as the new release (so n+1) of this package (i.e. I would like to go back to release n-1 of this package, because I realized that release n was bad).

I tried to use "File History" : I can find release n-1, I can get it with "Retrieve" button. But the trouble is it is in read-only mode (no check-out). So that, once retrieved, I ca not modify it, and I can not to a "Check-in" of it to make it as the new release (because the Check-in command is grayed).
I tried to do a Check-out before the File history, but in that case the Retrieve button of File history is grayed.
I tried to Export/Import a branch, but still the n release (not n-1).
(And when I simply do a Check-out, only the latest release is checked-out (same thing with Get Latest)).

So could you please tell me how to proceed?

Thanks.

[aap]

I had the same problem.

I used another Subversion client (TortoiseSVN) to revert the XMI file of the package, and then used "Get Latest" to update the model.

It seems to have worked OK.

Andy

[spxea]

Yes, thanks, manually it works.

Anyway, it is very strange not to be able to do this kind of operation from within EA isn't it?

[Frank Horn]

There's not much by way of version control that can be done from inside EA. If I haven't overlooked anything, all you can do ist create e new package in an existing folder, check it in and check it out.

No creating folders, no reverting, no branching and tagging. All these have do be done with a full blown version control client.

But then of course to enable all these things EA, supporting various version control systems, would have to be some kind of universial VC client. Since these are things I don't have to do all the time, I can live with the restrictions and prefer Sparx to concentrate on more severe shortcomings of EA.

[thomas.kilian]

This is wrong by design I think. There are so much pretty clients out there (e.g., Tortoise) that I can't understand why EA is putting parts of that into the product. Instead there should be a mechanism to store/load XMI independent (with stub!) so I can do all versioning stuff outside EA.

Feature mania. IOW scrap!

[Frank Horn]

I agree that the possibility to save subpackages as stubs without using EA's version control features would be a great feature. Alternatively branching an tagging should be added to the in-built version control features.

Now if you have nested controlled packages and want to copy the top package to a branch or tag, you have to do it with an "outer" VC client. The subpackages' VC path however will still point to the trunk, so you have to edit all the XMI files (or transform them) to move all their VC paths to the branch/tag.

[thomas.kilian]

Although I'm not a *NIX freak I like the way many things are done there (quite the OO way): have a number of stable base products with almost no extras and combine them to get more power.

The M$ way (which is obviously the one Sparx also took) is to put everything in one product. The result is of course scrap like Word. A product where more than 90% of the users only use less than 10% of the features but (OMG!) pay for all the useless stuff too. What a crazy world!