You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@oltu.apache.org by "Antonio Sanso (JIRA)" <ji...@apache.org> on 2016/08/02 11:19:20 UTC

[jira] [Updated] (OLTU-134) Broken OSGi metadata

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

Antonio Sanso updated OLTU-134:
-------------------------------
    Fix Version/s: commons-encodedtokens-1.0.1

> Broken OSGi metadata
> --------------------
>
>                 Key: OLTU-134
>                 URL: https://issues.apache.org/jira/browse/OLTU-134
>             Project: Apache Oltu
>          Issue Type: Improvement
>          Components: general
>    Affects Versions: oauth2-0.31
>            Reporter: Łukasz Dywicki
>            Assignee: Simone Tripodi
>              Labels: osgi
>             Fix For: commons-encodedtokens-1.0.1
>
>         Attachments: OLTU-134.patch, karaf oltu.png
>
>
> Currently Oltu uses maven-bundle-plugin to generate manifest entries and maven jar plugin to add some extra headers. This approach is error prone because same thing is done in two different places and OSGi headers may be easily broken if there is no tests deploying these jars in framework.
> Switching packaging type to bundle allows to use only one place to generate manifest entries, including also these custom, and adds validation phase in build to verify if all headers are just fine.



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