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 Tue, 17 Jun 2014 08:19:02 GMT

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

Hervé Barrault commented on FELIX-4205:

Hi, I tried with maven-bundle-plugin-2.4.1-20140616.131723-6

Adding the empty <Bundle-Activator></Bundle-Activator>

The Build is succesfull.
No Bundle-Activator is defined in the MANIFEST.
Seems good for my use case.

No deployment tested as I have some problems with the new "feature" Require-Capability but
out of the scope for this issue.

> 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