felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Hervé Barrault (JIRA) <j...@apache.org>
Subject [jira] [Commented] (FELIX-4205) Misleading error message
Date Mon, 02 Jun 2014 14:07:01 GMT

    [ https://issues.apache.org/jira/browse/FELIX-4205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14015404#comment-14015404

Hervé Barrault commented on FELIX-4205:

I was using 2.3.x bundle plugin which allows this configuration (empty Activator-Bundle).
It's not a very good practice but I used variables for configuration (for Activator-Bundle,
Import-Package, ...) in order to simplify the usage.
The log will be a great help for a migration process.

> Misleading error message
> ------------------------
>                 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
> An empty <Bundle-Activator></Bundle-Activator> clause causes following error:
> [INFO] [bundle:bundle {execution: default-bundle}]
> in default pack?
> [WARNING] Bundle mygroupId:myartifactId:mybundle: : Invalid package name: '*'
> [ERROR] Bundle mygroupId:myartifactId:mybundle: : 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

View raw message