Ok, I know next to nothing about Karaf, but I just want to make sure I didn't break anything with all the dependency cleanup I did in Pax URL, so I cloned Karaf and ran mvn install.

This is the error I'm getting in assemblies/apache-karaf-minimal:

Downloading: https://oss.sonatype.org/content/groups/public/wrap/mvn/org.ops4j.pax.url/pax-url-maven-commons/1.4-SNAPSHOT/mvn-org.ops4j.pax.url/pax-url-maven-commons/1.4-SNAPSHOT.jar Downloading: http://repository.apache.org/snapshots/wrap/mvn/org.ops4j.pax.url/pax-url-maven-commons/1.4-SNAPSHOT/mvn-org.ops4j.pax.url/pax-url-maven-commons/1.4-SNAPSHOT.jar [WARNING] could not resolve wrap:mvn:org.ops4j.pax.url/pax-url-maven-commons/1.4-SNAPSHOT org.sonatype.aether.resolution.ArtifactResolutionException: Could not find artifact wrap:mvn:jar:org.ops4j.pax.url/pax-url-maven-commons/1.4-SNAPSHOT in ops4j-snapshots (https://oss.sonatype.org/content/repositories/ops4j-snapshots)

So the problem is not that the artifact cannot be downloaded, but somehow the artifact URL is broken:

.../wrap/mvn/org.ops4j.pax.url/pax-url-maven-commons/1.4-SNAPSHOT

That simply doesn't make sense.

Is that pax-url-wrap you're using in Karaf?

Maybe the wrap: URL handler isn't working for you, because it is missing some dependencies which are no longer embedded. So you may want to check whether or not the pax-url-wrap bundle resolves and add any missing bundles for required dependencies to your setup.

The other question is, why does pax-url-maven-commons have to be wrapped? I suppose this is because up to now, it was only used as an embedded dependency of other URL handlers but not as an independent artifact.

But I see no reason why we shouldn't run the maven-bundle-plugin on pax-url-maven-commons and make it a real grown-up bundle.

The trouble is, Pax URL has no real integration tests at the moment. That's why I created a new module pax-url-itest with a Pax Exam test for the obr: handler.

If there is indeed an issue with the wrap: handler and if you can isolate it, that would be great input for a new wrap: integration test.

Hope that helps,
Harald


Am 27.01.2012 11:04, schrieb Achim Nierbeck:
Hi Harald,

thanx for trying, actually this is the same thing I did last night.
Nuked all my ops4j artifacts from local repo and did a rebuild of Karaf
3.0-SNAPSHOT.
Funny though Pax-Web 2.0-SNAPSHOT is actually building without issues,
even though it also uses pax-url artefacts.
Another interesting thing, I'm not the only one facing this issue with
Karaf right now others of the Karaf project reported this too.

regards, Achim


_______________________________________________
general mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/general

Reply via email to