Hi,
RepositoryUtils is a utility class, whereas an ArtifactHandler is a
Component (i.e. injectable), so these 2 don't mix that well together.
IMHO the Artifact is way too big and too complex. It is a mixture of a
pojo with component(s), and that's probably also the reason why there was
an A
After having lost many hours I finally found where the problem is likely
to be... :-(
maven is using aether for dependency resolution, but aether has not a
concept of packaging and extension as maven has. it only has extension.
as a workaround maven is saving the packaging type inside the aet
Well, is not the dot the culprit...
I tried with another packaging name and I got the same result.
I still don't know who injects the ArtifactHandler in the dependency...
any idea ?
-
To unsubscribe, e-mail: dev-unsubscr...@
Hello,
I'm facing a problem with a plugin that has a custom ArtifactHandler for
a custom packaging type. The custom class is being registered by sisu
and no problem was reported while running a build, except when a project
artifact has one artifact of this custom type as a dependency.
The pr
