Skip to content

Custom maven repository key leads to timeouts within custom repository structure #832

@DennisRippinger

Description

@DennisRippinger

When the plugin is executed within a strict nexus/artifactory environment it tries to download dependencies from custom repositories which are not reachable.

[INFO] --- jsonschema2pojo-maven-plugin:0.5.1:generate (default) @ myapp ---
Downloading: http://repo1.maven.org/maven2/io/grpc/grpc-core/maven-metadata.xml
Downloading: https://oss.sonatype.org/content/repositories/snapshots/io/grpc/grpc-core/maven-metadata.xml
Downloading: http://repo.spring.io/plugins-release/io/grpc/grpc-core/maven-metadata.xml

The parent pom defines two (with the oss-parent three) custom repositories. One of them is maven central with the key maven-central. I assume the default is explicitly listed regarding some problem with gradle (original commit).

I would suggest changing the key to central, which is the default key and usually handled in a nexus/artifactory environment as mirror.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions