You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Carsten Ziegeler (JIRA)" <ji...@apache.org> on 2015/08/01 13:30:04 UTC
[jira] [Closed] (FELIX-4205) "null" Bundle-Activator causes bundle
to fail
[ https://issues.apache.org/jira/browse/FELIX-4205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carsten Ziegeler closed FELIX-4205.
-----------------------------------
> "null" Bundle-Activator causes bundle to fail
> ---------------------------------------------
>
> Key: FELIX-4205
> URL: https://issues.apache.org/jira/browse/FELIX-4205
> Project: Felix
> Issue Type: Improvement
> Components: Maven Bundle Plugin
> Affects Versions: maven-bundle-plugin-2.4.0
> Reporter: Roland Weiglhofer
> Priority: Minor
> Fix For: maven-bundle-plugin-2.5.0
>
>
> An empty <Bundle-Activator></Bundle-Activator> clause causes following error:
> [INFO] [bundle:bundle {execution: default-bundle}]
> in default pack?
> [WARNING] Bundle mygroupId:myartifactId:mybundle:1.0.0.0 : Invalid package name: '*'
> [ERROR] Bundle mygroupId:myartifactId:mybundle:1.0.0.0 : The default package '.' is not permitted by the Import-Package syntax.
> This can be caused by compile errors in Eclipse because Eclipse creates
> valid class files regardless of compile errors.
> The following package(s) import from the default package null
> [ERROR] Error(s) found in bundle configuration
> It would be easier to understand if the error message would be something like this: "It is not allowed to specify an empty Bundle-Activtor clause. Check your POM in line xxx!"
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)