[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [m2e-users] [m2e-dev] please test m2e 1.2 changes
|
Do you have a more complete stacktrace?
Is the archetype defined in a remote archetype catalog or found in your nexus index?
On Mon, Aug 20, 2012 at 1:41 PM, Greg Thomas
<greg.d.thomas@xxxxxxxxx> wrote:
On 16 August 2012 23:16, Fred Bricon <
fbricon@xxxxxxxxx> wrote:
> The latest 1.2 build (few minutes old) contain fixes wrt remote archetype
> resolution. If you had troubles using remote archetypes behind proxies or
> mirrors, I'm interested in knowing if this works for you now.
I just tried 1.2.0.20120819-2129 with Juno; it seems to fix
https://bugs.eclipse.org/bugs/show_bug.cgi?id=371775 ("M2E does not
provide credentials to a repository when fetching an archetype") which
I raised a while ago, so thanks for that; however I am seeing
ArtifactDescriptorException: Failed to read artifact descriptor for
ch.qos.logback:logback-classic:jar:0.9.20:
ArtifactResolutionException: Could not transfer artifact
ch.qos.logback:logback-classic:pom:0.9.20 from/to local-releases
(https://.../artefacts/content/repositories/local-releases): Access
denied to (https://.../artefacts/content/repositories/local-releases/ch/qos/logback/logback-classic/0.9.20/logback-classic-0.9.20.pom
. Status code 401
It seems that M2E is now looking in the wrong repo for public artefacts.
i.e. Indigo with SR1 + M2E 1.0.100.20110804-1717 is correctly looking
in https://.../artefacts/content/repositories/apache/ch/qos/logback/logback-classic/0.9.20/logback-classic-0.9.20.pom
Juno + M2E is wrongly looking in
https://.../artefacts/content/repositories/local-releases/ch/qos/logback/logback-classic/0.9.20/logback-classic-0.9.20.pom
[That's just one example; all the public artefacts cached in our local
repository are failing ...]
Greg
--
"Have you tried turning it off and on again" - The IT Crowd