EA 7.0 and clearcase

[Mr. Sanders]

Hello,

we observed some (in our point fo view) strange behaviour.

Szenario:

One EAP file
two parallel packages
both of them are under clearcase (cc) control.
both of them are checked out.

Now we move a class from package A to package B.
Now close EA.

If we compare the xml files of the packages A and B with its predecessor in CC, NO differences are found.

Thus we have problems checking them in, because CC is telling us, that they are identical.

When we reopen EA all changings are still there.
When we now check in packages via EA and compare the xml files, the changes are visible as differences.

It seems, that the changings are written to the eap file, and only a checkin via EA is possible.

Is that correct?

If yes, this is not usefull for team development.
We have to work with the clearcase tool to handle all the other artefacts belonging to the project too. And this has to be done with clearcase.

How can we enforce EA to write the changes into the XML file, so that we can checkin with CC?

Regards
Michael

[gtschech]

Michael,

ths xml files are generated when you start the checkin procedure, so you won't find any differences before you check them in.
On the other hand, it should not be a problem, for clearcase is not invoked until the new XMLs have been generated...

Guenter

[Mr. Sanders]

Hello Guenter,

thank your for your answer.

Of course this is a problem, because checkin AND labeling is done via clearcase scripts.

And now the user is forced to use the EA checkin mechanism.

If the xml file would be generated during modelling, the user coud choose.

Either use the EA mechanism, or use the EXISTING process and scripts from clearcase mechanism.

The way it is, it enforces to adapt the process to the tool and this never was good choice.

Is there a way to enforce the EA, the the xml files are directly modified without checkin from EA?

Regards
Michael