Additionally, this is not a valid maven2 repository at all. The metadata files are missing completely.

-Tim


Wayne Fay schrieb:
That URL doesn't work:
Not Found
The requested URL /maven2 was not found on this server.

Do you mean http://maven.reucon.com/public/  ?

If you look in the repo, you'll see there is no matching pom file for
the commons-id artifact...
http://maven.reucon.com/public/commons-id/commons-id/0.1-dev/

Please complain to the reucon people.

Wayne

On 10/9/07, Rodrigo Madera <[EMAIL PROTECTED]> wrote:
                        <name>Repository only for commons-id</name>
                        <url>http://maven.reucon.com/maven2</url>
                        <layout>default</layout>
                        <snapshots>
                                <enabled>false</enabled>
                        </snapshots>
                        <releases>
                                <updatePolicy>never</updatePolicy>
                        </releases>

Yours,
Rodrigo



On 10/9/07, Tim Kettler <[EMAIL PROTECTED]> wrote:
Hi,

I don't find any of these in the central repo. Can you please point me
to the repositories containing the artifacts for GNU/Crypto & commons-id.

-Tim

Rodrigo Madera schrieb:
It does exist.

Just create something that uses GNU/Crypto.
It downloads it ALL the time. If I disconnect my Internet to test, then
the
build fails because it can't get the pom.

I imagined this would be something easy for you guys.
Also, commons-id-01-dev has the same problem.

Thanks,
Rodrigo

On 10/9/07, Wendy Smoak <[EMAIL PROTECTED]> wrote:
On 10/8/07, Rodrigo Madera <[EMAIL PROTECTED]> wrote:

Maven2 currently has a bad habit of downloading certain poms over and
over
again on each and every execution.

I had this problem with GNU Crypto, but I managed to not use it
anymore.
Now it''s happening with commons-id-0.1-dev.

Anyone know how to make Maven2 behave? this is getting REALLY
annoying.
Without the build output it's hard to tell, but I suspect it's
*trying* to download the pom, but not actually doing it because the
pom doesn't exist in the remote repo.

If so, you can...

* install the jar locally (mvn install:install-file) and use the
-DgeneratePom=true property to generate a pom for it.

* open a MEV ticket and provide a pom for the project

* open an issue with the project developers to have them provide the
missing pom and supply one for future releases.

--
Wendy

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



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



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


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

Reply via email to