Messages

1

Suggestions and Requests / Include reference data in Version Control

« on: April 02, 2007, 03:55:49 am »

All the available exports in the menu Tools->Export Reference Data... should also be available with version control. By this several users could add automatically common settings generated by others.

2

General Board / Re: Support ext in version control

« on: April 11, 2007, 01:57:28 am »

I see your point. To ease your angst why not talk to IBM and the open source development community at Eclipse? Perhaps Eclipse will support the same protocol as EA...

Because I pay for EA

I know, I'm not overly sympathetic (although certainly empathetic). Still, significant investment is involved, both products (EA and Eclipse) work with version control as is, and for both the effort could be well spent on other things.

Other things include for example, allow new protocols support.

Still, it might be worth making a request rather than voicing a complaint. There might be interest in either or both camps.

That's really the best idea! I will include this one there. By the way, I've done that for other stuff I would like to see in EA but I never got any feedback... that's a shame.

3

General Board / Support ext in version control

« on: April 02, 2007, 11:41:44 pm »

Why doesn't EA support ext in version control while accessing a CVS repository? AS you all know Eclipse supports this protocol, so it's very annoying to use several configurations for the same repository.

Is there any idea if this protocol will be supported?

4

Automation Interface, Add-Ins and Tools / RTF Image Size

« on: May 16, 2007, 02:12:34 am »

When exporting the RTF document with images if the image is bigger than the page or its place holder it doesn't get resized.

You can of course resize it after in the exported document, but is it possible to automatically resize the images for export?

5

Automation Interface, Add-Ins and Tools / Re: RaQuest relations problem

« on: April 17, 2007, 11:07:40 pm »

I've found that this only happens to users that already have the packages configured locally. If a new user arrives and configures everything from scratch what is imported from CVS is correct.

I'm not so sure that this is a bug anymore. This is probably related with the fact that when you update your packages you must always use the option "Always Import" instead of "Import Changes Only"  that appears when you do a checkout on some package.

This action never erases the previous relations from the local EAP and adds the new ones created that are on CVS, making the local Project have more relations than there are.

6

Automation Interface, Add-Ins and Tools / Re: RaQuest relations problem

« on: April 16, 2007, 11:35:37 pm »

Just submitted the bug report.

7

Automation Interface, Add-Ins and Tools / Re: RaQuest relations problem

« on: April 16, 2007, 07:23:30 am »

I've found that this problem occurs only when using the requirement matrix for inverting the relantionship. If you invert the relation in the matrix the previous one is not erased and the new one is added creating a ciclyc relation.

If after you right click the requirement and do "Delete Relationship..." and you select one of the repeated relations they both are deleted!

I think this is a bug.

8

Automation Interface, Add-Ins and Tools / Re: RaQuest relations problem

« on: April 16, 2007, 06:32:16 am »

Yes, the requirements are in separate controlled packages. But even in side the same package this happens.

For instance you have a packaged checked out that has requirements A,B and C. You make a relation between A and B and then you commit. Everybody gets this new relation if they check-out this package. Later on you decide to delete the relation between A and B and do a relation between A and C and you commit. When others check-out they have the relation A to B and A to C.

9

Automation Interface, Add-Ins and Tools / RaQuest relations problem

« on: April 16, 2007, 05:22:54 am »

Hi,

We are using EA with RaQuest for specifying system and software requirements. We are working on different packages, ex, Client, Server,... that version controlled. We didn't had any problem until now when we needed to correct a relation between two requirements. We decide that the relation was the other way around. So, we went to the matrix view and changed the relation direction.

The problem was that only the person that did the change saw the relation in the correct way. All the others anded up with a cyclic relation.

We tried deleting the existing relation and relate it to a different requirement, but what we only managed for the other users when they check-out, is a relation with the old requirement and the new one.

Bottom line there seems to be a problem when deleting or changing a requirement when the project is under version control. Only additions are sent to CVS the deletions are only local.

This is a serious problem, is there any work around.