Book a Demo

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - Simen

Pages: [1]
1
General Board / Re: 7.0 Beta
« on: May 21, 2007, 09:52:13 pm »
Is there a full backward compability between 6.5 (806) and the 7.0 Beta Release ? And how about the Visual Studio Integration. Is it ok that some developers use the 3.0 Beta version and others the 2.1 version to access the same model and Visual Studio Solution ?

We currently use 6.5 with SQL Server 2005 as repositry and VS Integration 2.1 and would like to test the new EA/VS Integrate on some pc's whilst most developers will still be using EA 6.5/VS Integration 2.1

2
Bugs and Issues / Re: Checked out package overvritten by GetAllLates
« on: March 30, 2010, 11:12:46 pm »
Correction. Turns out that I had to add a view to the model root node, then I could drag and drop the package in question. However the Import Model Branch doing GetAllLatest still apply.

3
Bugs and Issues / Re: Checked out package overvritten by GetAllLates
« on: March 30, 2010, 07:43:50 pm »
And yet another problem in the same are. I wanted to move a package (with subpackages) from one model root node to another. As drag and drop between model root nodes doesn't work I decided to export the package as a model branch and the import the model branch to the new model root node (in the same repository).

What happened when I tried to import was that EA started a GetAllLatest as part of the import. As you cannot cancel that process I decided to kill it after some time to prevent loss of packages checked out but not checked in.

Now it seems that work in progress for one package (checked out by another user) is lost as that package was retreived before I got to kill the GetAllLatest process. The help text does not mention that GetAllLatest is an implicit part of importing a Model Branch. Really need Sparx to look into this issue.

4
Bugs and Issues / Re: Checked out package overvritten by GetAllLates
« on: March 30, 2010, 06:19:33 pm »
Bug submitted. Thanks for commenting Roy.

5
Bugs and Issues / Re: Checked out package overvritten by GetAllLates
« on: March 30, 2010, 12:46:56 am »
Thanks all for your responses. Would like to see any Sparxians comment on this though. And one more thing we discovered. When importing a new version controlled package to a local eap through GetAllLatest, any elements in the given package of type 'Packaging Component' ends up as a standard Package...

6
Bugs and Issues / Re: Checked out package overvritten by GetAllLates
« on: March 18, 2010, 07:34:05 pm »
And forgot to mention, we're usinig EA 7.5.850 and CollabNet SVN Client 1.6.6. Also noticed that in the EA 8.0 B2 release notes there's a fix where resynch is updated to handle packages checked out by other users, could this be our problem?

Thanks

7
Bugs and Issues / Checked out package overvritten by GetAllLatest
« on: March 18, 2010, 07:44:06 am »
Hi, today we discovered a potential critical problem with version control. We have a SQL Server Repository configured with subversion version control. We've also got User Security configured.

What happened was that user A had a package checked out and was working on that package.

User B ran a combination of resynch package status and GetAllLatest and after checking in other packages from a local eap repository used for working out of office.

Then we discovered that user A's package had been overwritten (he got a message about the model was changed and press ok to update). And he lost all his work since last checkin. And, the package changed status from checked out to check in. The latter changed when he did a resynch VC status but all changes was still gone.

We've immediately stopped all usage of local Copies and GetAllLatest until issue is resolved. Seems like a bug or design flaw. The GetAllLatest was set to import only changed packages.

I'm aware of the note in the help file regarding resynch and packages checked out by other users, but our issue is not the same as noted in the help file from my understanding.

Anyone experienced the same behaviour?

Pages: [1]