[
https://issues.apache.org/jira/browse/KARAF-314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Pieber updated KARAF-314:
---------------------------------
Attachment: fail-on-resolution-error-feature-branch-karaf-trunk.patch
fail-on-resolution-error-feature-branch-karaf-2.1.x.patch
Ok, this adds an additional config property (failOnArtifactResolutionError)
which throws an exception if something went wrong during artifact resolution.
Basically both attached patches do the same with one difference. While
karaf-2.1.x.patch sets failOnArtifactResolutionError to false (for backward
compatibility) karaf-trunk set its default value to true. IMHO the plugin
should abort the process in such a case. If you're not my opinion simply apply
karaf-2.1.x.patch to trunk and karaf-2.1.x branch.
> feature-maven-plugin does not fail if component couldn't be found
> -----------------------------------------------------------------
>
> Key: KARAF-314
> URL: https://issues.apache.org/jira/browse/KARAF-314
> Project: Karaf
> Issue Type: Improvement
> Components: tooling
> Affects Versions: 2.1.2, 2.2.0
> Reporter: Andreas Pieber
> Attachments:
> fail-on-resolution-error-feature-branch-karaf-2.1.x.patch,
> fail-on-resolution-error-feature-branch-karaf-trunk.patch
>
>
> The feature-maven-plugin does not fail if a dependency could not be loaded.
> The problem is: it is printed on the console but the build still goes on,
> missing some artifacts in the system folder afterwards. This mostly happens
> because I have a type in my features.xml file. IMHO there should be at least
> an option to set the plugin to failIfDepsAreMissing or something like this
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
