UNKNOWN for license in report for non maven central artifacts

Issue #360 open
Roman Ivanov created an issue

report - https://www.versioneye.com/user/projects/5504ca834a1064774400049a sevntu-checkstyle-maven-plugin 1.23.1 UNKNOWN UNKNOWN

https://github.com/sevntu-checkstyle/sevntu.checkstyle/blob/master/sevntu-checkstyle-maven-plugin/pom.xml

License is specified in proper format to my mind. Nuance is that artifact is not on maven central.

By design ? or some problem ?

Comments (8)

  1. Robert Reiz

    Hi @r_ivanov. The dependency is marked grey and the license is unknown because the whole dependency is unknown to VersionEye. Why is that package not published to Maven central? What's wrong with Maven Central? If configured correctly you can publish to Maven central with 1 command:

    mvn clean deploy -Dgpg.passphrase=
    

    On which repository server is published?

  2. Roman Ivanov reporter

    On which repository server is published?

    Custom repo. Custom repos are not a rare case. https://github.com/checkstyle/checkstyle/blob/master/pom.xml#L224

        <pluginRepository>
          <id>sevntu-maven</id>
          <name>sevntu-maven</name>
          <url>http://sevntu-checkstyle.github.io/sevntu.checkstyle/maven2</url>
        </pluginRepository>
    

    Why is that package not published to Maven central? What's wrong with Maven Central?

    One day it will be done. Not that simple as project require to pass verification and approval for a groupId and artifactId on Maven central. Release process need to be changed ...... All is doable but just no time to make it happen, due to high activity on main project - https://github.com/checkstyle/checkstyle/

    The dependency is marked grey and the license is unknown because the whole dependency is unknown to VersionEye

    Looks like this is by design, that is reasonable to some extend as you can not scan all other custom repos. If nothing you plan to improve now - please close the issue.

  3. Roman Ivanov reporter

    maven repository is working fine , example of usage - https://github.com/sevntu-checkstyle/checkstyle-samples/tree/master/maven-project it is also used in checkstyle project - https://github.com/checkstyle/checkstyle/blob/master/pom.xml#L225

    what you see is how github restrict access to hit web pages - not access to fylesystem view. But maven do not need it as it download files with certain name. https://github.com/sevntu-checkstyle/sevntu.checkstyle/tree/gh-pages/maven2/com/github/sevntu/checkstyle/sevntu-checks

    link that works in browser - http://sevntu-checkstyle.github.io/sevntu.checkstyle/maven2/com/github/sevntu/checkstyle/sevntu-checks/maven-metadata.xml

  4. Robert Reiz

    I tried to crawl the repository but it doesn't expose a Maven index like other Maven repositories. Also tried a HTML crawler but that is somehow blocked. Can you somehow expose a Maven index on that URL? Or just use Maven Central ;-)

  5. Roman Ivanov reporter

    Or just use Maven Central ;-)

    yes it is in plan to eventually appear on maven central.

    Can you somehow expose a Maven index on that URL?

    Maven took all required info from http://sevntu-checkstyle.github.io/sevntu.checkstyle/maven2/com/github/sevntu/checkstyle/sevntu-checks/maven-metadata.xml , so by content of this file maven generate strict links to jars http://sevntu-checkstyle.github.io/sevntu.checkstyle/maven2/com/github/sevntu/checkstyle/sevntu-checks/1.5.1/sevntu-checks-1.5.1.jar and other files (https://github.com/sevntu-checkstyle/sevntu.checkstyle/tree/gh-pages/maven2/com/github/sevntu/checkstyle/sevntu-checks/1.5.1)

    I ma not sure what "expose Maven index" mean, please clarify.

  6. Log in to comment