Are you defining a mirror in your maven settings ?
How many different snapshots repositories are defined in your project and
it's transitive dependencies (hard to define but from central it should
never be the case)
My guess is that in your project and transitive dependencies you are
defining ~20 snapshots repositories (with different identifiers).
When you upload upload an artifact, maven doesn't know where each artifact
comes from and thus it is asking to each repository if there are some
metadata for it.
It you have a catch-all mirror defined in your settings it could end to
have maven asking 20 times the same metadata to your mirror (Maven doesn't
compare at all the repositories URLs to see if some repositories with
different identifiers are targeting the same url)


On Fri, May 12, 2017 at 9:31 PM, Dan Tran <[email protected]> wrote:

> and it happens at deploy phase only
>
> -D
>
> On Fri, May 12, 2017 at 12:01 PM, Dan Tran <[email protected]> wrote:
>
> >
> > my particular module has one optional RPM dependency. this means it only
> > downloads one dependency and no transitive
> >
> > not sure why this cause the strange metadata download behavior
> >
> > -D
> >
> >
> > On Fri, May 12, 2017 at 3:49 AM, Robert Scholte <[email protected]>
> > wrote:
> >
> >> My guess: references to snapshots or version ranges in one of your
> >> (transitive) dependencies.
> >>
> >> Robert
> >>
> >
>



-- 
-----
Arnaud Héritier
http://aheritier.net
Mail/GTalk: aheritier AT gmail DOT com
Twitter/Skype : aheritier

Reply via email to