[jira] [Commented] (MRESOLVER-142) maven does not honour configured in some cases

["Michael Osipov (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/MRESOLVER-142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17215684#comment-17215684 ] 

Michael Osipov commented on MRESOLVER-142:
------------------------------------------

I had to apply the following patch to make the project run:
{noformat}
diff --git a/module-a/pom.xml b/module-a/pom.xml
index 6c1144b..8fd4fa1 100644
--- a/module-a/pom.xml
+++ b/module-a/pom.xml
@@ -8,7 +8,7 @@

   <dependencies>
     <dependency>
-      <groupId>dependency-parent</groupId>
+      <groupId>dependency</groupId>
       <artifactId>dependency</artifactId>
       <version>0.0.1</version>
     </dependency>
diff --git a/module-b/pom.xml b/module-b/pom.xml
index 19045cb..a30b049 100644
--- a/module-b/pom.xml
+++ b/module-b/pom.xml
@@ -8,7 +8,7 @@

   <dependencies>
     <dependency>
-      <groupId>dependency-parent</groupId>
+      <groupId>dependency</groupId>
       <artifactId>dependency</artifactId>
       <version>0.0.1</version>
     </dependency>
{noformat}

It is not fully clear to me what the bug is. You understanding is that the repo which loaded dependency-parent for module a should not be visible to module b under no circumstances?

> maven does not honour configured <repositories> in some cases
> -------------------------------------------------------------
>
>                 Key: MRESOLVER-142
>                 URL: https://issues.apache.org/jira/browse/MRESOLVER-142
>             Project: Maven Resolver
>          Issue Type: Bug
>          Components: resolver
>            Reporter: Igor Fedorenko
>            Priority: Major
>
> There appear to be a bug in artifact descriptor cache implemented in aether DefaultDependencyCollector. The cache allows use of cached descriptors  when descriptor parent(s) are not accessible from any enabled repository. 
> This is particularly problematic during multithreaded builds, where timing of individual module project builds is not guaranteed, and the invalid artifact descriptor cache implementation can result in infrequent and hard to troubleshoot dependency resolution failures.
> I'll provide small standalone example project that demonstrates the problem shortly.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)