+1 sounds great to me. --Paul
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Paul Ramirez, M.S. Technical Group Supervisor Computer Science for Data Intensive Applications (398M) Instrument Software and Science Data Systems Section (398) NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA Office: 158-264, Mailstop: 158-242 Email: [email protected]<mailto:[email protected]> Office: 818-354-1015 Cell: 818-395-8194 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ On Jul 23, 2015, at 11:23 AM, Chris Mattmann <[email protected]<mailto:[email protected]>> wrote: Totally agree! JIRA issue time and if no one gets to it, maybe GSoC or student project? — Chris Mattmann [email protected]<mailto:[email protected]> -----Original Message----- From: Tom Barber <[email protected]> Reply-To: <[email protected]> Date: Thursday, July 23, 2015 at 11:21 AM To: <[email protected]> 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" <[email protected]> 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 [email protected] or file a JIRA ticket with INFRA. ---
