Properties from a parent pom are not evaluated.

[Markus Malkusch]

I have a Java project which has this dependency:

<dependency>
    <groupId>org.slf4j</groupId>
    <artifactId>slf4j-api</artifactId>
    <version>${slf4j.version}</version>
</dependency>

${slf4j.version} is defined in its parent pom. In "My Projects" the version is not resolved.

[Robert Reiz]

Hi @malkusch. Many Thanks for your feedback. Currently we don't resolve multiple files via the GitHub/Bitbucket API, or any other API. If you want to take advantage of our GitHub/Bitbucket integration you have to put everything in 1 single pom.file.

For more complex Maven Projects we recommend to use the VersionEye Maven Plugin. Simply put this snippet into your parent pom.xml:

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

Run once

mvn versioneye:create

to create the project. Then execute

mvn versioneye:update

on each build on your CI system. That will resolve ALL your dependencies and update your VersionEye project with your dependencies.

There are different ways to keep your API Key secret. More to that in the documentation. And here is a complete list with all the configuration options.

Does that solve your problem?

[Markus Malkusch]

Currently we don't resolve multiple files via the GitHub/Bitbucket API, or any other API.

Well that's strange, cause somehow you do resolve it on the public view of such a package. On the public view of e.g. https://www.versioneye.com/java/de.malkusch.localized:localized/0.2.9 I see the dependency of org.slf4j:slf4j-api completely resolved.

[Robert Reiz]

@malkusch That's true. The difference between your project on GitHub and this project project here: https://www.versioneye.com/java/de.malkusch.localized:localized/0.2.9 is that the last one is deployed on a Maven Repository Server, like Maven Central. For everything what is on a Maven Repository we can resolve parent poms and even transitive dependencies via the maven-core or Aether project. GitHub doesn't has a Maven API, that's the difference. I'm not saying that it is impossible to resolve the parent pom via the GitHub API, just saying that it is not done yet. It's one out of many points on our roadmap. Until that feature is not implemented for the GitHub API I have to refer you to the VersionEye Maven Plugin.

[Robert Reiz]

I changed the status from Bug to Enhancement, because it works like expected.