Skip to content

Conversation

@cstamas
Copy link
Member

@cstamas cstamas commented Aug 29, 2024

Fixing the method (there is one GA inside reactor), but this still does not fix the issue, now it fails elsewhere.

The problem in short is CI friendly version and its half-assed solution as model version "suddenly" change from file-activated models to effective ones.


https://issues.apache.org/jira/browse/MNG-8229

Fixing the method (there is one GA inside reactor),
but this still does not fix the issue, now it fails
elsewhere.

The problem in short is CI friendly version and its
half-assed solution as model version "suddenly" change
from file-activated models to effective ones.

---

https://issues.apache.org/jira/browse/MNG-8229
"Multiple modules with key " + a.getGroupId() + ':' + a.getArtifactId());
})
.orElse(null);
}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This does not change the behaviour, right ? What's the point ?

Copy link
Contributor

@gnodet gnodet Aug 30, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oh, it does change the behaviour, as if there's a single version, it will always be used, even if there's a version mismatch. I think that's wrong.
Multiple versions of the same GA inside a reactor is a supported (albeit rare) use case.
If the model pool is being filled, we can't rely on the existence of a single version (while the second may not have been read yet).

@cstamas cstamas closed this Aug 30, 2024
@cstamas cstamas deleted the MNG-8229 branch August 30, 2024 09:01
@jira-importer
Copy link

Resolve #9982

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants