karaf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Achim Nierbeck (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (KARAF-314) feature-maven-plugin does not fail if component couldn't be found
Date Sun, 12 Dec 2010 20:22:01 GMT

     [ https://issues.apache.org/jira/browse/KARAF-314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Achim Nierbeck resolved KARAF-314.
----------------------------------

       Resolution: Fixed
    Fix Version/s: 2.2.0
                   2.1.3

Revision: 1044906 - 2.1.3
Revision: 1044903 - 2.2.0

> 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
>            Assignee: Achim Nierbeck
>             Fix For: 2.1.3, 2.2.0
>
>         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.


Mime
View raw message