[jira] Commented: (MECLIPSE-174) Plugin doesn't cache source not available status
[ http://jira.codehaus.org/browse/MECLIPSE-174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_108589 ] Aaron Digulla commented on MECLIPSE-174: I can confirm that. It seems the list of downloaded files which you get back from resolveArtifacts() (from memory; I'm not at my work PC right now) is empty. Plugin doesn't cache source not available status -- Key: MECLIPSE-174 URL: http://jira.codehaus.org/browse/MECLIPSE-174 Project: Maven 2.x Eclipse Plugin Issue Type: Improvement Affects Versions: 2.2 Reporter: Aaron Digulla Assignee: 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: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MECLIPSE-174) Plugin doesn't cache source not available status
[ http://jira.codehaus.org/browse/MECLIPSE-174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_108465 ] Chuck Daniels commented on MECLIPSE-174: Looks like this has regressed in version 2.5 of this plugin. The mvn-eclipse-cache.properties file is empty (except for header comment) after running eclipse:eclipse with downloadSources and downloadJavadocs set to true. Now every run of eclipse:eclipse attempts to download sources and javadocs since cache file contains no entries. Plugin doesn't cache source not available status -- Key: MECLIPSE-174 URL: http://jira.codehaus.org/browse/MECLIPSE-174 Project: Maven 2.x Eclipse Plugin Issue Type: Improvement Affects Versions: 2.2 Reporter: Aaron Digulla Assignee: 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: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MECLIPSE-174) Plugin doesn't cache source not available status
[ http://jira.codehaus.org/browse/MECLIPSE-174?page=comments#action_78819 ] 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: http://jira.codehaus.org/browse/MECLIPSE-174 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: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
