On 04/23/2012 01:28 PM, Suresh Marru wrote:
Hi All,
Jenkins is failing randomly trying to pull j2ssh jars from ibiblio - "Could not
transfer artifact j2ssh:j2ssh-core:pom:0.2.9 from/to ibiblio
(http://mirrors.ibiblio.org/pub/mirrors/maven2): Error transferring file: Connection
refused"
Any alternative maven repo for these jars?
Yeah: like maven central?
I saw you later comment you now uploaded these to the ogce.m2.all maven repo to
'fix' this. However IMO this is a bad practice if the *default* repository
(Maven Central) already provides these as well.
It looks like airavata uses many 3rd party repositories for its build but I
doubt they are or should be needed in many/most cases. Also note that the more
repositories you need/configure, the longer a build will take...
The problem here is that the maven central repository is not (also) defined in
the root pom which causes maven to *first* check those defined repositories
*before* it will fall-back to Maven Central.
As a test, I successfully build airavata with no local repository and a local
settings.xml which enables/predefines central and *disables* ibiblio, which
indeed is notoriously slow and AFAIK nobody should use or even need anymore:
<?xml version="1.0" encoding="UTF-8"?>
<settings xmlns="http://maven.apache.org/POM/4.0.0";>
<profiles>
<profile>
<id>default-profile</id>
<activation>
<activeByDefault>true</activeByDefault>
</activation>
<repositories>
<repository>
<id>ibiblio</id>
<name>ibiblio Repository</name>
<url>http://mirrors.ibiblio.org/pub/mirrors/maven2</url>
<releases><enabled>false</enabled></releases>
<snapshots><enabled>false</enabled></snapshots>
</repository>
<repository>
<id>central</id>
<name>Maven Central</name>
<url>http://repo1.maven.org/maven2</url>
<releases><enabled>true</enabled></releases>
<snapshots><enabled>false</enabled></snapshots>
</repository>
</repositories>
</profile>
</profiles>
</settings>
So, I strongly suggest removing the ibiblio repo from the airavata build all
together and probably also add the central repo as *first* in the root pom.
And it would also be smart to check/validate if possibly you can cleanup in the
ogce.m2.all repo...
Also, I see usage of a personal repository from Lahiru:
http://people.apache.org/~lahiru/maven-repo
AFAIK this type of personal repositories on people.apache.org is not endorsed
and maybe even not allowed (already now or else in the future) by ASF Infra...
I'm not saying this is a blocker right now but why would this be needed in the
first place and why are the needed artifacts not available from a
general/central repository, preferably Maven Central?
Thanks, Ate
