"My Projects" list should include branch+filename for GitHub projects

[Sean Flanigan]

As a result of some problems with the GitHub import process, I had a number of duplicate projects in My Projects. Trying to clean them up was especially difficult because many of them were called things like zanata/zanata-common, which is the name of a GitHub repo containing multiple pom.xml files (different Maven modules). Some of them were actual duplicates (same filename), others were just different files in the same GitHub repo.

If the "My Projects" list were to include the branch name and the filename (or the Maven module name), it would make a lot more sense and be easier to use.

[Robert Reiz]

@seanf What is your username on VersionEye? And is it a Maven Multi Module Project you try to track with VersionEye? For multi module projects please use the Maven Plugin here: https://github.com/versioneye/versioneye_maven_plugin
The plugin supports different naming strategies as well. It's meant to be executed on your CI system on each build. Let me know if you need support with that.

[Sean Flanigan]

@reiz My VersionEye username is seanf. Yes, it is a multi-module project.

I know the VersionEye Maven plugin exists, and I guess I now know why, but I was hoping I could quickly set up an automatic, self-updating, link to the project on github, without the hassle of working out the Maven plugin, API keys, or which particular CI job should actually talk to VersionEye. (I had been using the URL feature to link to the pom.xml files on raw.github.com, but that of course is a clunky approach, and I don't think it auto-updates, which is why I switched to the GitHub option.)

[Robert Reiz]

@sean If it is a multi module project you have to use the VersionEye Maven Plugin.

The problem with multi module projects is that the dependencies are distributed over multiple files. Resolving that via the GitHub API is kind of an overkill! In order to correctly parse the dependencies we would have to checkout the complete repository and compile everything on our servers. And if you depend on a dependency in a private repository it would not work at all. That's why we have the VersionEye Maven Plugin. It runs on your machine and only sends the resolved dependencies to the VersionEye API.

The setup is easy. Just add this to your parent pom.xml

    <plugin>
        <groupId>com.versioneye</groupId>
        <artifactId>versioneye-maven-plugin</artifactId>
        <version>3.2.1</version>
        <configuration>
          <apiKey>YOUR_API_KEY</apiKey>
        </configuration>
    </plugin>

Run this initially to create the project on VersionEye:

mvn versioneye:create 

And run this on each build on your CI server:

mvn versioneye:update 

Here is a YouTube video which shows how I setup a multi module project: https://www.youtube.com/watch?v=JPVEuqGHbeU.

[Sean Flanigan]

Thanks @reiz, I'll give that I try if I get a chance.

[Robert Reiz]

@seanf I close this ticket because there is no activity here since a while. Feel free to re open it or to open a new one.