Maven site warning: The repository url 'https://maven-repository.dev.java.net/nonav/repository' is invalid

Question

I’m using Maven 3.2.3 on a multi-module project. I want to generate a checkstyle and findbugs report, so I have configured the following:

Answer 1

You have to configure the reporting plugin, so that it does not look for repositories, as it builts the report. in you pom add the following:

<reporting>
    <plugins>
        <plugin>
            <groupId>org.apache.maven.plugins</groupId>
            <artifactId>maven-project-info-reports-plugin</artifactId>
            <version>2.8</version>
            <configuration>
                <dependencyLocationsEnabled>false</dependencyLocationsEnabled>
            </configuration>
        </plugin>
    </plugins>
</reporting>

The reporting plugin throws the Warning even if you do not have set in your private or global maven settings or in any parent pom the "invalid" repositories. Maybe the plugin looks also for repository definitions in the dependencies of the project.

[WARNING] The repository url 'https://maven-repository.dev.java.net/nonav/repository' is invalid - Repository 'java.net' will be blacklisted.
[WARNING] The repository url 'http://maven.glassfish.org/content/groups/glassfish' is invalid - Repository 'glassfish-repo-archive' will be blacklisted.
[WARNING] The repository url 'https://maven.java.net/content/repositories/releases/' is invalid - Repository 'jvnet-nexus-releases' will be blacklisted.
[WARNING] The repository url 'https://maven.java.net/content/groups/public' is invalid - Repository 'release.maven.java.net' will be blacklisted.
[WARNING] The repository url 'http://repository.springsource.com/maven/bundles/external' is invalid - Repository 'spring-external' will be blacklisted.

Answer 2

I have maven project, where aggregation separate from inheritance: maven module inheritance vs aggregation. In order

mvn project-info-reports:dependencies

works, aggregate pom must inherit parent. To avoid blacklisted repository warnings, parent reporting must be configured as below mentioned, or it could be simple:

<properties>
    ...
    <dependency.locations.enabled>false</dependency.locations.enabled>
</properties>