Thanks Doug. I'll take a look into that.
On 9/25/07, Doug Bateman <[EMAIL PROTECTED]> wrote: > > The annoyance you describe is actually related to the Maven embedded. If > you told the command line version of maven to fetch sources, it would have > the same issue. > > What we do at our company is use proximity to serve as a local cache to > all remote maven repositories. This has several advantages: > 1. Proximity can be configured to only attempt to download a missing > artifact a fixed number of times in a given time period. > 2. Proximity can cache locally remote artifacts, making download to the > local box VERY fast, which is especially helpful if you were to clear out > your local maven2 repository on your local machine. > 3. Proximity can serve as a gate keeper, allowing you to track which 3rd > party artifacts are in use at your company. > 4. You can upload commercial artifacts from vendors to your own local > maven repository, when your contract with that vendor wouldn't let you > upload it to a central internet repository. > > Doug > > ------------------------------ > *From:* Tim Downey [mailto:[EMAIL PROTECTED] > *Sent:* Tuesday, September 25, 2007 7:55 AM > *To:* [email protected] > *Subject:* [m2eclipse-user] Rebuild speed of multi-module project slow due > to missing java-source artifacts? > > Hi, > > Rebuild speed in 0.11 of a large multi-module project is quite slow, > perhaps due to trying to download source artifacts. This is particularly > noticeable after forcing a refresh in Eclipse of the projects. Typically, > after synchronizing my Eclipse workspace with the version control system, it > is necessary to Refresh the projects in Eclipse. > > This tends to send the Maven plugin sideways for quite a while (sometimes > over 20 minutes) in what seems like frequent and repeated attempts to > download the java-source artifacts. It is very useful to have the java > source artifacts available, but for many open source dependencies, the > source is not available. In such situations, it seems like m2Eclipse will > repeatedly attempt to contact the repository to download the artifacts. > > Is there anything that can be done to remember artifacts that are > unavailable? It would seem that this could be done in memory so that > restarting Eclipse would have the benefit of looking again in case artifacts > become available. > > Regards, > Tim >
