[
https://issues.apache.org/jira/browse/OODT-859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14639277#comment-14639277
]
ASF GitHub Bot commented on OODT-859:
-------------------------------------
Github user buggtb commented on a diff in the pull request:
https://github.com/apache/oodt/pull/23#discussion_r35351331
--- Diff: crawler/pom.xml ---
@@ -27,6 +27,7 @@ the License.
<artifactId>cas-crawler</artifactId>
<name>Catalog and Archive Crawling Framework</name>
<description>The Catalog and Archive Service Crawling
Framework.</description>
+ <packaging>bundle</packaging>
--- End diff --
Makes me sad I spent hours copying and pasting!
But your plan also doesn't fit my idea because bundling all of oodt into a
mega bundle is a bloat that isn't required. For example I just want to
deploy a file manager and expose it via DOSGI to a main server, why would I
deploy a massive jar for a very light weight requirement.
I started by creating a wrapper jar for it but I figured as we're only
changing a very default manifest file actually pushing it down to the Base
jars made more sense.
On 23 Jul 2015 18:48, "Chris Mattmann" <[email protected]> wrote:
> In crawler/pom.xml
> <https://github.com/apache/oodt/pull/23#discussion_r35350102>:
>
> > @@ -27,6 +27,7 @@ the License.
> > <artifactId>cas-crawler</artifactId>
> > <name>Catalog and Archive Crawling Framework</name>
> > <description>The Catalog and Archive Service Crawling
Framework.</description>
> > + <packaging>bundle</packaging>
>
> maybe we shouldn't change the default packaging per project, but instead
> create an oodt-bundle that is packaged as an OSGI bundle that combines the
> constituent sub projects.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/apache/oodt/pull/23/files#r35350102>.
>
> 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)
