I know, there are a lot of dependencies that are downloaded from my
company repository that is specified in the child project pom.
As you can see in my log, there is a incoherence that I am trying to point out:

Maven tries to download the parent pom just from repo1.maven.org:

[INFO] Scanning for projects...
Downloading: 
http://repo1.maven.org/maven2/com/sourcesense/alfresco/alfresco-base/1.0/alfresco-base-1.0.pom
[INFO] -----------

and then give the Fatal Error.
But after it tells that it cannot found artifact in both repos:

--
from the specified remote repositories:
central (http://repo1.maven.org/maven2),
sourcesense (dav:https://dev.sourcesense.com/repos/dev/maven2)
--

I suspect that it does not even try to download the parent pom
artifact from my company repo. All other artifact are correclty
downloaded and normally the download sequence is: first, specified
repo, later the default repo, in fact this is a typical sequence:

Downloading: 
https://dev.sourcesense.com/repos/dev/maven2/axis/axis-jaxrpc/1.4/axis-jaxrpc-1.4.pom
Downloading: 
http://repo1.maven.org/maven2/axis/axis-jaxrpc/1.4/axis-jaxrpc-1.4.pom
Downloading: 
https://dev.sourcesense.com/repos/dev/maven2/axis/axis-saaj/1.4/axis-saaj-1.4.pom
Downloading: http://repo1.maven.org/maven2/axis/axis-saaj/1.4/axis-saaj-1.4.pom

Finally: or I am missing something in configuration or there is a bug
in the sequence: maven does not look for repositories defined in pom
before looking for the parent project artifact.
In fact if I already have the artifact in local repo, everything works.

On 7/9/07, Rémy Sanlaville <[EMAIL PROTECTED]> wrote:
Hi,

You parent pom is like any artifact and you have to indicate to maven 2
where to find it.

Since you have a corporate repository (via a maven proxy) you have two
solutions :
1. Either you add a reference to your corporate repository in your pom.xml
  <repositories>
    <repository>
      <id>inhouse</id>
      <name>Inhouse maven repository</name>
      <url>url to your corporate repository</url>
      <releases>
        <enabled>true</enabled>
      </releases>
      <snapshots>
        <enabled>false</enabled>
      </snapshots>
    </repository>

2. or by specifying your corporate repository to maven 2 in your setting.xml
  <mirrors>
    <mirror>
      <id>Corporate Proxy</id>
      <mirrorOf>central</mirrorOf>
      <name>my corporate repository</name>
      <url>url to your corporate repository</url>
    </mirror>
It's important to use the token central for the node mirrorOf.

In general, the second solution is better when using a maven 2 proxy.

HTH,

Rémy


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to