felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sahoo (JIRA)" <j...@apache.org>
Subject [jira] Commented: (FELIX-548) Import-Package version qualifiers vary depending on dependency scope.
Date Wed, 04 Feb 2009 12:23:59 GMT

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

Sahoo commented on FELIX-548:


Per your last comment, this bug has been fixed. I am curious to know what was the fix. As
per most of the comments, the behavior was intended.


> Import-Package version qualifiers vary depending on dependency scope.
> ---------------------------------------------------------------------
>                 Key: FELIX-548
>                 URL: https://issues.apache.org/jira/browse/FELIX-548
>             Project: Felix
>          Issue Type: Bug
>          Components: Maven Bundle Plugin
>    Affects Versions: maven-bundle-plugin-1.4.0
>         Environment: N/A
>            Reporter: Thomas Dewire
>            Assignee: Stuart McCulloch
>            Priority: Minor
>             Fix For: maven-bundle-plugin-1.4.2
>         Attachments: bugtest3.tar.gz
> The produced Import-Package directive appears to vary depending on the declared scope
of a dependency.
> Assuming that a dependency is a valid OSGi bundle:
> - "compile" scope will include a version qualifier (eg. Import-Package: org.springframework.core;version="2.5.4").
> - "provided" scope will not include a version qualifier (eg. Import-Package: org.springframework.core).
> In this case, I believe the 'compile' behavior is correct.
> I have not tested all possible scopes. A similar inconsistency might exist for runtime,
test, etc.

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

View raw message