logging profile does not work.

Description

-> mvn:org.ops4j.pax.logging/pax-logging-api/1.4 : connecting...
___
/ /
/ / Oops, there has been a problem!
/ /
/__/ URL mvn:org.ops4j.pax.logging/pax-logging-api/1.4 could not be resolved.
___
/__/ Use --log=debug to see details.

Environment

Apache Maven 2.2.0 (r788681; 2009-06-26 15:04:01+0200)
Java version: 1.6.0_15
Java home: /System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Home
Default locale: no_NO, platform encoding: MacRoman
OS name: "mac os x" version: "10.6" arch: "x86_64" Family: "mac"

Activity

Show:
BjørnM
August 12, 2009, 11:48 AM

Ah ok thats why you didnt host 1.4.0..

Still does not explain the checksum error we get when checking pax-logging-api-1.4.jar ..

NiclasH
August 12, 2009, 12:02 PM

Alin,
I downloaded the pax-logging-api-1.4.jar myself, and ran the sha1 and md5 checksum digesters on it, and it produced the numbers seen in the exception and NOT the values in the .MD5 and .SHA1 files on the server.
Try for yourself if you like; http://repo1.maven.org/maven2/org/ops4j/pax/logging/pax-logging-api/1.4/

Alin Dreghiciu
August 12, 2009, 1:32 PM

I have to verify this but I recall that in some late version of maven the md5 and sha1 were calculated wrong so it may be the cause.

Alin Dreghiciu
August 12, 2009, 11:12 PM

I guess the problem is the one described in http://jira.codehaus.org/browse/MNG-4235 as I used Maven 2.2.0 while releasing and it may be that it can be solved only when we will do a new release.

Alin Dreghiciu
August 13, 2009, 8:22 AM

No need for a new version. Nexus has an option to regenerate this files, so I did.
No the checksums are okay, and the artifactory proxy does not complain anymore.

Assignee

Alin Dreghiciu

Reporter

BjørnM

Labels

None

Components

Fix versions

Affects versions

Priority

Major
Configure