felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stuart McCulloch (JIRA)" <j...@apache.org>
Subject [jira] Commented: (FELIX-340) Plug-in fails if dependencies are not all jar files
Date Wed, 22 Aug 2007 03:22:30 GMT

    [ https://issues.apache.org/jira/browse/FELIX-340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12521664

Stuart McCulloch commented on FELIX-340:

I also updated the maven-plugin-testing-harness to 1.1 because the 1.0 version
contained a bug where the maven project stub code always returned a list with
an empty string for getArtifacts() causing a class-cast-exception in the test.

> Plug-in fails if dependencies are not all jar files
> ---------------------------------------------------
>                 Key: FELIX-340
>                 URL: https://issues.apache.org/jira/browse/FELIX-340
>             Project: Felix
>          Issue Type: Bug
>          Components: Maven Bundle Plugin
>    Affects Versions: 1.0.0
>            Reporter: Guillaume Sauthier
>            Assignee: Stuart McCulloch
>         Attachments: FELIX-340.patch, FELIX-340.poms.zip
> I'm just trying to make my first bundle using the felix maven-bundle-plugin.
> As this bundle is intended to have a quite big number of dependencies, I've created a
pom module that only defines all the dependencies. The  this module has been placed in the
dependencies section of my bundle's pom.xml.
> looks like this: a --> b --> (c, d, e, f, g, h, i, ...)
> When I just build my bundle, It finish quite soon with a NPE in JarFile!
> -> The bundleplugin only manage jar file as dependencies. It should at least check
the dependency type before assuming this is a jar file.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message