Wrong checksum in mulesoft maven repo for 2.10.0

28 views
Skip to first unread message

Amit Singla

unread,
Oct 16, 2019, 1:22:41 PM10/16/19
to jackson-user

The checksum is wrong on all files in the below maven repository. This is blocking to use this latest version.

https://repository.mulesoft.org/nexus/content/repositories/public/com/fasterxml/jackson/core/jackson-annotations/2.10.0/

Any idea how to get this fixed?

Regards, Amit

Tatu Saloranta

unread,
Oct 16, 2019, 1:28:21 PM10/16/19
to jackson-user
I think you will need to reach out maintainers of that Repo. They will
probably need to do hard sync from Maven Central to get consistent set
-- by default things are write-once, I think, to prevent accidental
mutation of artifacts. For this admin privileges are likely needed.
But I think they have had to do this occasionally.

The root cause in this case was that due to some issue with Sonatype's
OSS repo, incomplete set got through, and initial fix then pushed
inconsistent checksum files. This did get resolved, but it is likely
that sync by other repos occurred in the meantime.

-+ Tatu +-

Amit Singla

unread,
Oct 17, 2019, 6:56:16 AM10/17/19
to jackson-user
Not sure how to reach this repo out. Anyway is there any plan for next release 2.10.1 or something?

Guido Medina

unread,
Oct 17, 2019, 7:11:09 AM10/17/19
to jackso...@googlegroups.com
Hi Amit,

Not sure if this can help but can you try clearing your ${user_home}/.m2/repository/* ? you can simply delete recursively everything in there,
the downside is that every single jar will be downloaded again; that might help getting a consistent pom + checksum.

Guido.

--
You received this message because you are subscribed to the Google Groups "jackson-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jackson-user...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jackson-user/d61fdd90-6f4f-4013-a8ef-04334f03016f%40googlegroups.com.

Guido Medina

unread,
Oct 17, 2019, 7:13:18 AM10/17/19
to jackso...@googlegroups.com
Actually what I suggested won't help, maybe set the MuleSoft repo as a cache repo and not as main, meaning that you have to make Maven use the central first and then fallback to that other repo.

Tatu Saloranta

unread,
Oct 17, 2019, 1:01:00 PM10/17/19
to jackson-user
On Thu, Oct 17, 2019 at 3:56 AM Amit Singla <amitsi...@gmail.com> wrote:
Not sure how to reach this repo out. Anyway is there any plan for next release 2.10.1 or

Have you tried googling? Looks like this:


might help.

If anyone else has contacts with Mulesoft, help would be appreciated.

 
something?

Eventually, yes. There are a few reason why this is important: turns out that sorting of versions is also problematic (many systems consider `2.10.0.prX` to be "after" `2.10.0`.
But I really want to give enough time to get bug reports for initial problems to avoid having to spend 4-8 hours (typical time for making release) every 2 weeks.
So it is likely I'll release it somewhere towards end of October.

-+ Tatu +-
 
--

Amit Singla

unread,
Oct 17, 2019, 11:37:20 PM10/17/19
to jackso...@googlegroups.com

Tatu Saloranta

unread,
Oct 18, 2019, 3:23:59 PM10/18/19
to jackson-user
On Thu, Oct 17, 2019 at 8:37 PM Amit Singla <amitsi...@gmail.com> wrote:
I have already raised a ticket there. Let's see if someone responds and fix it.


Thank you!

-+ Tatu +-
 
Reply all
Reply to author
Forward
0 new messages