oltu-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Antonio Sanso (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (OLTU-134) Broken OSGi metadata
Date Tue, 02 Aug 2016 11:24:20 GMT

     [ 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: jose-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, jose-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)

Mime
View raw message