Good morning and thanks for such an interesting history of Maven
evolution, Tamás. See below on discussion for next troubleshooting steps:
On 5/25/2023 2:23 AM, Tamás Cservenák wrote:
…
I really cannot tell who or what (my guess) corrupted the "update
check" related files.
This is the part o
Compare org.eclipse.aether.internal.impl.DefaultUpdateCheckManager, line
115:
public void checkArtifact( RepositorySystemSession session, UpdateCheck<
Artifact, ArtifactTransferException> check )
{
if ( check.getLocalLastUpdated() != 0
&& !isUpdatedRequired( session, check.getLocalLastUpdated(), c
Howdy,
That's interesting, but how came then into his debug logs the
"Determining..." line that IS in maven-compat:
https://github.com/apache/maven/blob/maven-3.9.2/maven-compat/src/main/java/org/apache/maven/repository/legacy/DefaultUpdateCheckManager.java#L76
T
On Thu, May 25, 2023 at 2:46 PM
Yes, in fact we use the Aether Resolver to resolve versions. And the message is
actually coming from org.eclipse.aether:aether-impl.
But I shall double check.
Best regards
Jarmoni
From: Slawomir Jaranowski
Sent: Thursday, May 25, 2023 2:45:46 PM
To: Maven Users
Hi,
Short hint
org.apache.maven.repository.RepositorySystem is not used for resolving by
versions plugin
It used
for repositorySystem.createPluginArtifact,
repositorySystem.createDependencyArtifact
https://github.com/mojohaus/versions/blob/master/versions-common/src/main/java/org/codehaus/mojo/v
Howdy,
So Garret, sorry for the long response, and exactly for its length I have
to say in advance: this will NOT solve your problem :(
For readers: context https://github.com/mojohaus/versions/issues/959
OTOH, it sheds some light on the "passive aggressive" stance of some Maven
Core developers
Hi,
as I wrote on SO... are you in a corporate environment and using a
repository manager ?
Kind regards
Karl Heinz Marbaise
On 24.05.23 18:04, Garret Wilson wrote:
I'm writing to this list on the advice of Andrzej Jarmoniuk on [Versions
Maven Plugin Issue
#959](https://github.com/mojohaus/vers
