[ 
https://issues.apache.org/jira/browse/KARAF-6103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16747903#comment-16747903
 ] 

ASF GitHub Bot commented on KARAF-6103:
---------------------------------------

chrisdutz commented on pull request #734: KARAF-6103 - When doing a "mvn 
compile" the karaf-maven-plugin causes…
URL: https://github.com/apache/karaf/pull/734
 
 
   … a IOException
   
   - Added a check to detect if the "file" passed in to getMetadata() is a file 
or a directory.
   - Implemented an alternate process for reading MANIFEST.MF files from 
directories.
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[email protected]


> 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: Minor
>             Fix For: 4.2.3
>
>
> 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)

Reply via email to