maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aaron Digulla (JIRA)" <>
Subject [jira] Commented: (MECLIPSE-174) Plugin doesn't cache "source not available" status
Date Mon, 30 Oct 2006 19:44:03 GMT
    [ ] 
Aaron Digulla commented on MECLIPSE-174:

Can't you reuse the standard maven2 cache? I would prefer if the command line maven and the
plugin would agree on what has been tried and what hasn't.

Also I don't think the target dir is a good place for this information. What happens when
I close a project? Why not put this into the workspace instead?

> Plugin doesn't cache "source not available" status
> --------------------------------------------------
>                 Key: MECLIPSE-174
>                 URL:
>             Project: Maven 2.x Eclipse Plugin
>          Issue Type: Improvement
>    Affects Versions: 2.2
>            Reporter: Aaron Digulla
>         Assigned To: fabrizio giustina
>            Priority: Minor
>             Fix For: 2.3
> When the m2 plugin reads the POM files and "Download sources" is set in the Eclipse preferences,
it tries to download the source every time.
> Instead, it should cache the "source not available" status somewhere (just like Maven
itself does) and not print thousands of error messages (Unable to download the artifact from
any repository).
> This also delays the build considerably (opening network connections) and real errors
are drowned.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message