Exchange of components between different eap files

[Daniel Graupner]

Hello

I have a eap file with some general components that I want to reuse in other eap files.

One method I found is XMI Import/Export, this works fine but it is very difficult to merge changes.

I also tried baselines/Load From other Files/Load from Eap but the baselines from my eap with the components did not show up.

How can I achieve this kind of modularity?

Regards
Daniel

[qwerty]

If you want a common resource save that at a place where all members have access (preferably using a VC system). When you set the desired package as Controlled you can eventually reload/update this common resource.

But: things like that need a deep thought. Configuring EA for team work is a task not to be underestimated! Plan at least a weak to read about all possibilities (Sparx has a lot of resources). Then plan some more weeks to try out the various variants to find out the one that suits you.

You will not find the right answer to your question here on the forum.

q.

[Daniel Graupner]

I do not want to setup team environments nor do I want to include a Versioning System. I read about all the possibilities and decided to only use EA's built in audit and baseline support.

So vereything I want is to exchange and manage/update a component from one eap file to another. Without multi user and shared access, its only me using the model.

[Geert Bellekens]

Daniel,

If you are sure it's only you, and you have a strong discipline then you can use manual xmi import/export to synch the component between your two .eap's.
But even in this scenario I would setup an integration with SVN just to manage that. Since EA uses exclusive checkouts, it prevents mishaps. (like updating the component in both .eap simultaniously, or importing the wrong xmi file, or...)

Geert

[Daniel Graupner]

Yes, I thought about using the SVN integration. But the EA Handbook has some good reasons why not to use this approach. Hmm, seems I have to find my way by trying things out.