felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Konrad Windszus (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (FELIX-5163) Suppress empty classpath warnings from bnd when creating a fragment with a manifest only
Date Mon, 11 Jan 2016 17:56:39 GMT

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

Konrad Windszus updated FELIX-5163:
-----------------------------------
    Description: 
Currently bnd emits the following warnings when building a fragment with the maven-bundle-plugin
which does not contain any classes (which is totally valid)
{code}
WARNING] Bundle somegroup:system-fragment-xml-api:bundle:1.0-SNAPSHOT : Classpath is empty.
Private-Package (-privatepackage) and Export-Package can only expand from the classpath when
there is one
[WARNING] Bundle somegroup:system-fragment-xml-api:bundle:1.0-SNAPSHOT : Unused Private-Package
instructions, no such package(s) on the class path: [!*]
[WARNING] Bundle somegroup:system-fragment-xml-api:bundle:1.0-SNAPSHOT : The JAR is empty:
The instructions for the JAR named somegroup.system-fragment-xml-api did not cause any content
to be included, this is likely wrong
{code}

Attached is a demo pom.xml.

Just setting the instruction {{-resourceonly}} to {{true}} in that case should be enough to
suppress those warning (compare with https://github.com/bndtools/bnd/issues/1287).

Maven-Bundle-Plugin should check if the header {{FragmentHost}} host is set and the classpath
is empty. IFF that is the case it should call bnd with resourceonly:true.

  was:
Currently bnd emits the following warnings when building a fragment with the maven-bundle-plugin
which does not contain any classes (which is totally valid)
{code}
WARNING] Bundle somegroup:system-fragment-xml-api:bundle:1.0-SNAPSHOT : Classpath is empty.
Private-Package (-privatepackage) and Export-Package can only expand from the classpath when
there is one
[WARNING] Bundle somegroup:system-fragment-xml-api:bundle:1.0-SNAPSHOT : Unused Private-Package
instructions, no such package(s) on the class path: [!*]
[WARNING] Bundle somegroup:system-fragment-xml-api:bundle:1.0-SNAPSHOT : The JAR is empty:
The instructions for the JAR named somegroup.system-fragment-xml-api did not cause any content
to be included, this is likely wrong
{code}

Attached is a demo pom.xml.

Just setting the instruction {{-resourceonly}} to {{true}} in that case should be enough to
suppress those warning (compare with https://github.com/bndtools/bnd/issues/1287)


> Suppress empty classpath warnings from bnd when creating a fragment with a manifest only
> ----------------------------------------------------------------------------------------
>
>                 Key: FELIX-5163
>                 URL: https://issues.apache.org/jira/browse/FELIX-5163
>             Project: Felix
>          Issue Type: Improvement
>          Components: Maven Bundle Plugin
>    Affects Versions: maven-bundle-plugin-3.0.1
>            Reporter: Konrad Windszus
>
> Currently bnd emits the following warnings when building a fragment with the maven-bundle-plugin
which does not contain any classes (which is totally valid)
> {code}
> WARNING] Bundle somegroup:system-fragment-xml-api:bundle:1.0-SNAPSHOT : Classpath is
empty. Private-Package (-privatepackage) and Export-Package can only expand from the classpath
when there is one
> [WARNING] Bundle somegroup:system-fragment-xml-api:bundle:1.0-SNAPSHOT : Unused Private-Package
instructions, no such package(s) on the class path: [!*]
> [WARNING] Bundle somegroup:system-fragment-xml-api:bundle:1.0-SNAPSHOT : The JAR is empty:
The instructions for the JAR named somegroup.system-fragment-xml-api did not cause any content
to be included, this is likely wrong
> {code}
> Attached is a demo pom.xml.
> Just setting the instruction {{-resourceonly}} to {{true}} in that case should be enough
to suppress those warning (compare with https://github.com/bndtools/bnd/issues/1287).
> Maven-Bundle-Plugin should check if the header {{FragmentHost}} host is set and the classpath
is empty. IFF that is the case it should call bnd with resourceonly:true.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message