maven-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Martin Gainty <>
Subject Re: Confused about resolution of test-jar to WorkspaceRepository
Date Sat, 25 Aug 2018 12:43:15 GMT

 you can disable release/snapshot lookup for any repository from your settings.xml :
<!-- This will disable repository lookup that comesfrom transitive
        <!-- and that will make the build failed because of 403 HTTP error. -->

nexu/pom.xml at master · nowina-solutions/nexu · GitHub<>
GitHub is where people build software. More than 28 million people use GitHub to discover,
fork, and contribute to over 85 million projects.

if you need finer grain control over repositories you may want to consider repo-manager:
nexus, cloudera, artifactory
From: lorenzo <>
Sent: Friday, August 24, 2018 12:51 PM
Subject: Confused about resolution of test-jar to WorkspaceRepository


I'm working on a Maven plugin[0] that interacts with the maven plugin
API v3.3.3.

The problem I'm encountering is that of these[1] two dependencies, the
former is resolved as a belonging to a RemoteRepository, whereas the
latter (the test-jar) to a WorkspaceRepository.

I don't understand why that is. Both are hosted on a remote Maven repo.

Is there something intrinsic in the test-jar type, or the test scope,
that causes the ArtifactDescriptorResult.getRepository()[2] method to
return objects of different classes?



To unsubscribe, e-mail:
For additional commands, e-mail:

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message