Introduce relative source path

[Martin Bohring]

Dear Sparxians,
please please introduce relative source paths.
When checking models and source into VCS's, it is possible to check
out those into another path depending on developer preferences or if its a different branch.

The local paths feature looks very much like an afterthought to me.
And it does solve the problem only partial.

Im sure almost everbody doing roundtripping would want this feature.
Just look at the hoops and loops peaple are suggesting in the discussion groups to get around that limitation.

I want to be able to check out the code, the model, update the code or the model, synchronize and check both back in without fiddling with local paths or replacing directory paths in exported XMI or resort to voodo.

[Frank Horn]

I agree. The local path mechanisms has its virtues, but at times it's rather clumsy, and an option to use relative paths would be nice.

Furthermore it's a pity (or a shame, or even an outrage) that there is no support for branching and tagging with version control. It's pest or cholera now: either you don't use version control from inside EA and can do whatever you like but cannot save nested packages as stubs, or you use it and are restricted to what EA supports.
Which does not include tagging and branching: No support from inside EA, and if you do it outside you end up with EA models the nested packages of which point to the trunk of your VC repository and you have to fiddle with the xmi file to make them point to subpackages you created inside a tag or branch.

[Thelonius]

It's pest or cholera now

  Good metaphor. I'll plagiarize that one, if you don't mind.

[Frank Horn]

I'll plagiarize that one

No copyright there. It's just a common expression in German.

[Jens Nötzold]

I want to be able to check out the code, the model, update the code or the model, synchronize and check both back in without fiddling with local paths or replacing directory paths in exported XMI or resort to voodo.

Moreover, the "local paths feature" (well its more a workaround than a feature) doesn't help for model elements having links to local files. So I would suggest that every link to the local filesystem may be stored relative to the current model.
(Currently EA is not applicable in a distributed development environment. A model with links to the outside must be diverged per user an per machine).

Has somebody already raised a feature request?

[Eve]

So I would suggest that every link to the local filesystem may be stored relative to the current model.

Which leaves you with absolute paths only if you have a DBMS connection.  At least local paths still works for DBMS connections.

[Philipp]

I've been asking for that feature for years now - this is something that *immediately* starts annoying pretty much everybody I worked with in a team right from the start - the models just aren't portable (and "local paths" is just a hack IMO). As a result, I not only suspended my upgrade but also stopped recommending the product to my customers which is a pity because I really love EAs usability.

With regards to the announcement of EA 7.5 that was the single thing I looked for but I guess I'll have to sit this one out, too.