Maybe you could hack it by labeling your internal artifacts as
snapshots and then listing my-repo as snapshot only? Still learning
maven so that may be way off.
Sean
On 5/10/06, Bruno Aranda <[EMAIL PROTECTED]> wrote:
Mmm, I see what is happening,
When it goes to search a dependency already present in the internal
repository no problem, but when it tries to search a dependency not
present in the repo (such as commons-logging, for instance), it gets a
"Missing page" html. How can avoid that? Because if it gets the
missing page, it does not try to look for the dependency in the
central repository...
Adding the ibiblio repo in the pom fixes the issue, as it tries first
now to look for the central repo and then the internal...
<repositories>
<repository>
<id>central-repo</id>
<name>Ibiblio repository</name>
<url>http://www.ibiblio.org/maven2</url>
</repository>
<repository>
<id>my-repo</id>
<name>My interlanl repository</name>
<url>http://www.myorganization.org/m2repo</url>
</repository>
</repositories>
At least it works now, but is there a more elegant solution?
Thanks,
Bruno
On 5/10/06, Bruno Aranda <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I am trying to create a pom for an existing project and I have setup
> an internal repository for all those jars that I need which are not
> present in ibiblio. In the institution where I work, there is a proxy.
>
> When I include the repository section in my pom:
>
> ...
>
> <repositories>
> <repository>
> <id>my-repo</id>
> <name>My interlanl repository</name>
> <url>http://www.myorganization.org/m2repo</url>
> </repository>
> </repositories>
>
> ...
>
> I keep getting these kind of warnings:
>
> Downloading:
http://www.ebi.ac.uk/~maven/m2repo/org/apache/maven/wagon/wagon-ssh-external/1.0-alpha-5/wagon-ssh-external-1.0-alpha-5.pom
> 50K downloaded
> [WARNING] *** CHECKSUM FAILED - Checksum failed on download: local =
> '93acd1eaeb3d27ec9f89ab480f384fdce57578ca'; remote = '<html>
> <script' - RETRYING
> ...
> and later:
>
> [WARNING] POM for
> 'commons-collections:commons-collections:pom:3.1:compile' is invalid.
> It will be ignored for artifact resolution. Reason: Not a v4.0.0 POM.
> [WARNING] POM for 'commons-logging:commons-logging:pom:1.0.4:compile'
> is invalid. It will be ignored for artifact resolution. Reason: Not a
> v4.0.0 POM.
> ...
>
> It seems to me like there is a proxy problem. I have setup the proxy
> details in my settings.xml file to no avail... Possibly I have
> something misconfigured somewhere... anywhere have an idea where to
> look?
>
> Thanks!
>
> Bruno
>
