oodt-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Tom Barber <tom.bar...@meteorite.bi>
Subject Re: Osgi stuff
Date Thu, 23 Jul 2015 18:54:53 GMT
I'll file it. I'll get to it because it's part of my project and being able
to use a "feature" to deploy it will make my life far easier.

Tom
On 23 Jul 2015 19:23, "Chris Mattmann" <mattmann@apache.org> wrote:

> Totally agree!
>
> JIRA issue time and if no one gets to it, maybe GSoC or student
> project?
>
> —
> Chris Mattmann
> chris.mattmann@gmail.com
>
>
>
>
>
>
> -----Original Message-----
> From: Tom Barber <tom.barber@meteorite.bi>
> Reply-To: <dev@oodt.apache.org>
> Date: Thursday, July 23, 2015 at 11:21 AM
> To: <dev@oodt.apache.org>
> Subject: Osgi stuff
>
> >Taking that off of there and onto here about your mega bundle stuff. One
> >thing I would like to do with this little project over time is create a
> >karaf feature so people could run "feature:install oodt.xyz" and karaf
> >spin
> >up working OODT components radix style. I think that would be very useful.
> >On 23 Jul 2015 19:08, "chrismattmann" <git@git.apache.org> wrote:
> >
> >> Github user chrismattmann commented on the pull request:
> >>
> >>     https://github.com/apache/oodt/pull/23#issuecomment-124189993
> >>
> >>     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
> >>
> >>
> >> ---
> >> If your project is set up for it, you can reply to this email and have
> >>your
> >> reply appear on GitHub as well. If your project does not have this
> >>feature
> >> enabled and wishes so, or if the feature is enabled but not working,
> >>please
> >> contact infrastructure at infrastructure@apache.org or file a JIRA
> >>ticket
> >> with INFRA.
> >> ---
> >>
>
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message