artifact version as property does not work for maven

[Gerd Aschemann]

If the version of a maven dependency is given as maven property VersionEye complains about an unknown version, e.g., https://www.versioneye.com/user/projects/555209a206c3183055000123. It should evaluate the POM and replace the property with its current value.

[Robert Reiz]

@ascheman I just double checked it. "lombok.version" version is not defined in the pom.xml, that's why VersionEye is not finding it. I guess it is defined in the parent pom.xml. Right? Currently VersionEye does not resolved dependencies/variables through multiple files via the GitHub API. For Maven multi module projects I recommend to use the VersionEye Maven Plugin.

Simply add this to your parent pom.

<build>
  <plugins>
    <plugin>
      <groupId>com.versioneye</groupId>
      <artifactId>versioneye-maven-plugin</artifactId>
      <version>3.4.0</version>
      <configuration>
          <apiKey>my_secret_api_key</apiKey>
      </configuration>
    </plugin>
  </plugins>
</build>

And run this to create the project initially:

mvn versioneye:create

And then this on each build on your CI system:

mvn versioneye:update

If you have a default license whitelist on VersionEye you can check license violations with this goal:

mvn versioneye:licenseCheck

This goal will break you build if there is a license violation. That means if you are using a dependency with a license which is not on your license whitelist, your build will fail. But that's a good thing because it prevents you from pushing GPL to production ;-)

There are several ways of keeping your API Key secret. See all config options here. And let me know if you need more help with the setup.

[Robert Reiz]

I close this ticket, because it's the expected behaviour. VersionEye will support resolving dependencies/variables through multiple files via the GitHub API, but not sure then. Currently all Enterprise clients are using the VersionEye Maven Plugin on their CI systems and that works fine.