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

2021-04-11 Thread Igor Fedorenko (Jira) 


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

Igor Fedorenko commented on MRESOLVER-142:
--

Sorry, it's been awhile, I don't recall any details about this issue, feel free 
to close.

> maven does not honour configured  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
> Fix For: waiting-for-feedback
>
>
> 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)

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

2021-04-11 Thread Michael Osipov (Jira) 


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

Michael Osipov commented on MRESOLVER-142:
--

[~igorf], can you add more detail as requested last year?

> maven does not honour configured  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
> Fix For: waiting-for-feedback
>
>
> 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)

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

2020-10-16 Thread Michael Osipov (Jira) 


[ 
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 @@

   
 
-  dependency-parent
+  dependency
   dependency
   0.0.1
 
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 @@

   
 
-  dependency-parent
+  dependency
   dependency
   0.0.1
 
{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  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)