pretty generic project_key and title
ecki opened this issue · 8 comments
When I use versioneye:create in http://github.com/ecki/seeburger-vfs2 it creates 3 projects with pretty generic project keys like:
project_id=523a6cde632bac45e60037d2
project_key=maven2_pom_json_2
Also on the project homepage the name is "pom.json" which is especially a problem since the POM with the two sub modules result in 3 of those projects.
Yes. the project name is not the best. It should be the name or the artifact_id from the pom.xml. I double check that on the server side.
On the server we read via xpath //project/name from the pom.xml file. Is that set in your pom.xml file?
The filename is just the fallback solution.
Yes, it is set, see Line 10 here: https://github.com/ecki/seeburger-vfs2/blob/master/pom.xml#L10
Just found the error. If you upload a pom.xml VersionEye takes the name attribute. But the maven plugin uploads a pom.json which doesn't include the name. I will change that.
Cool, this works with 1.0.0-13 g35ae436822c7 from master
It's working with the current master of this plugin. But it is a breaking change, that's why I updated the version to 2.0.0. Following the semantic version concept :-)
What is the project key used for anyway? With a non-semantic project-id most "discussions" can be avoided and the visible title can be changed on the web.
Yes. The project_key is kind of redundant. We don't really need it. It is just a more readable alternative for the id.