[
https://issues.apache.org/jira/browse/OODT-859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14639300#comment-14639300
]
ASF GitHub Bot commented on OODT-859:
-------------------------------------
Github user buggtb commented on the pull request:
https://github.com/apache/oodt/pull/23#issuecomment-124190700
I'll try and swap them back the output is the same you still get a jar but
it wasn't packaging properly with jar defined but that's just plugin
annoyances. But yes I'll move those out somewhere.
Tom
On 23 Jul 2015 19:08, "Chris Mattmann" <[email protected]> wrote:
> gotcha. That's fine, well then I wouldn't change the default packaging of
> the components from jar to bundle then. As you are doing in a profile
> anyways with the plugin and dependencies, make the packaging also
something
> that is dependent on the profile. I am +1 as long as it doesn't change the
> default behavior of jar packaging on these. @buggtb
> <https://github.com/buggtb>
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/apache/oodt/pull/23#issuecomment-124189993>.
>
> Convert Jars to OSGI Bundles
> ----------------------------
>
> Key: OODT-859
> URL: https://issues.apache.org/jira/browse/OODT-859
> Project: OODT
> Issue Type: Bug
> Reporter: Tom Barber
> Assignee: Tom Barber
> Priority: Minor
>
> For various reasons we should include the OSGI compliant MANIFEST headers.
> The poms need updating to build it that is all.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
