locate projects with manipulated project names

[pepov]

We have some projects where we have modified subproject names (we add a prefix) and it would be nice if we could support it in the pride as well. Absolute paths are kind of ugly, but at least works precisely.

My questions:

• do you know a better option? (I know we shouldn't mess with project names)
• how can I make this change backward compatible? (I had issues using pride 0.9.+ with pride-plugin 0.6.+)
• what kind of tests should I add/extend?

[lptr]

Hey, thanks for the patch. I think this is a valid use-case that Pride should support. It looks to me that your solution is in the right direction.

I'd like to ask for a couple of changes:

• please use tabs instead of spaces
• let's not use absolute paths: try relativizing the path like this

About the compatibility issue: Pride 0.9 is not compatible, unfortunately, with previous versions. You need to use Pride plugin 0.9+ to work with Pride 0.9. I'll try to minimize breaking changes like this in the future, but currently agility was more important. For now I'd recommend upgrading to Pride 0.9.2 across the board.

One of the ways to stay more compatible is to split off the project model extraction from the Pride plugin: https://github.com/prezi/pride/issues/94

About tests: there aren't much, as you can see. It would be awesome if you could contribute some nice tests, for this or any other part of the tool. :)

[pepov]

• Ok I was too blind to see this relativize thing, I will fix it.
• Spaces were already there, my commit just replaces them with tabs, as I saw it beeing used everywhere else.

[lptr]

Ah, sorry about the spaces then. I'll fix those after we've merged this pull request.