[
https://issues.apache.org/jira/browse/MRESOLVER-146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17228279#comment-17228279
]
Michael Osipov commented on MRESOLVER-146:
------------------------------------------
This is a very good example for a very bad versioning scheme we cannot help
with. Publication dates cannot be trusted also because you could have the
following release order: 1.1.0, 1.1.1, 1.2.0, 1.1.2, 1.1.3, 1.2.1, 1.3.0.,
1.2.2, etc. The date will fool you.
The the information must be a transport-agnostic metadatum otherwise I see no
chance, it has to be carried through ALL layers. Optional or not, it has to be
implemented somehow. The only option I see is something like a {{.date}} side
file for signatures or checksums.
I rather recommend to inspect {{project.build.outputTimestamp}} from a
project's POM. This will give you the information you need, everything else is
just unrealisting for the time to come.
> method to get artifact publication date
> ---------------------------------------
>
> Key: MRESOLVER-146
> URL: https://issues.apache.org/jira/browse/MRESOLVER-146
> Project: Maven Resolver
> Issue Type: Task
> Reporter: Th Stock
> Priority: Major
>
> I'm looking for a method to get the date of artifact publication in
> org.eclipse.aether.RepositorySystem
> e.g.
> "org.apache.maven.resolver" % "maven-resolver-api" % "1.6.1" => 2020-10-02
> 18:05
> https://repo1.maven.org/maven2/org/apache/maven/resolver/maven-resolver-api/1.6.1/
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
