[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [aether-users] doubts about custom packaging artifacts resolution
|
Hi,
The exception was:
org.apache.maven.artifact.resolver.ArtifactResolutionException: Could
not transfer artifact
org.apache.felix:org.apache.felix.bundlerepository:bundle:1.6.6
But your tip help me to figure out that I need to declare the bundle
ArtifactHandler component in my plugin and I could make it work. thanks
for the tip.
Btw, and if I need to do such resolution of artifacts at runtime,
without maven, how would I setup aether to consider the artifacts types
? for example I have some install pieces that are packaged using zip
format with a proper mime/type and have extension ".proc".
best regards,
Cristiano
On 04-05-2014 09:24, Benjamin Bentmann wrote:
Cristiano Gavião wrote:
I'm start working in a mojo (maven 3.2.1, aether 0.9.0.M2) where it
needs to traverse project's direct dependency, get its real packaging
type (bundle or other custom archive type) [...]
ArtifactHandler bundleArtifactHandler = new
DefaultArtifactHandler("bundle");
If you want to mimic a custom packaging, you need to ensure you mimic
it properly. The artifact handler you create here does not match the
one defined by the maven-bundle-plugin [0].
Could someone point me to right direction?
You didn't actually share the details of the error, your brief
description suggests you have issues with Maven's artifact handler
concept. So you might be better off asking on the Maven user list
about that.
Benjamin
[0]
http://svn.apache.org/repos/asf/felix/releases/maven-bundle-plugin-2.4.0/src/main/resources/META-INF/plexus/components.xml
_______________________________________________
aether-users mailing list
aether-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/aether-users
