Erratum :
I configured archiva to remembers errors on remote repositories but how
can we do the same for local ones ?
Julien CARSIQUE a écrit :
We use archiva 1.0.
I've checked the external repositories, they're ok. And I already
encountered this situation (external repository down) but it was
impacting mvn install too, not only mvn eclipse:eclipse.
I recently thought about this possibility and so configured archiva to
remember errors. It was a week ago, and we still have the issue : I ran
an mvn eclipse:eclipse this afternoon and it was running for hours when
I stopped it.
Arnaud HERITIER a écrit :
With which version of archiva is it ?
With a version < 1.0 (I didn't test with 1.0) I have a similar problem for 2
reasons :
- Some external repositories proxied by archiva were down and each time
archiva tried to download a missing artifact it waited the http timeout
(probably 1min) to try another external repo
- A lot of sources and javadocs aren't published and thus if you don't
configure archiva to keep in memory the errors, it will try to download them
every XX hours (depending of your settings).
Arnaud
On Dec 20, 2007 6:25 PM, Julien CARSIQUE <[EMAIL PROTECTED]> wrote:
"mvn eclipse:clean eclipse:eclipse" has just finished
[INFO] BUILD SUCCESSFUL
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 134 minutes 34 seconds
[INFO] Finished at: Thu Dec 20 18:14:35 CET 2007
[INFO] Final Memory: 66M/254M
134 minutes to download sources against 1min30 with
"-DdownloadSources=false"
Why this crazy difference ?
It could be useful to download javadoc too but I fear having to wait for
3 more hours :-(
Any help would be appreciated, thanks
Julien
Julien CARSIQUE a écrit :
Hi,
Does anyone use maven-eclipse:plugin, mvn eclipse:eclipse in online
mode with downloadSources=true ?
In offline, it takes about 1min30; online, with downloadSources=true,
it takes several hours (when it finishes, as archiva often freeze on
too long tasks) !
I have this configuration in the parent pom.xml :
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-eclipse-plugin</artifactId>
<version>2.4</version>
<configuration>
<downloadSources>true</downloadSources>
</configuration>
</plugin>
If this can be a workaround, is it possible to store the sources'
status cache, outside the target dir ?
<< Enables/disables the downloading of source attachments. Defaults to
false. When this flag is |true| remote repositories are checked for
sources: in order to avoid repeated check for unavailable source
archives, a status cache is mantained into the target dir of the root
project. Run |mvn:clean| or delete the file
|mvn-eclipse-cache.properties| in order to reset this cache. >>
--
Julien CARSIQUE, Nuxeo (Paris, France)
Open Source Enterprise Content Management - http://www.nuxeo.org/
Nuxeo EP 5: extensible, Java EE and standards based ECM Platform
http://www.nuxeo.com/ - Tel: +33 1 40 33 79 87
|
