maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jim Showalter (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MNG-6448) Need to be able to tell Maven to not bother trying to download particular sources jars
Date Thu, 19 Jul 2018 20:31:00 GMT

    [ https://issues.apache.org/jira/browse/MNG-6448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16549819#comment-16549819
] 

Jim Showalter commented on MNG-6448:
------------------------------------

I hadn't expected to get lectured about why do we want the sources jars. We want them for
debugging, to be able to step through code.

We don't download sources jars in production builds, but we do in developer builds, by activating
a profile.

It wouldn't matter if we did this from an IDE or command line: so long as Maven is involved,
it will continue fruitlessly attempting to download nonexistent sources jars.

Consider a binary compile in 1999 without a sources jar, and then that project becomes moribund.
The jar is still in use, it will never have an accompanying sources jar, and there seems to
be no way to tell Maven to stop attempting to download the sources jar.

We're simply asking to be provided with a way to tell Maven not to bother, for sources jars
we know don't exist and never will.

Point me to the part of the code that needs to be modified and I'll happily submit a PR.

> Need to be able to tell Maven to not bother trying to download particular sources jars
> --------------------------------------------------------------------------------------
>
>                 Key: MNG-6448
>                 URL: https://issues.apache.org/jira/browse/MNG-6448
>             Project: Maven
>          Issue Type: Bug
>          Components: Dependencies
>            Reporter: Jim Showalter
>            Priority: Major
>         Attachments: pom.xml
>
>
> Sources jars are optional, so Maven has no way of knowing if a project decided to publish
a sources jar. Even if the code and released jar hasn't changed since 1998, somebody might
edit the build pom to generate a sources jar.
> This causes Maven to attempt to fetch non-existent sources jars in perpetuity.
> Maven waits several seconds when attempting to fetch a sources jar before giving up.
> We have 142 sourceless jars on our build path.
> The wait time multiplied by 142 winds up adding 11 minutes to our builds.
> We don't want to shut off sources jars, because, when they exist, developers use them
to step through code. But we don't want Maven to keep trying to download sources jars we know
don't exist and are pretty sure will never exist.
> Something like a section in settings.xml for ignoreSourcesJars that allowed us to list
the ones to ignore would be great.
> I'm happy to help with this if someone can point me to where in the code a change like
this needs to be made.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message