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

Stefan Seifert reassigned FELIX-6106:
-------------------------------------

    Assignee: Stefan Seifert

as far a i see the problem was introduced one commit before:
https://github.com/apache/felix/commit/e12e94cb84d99e4613a4a57c3655bc7c6095140c

it seems the collection of class path items with this refactoring includes also 
items that does not exist yet (in this case the target/classes folder - because 
in this case this project produced no classes at all but combines only 
artifacts from dependencies).


> Regression after a change in maven-bundle-plugin:4.2.0 related to 
> non-existing files
> ------------------------------------------------------------------------------------
>
>                 Key: FELIX-6106
>                 URL: https://issues.apache.org/jira/browse/FELIX-6106
>             Project: Felix
>          Issue Type: Bug
>          Components: Maven Bundle Plugin
>    Affects Versions: maven-bundle-plugin-4.2.0
>            Reporter: Martin Grigorov
>            Assignee: Stefan Seifert
>            Priority: Major
>
> Commit 
> https://github.com/apache/felix/commit/9487647dc2fa8734a0ab4a113b0b93ec281a2594
>  introduced with FELIX-6074 leads to an error in one of our projects:
> {code}
> INFO] --- maven-bundle-plugin:4.2.0:bundle (default-bundle) @
> wicketstuff-bundle ---
> [ERROR] An internal error occurred
> java.lang.IllegalArgumentException: A Jar can only accept a file or
> directory that exists:
> /home/solomax/work/wicketstuff-core/wicket-bundle-parent/wicket-bundle/target/classes
>     at aQute.bnd.osgi.Jar.<init> (Jar.java:124)
>     at aQute.bnd.osgi.Jar.<init> (Jar.java:172)
>     at org.apache.felix.bundleplugin.BundlePlugin.getOSGiBuilder
> (BundlePlugin.java:603)
> {code}
> The code of the module can be found at 
> https://github.com/wicketstuff/core/tree/master/wicket-bundle-parent/wicket-bundle.
>  It is mostly Maven code (pom.xml and assembly.xml) that generates an OSGi 
> compatible bundle.
> After upgrading to maven-bundle-plugin:4.2.0 it started failing with the 
> above error.



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

Reply via email to