You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@karaf.apache.org by "Jean-Baptiste Onofré (JIRA)" <ji...@apache.org> on 2019/01/21 10:07:01 UTC

[jira] [Assigned] (KARAF-6103) When doing a "mvn compile" the karaf-maven-plugin causes a IOException

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

Jean-Baptiste Onofré reassigned KARAF-6103:
-------------------------------------------

    Assignee: Jean-Baptiste Onofré

> When doing a "mvn compile" the karaf-maven-plugin causes a IOException
> ----------------------------------------------------------------------
>
>                 Key: KARAF-6103
>                 URL: https://issues.apache.org/jira/browse/KARAF-6103
>             Project: Karaf
>          Issue Type: Bug
>          Components: karaf
>    Affects Versions: 4.2.2
>            Reporter: Christofer Dutz
>            Assignee: Jean-Baptiste Onofré
>            Priority: Major
>
> If a user is building a project using the "karaf-maven-plugin" and is simply running "mvn compile" the "features-generate-descriptor" fails with an IOException as in "getManifest" the code is expecting the dependency to be a jar-file which is a directory in this case. 
> I see two solutions for this issue:
> a) Shift the execution of the plugin to a phase in which the jar is known to exist (I shifted it to the package phase)
> b) (preffered) Make the getManifest method to check if it's a directory or a jar and to use a directory scanner instead of a jar scanner if it's a directory.
> I could probably whip up a patch quite easily, if this is not been addressed yet ... Not being able to do a mvn compile in a project using this plugin is quite a drawback and it took me quite some time to find out what was going on with the build at the user that was reporting this.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)