Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [concierge-dev] Installing bundles from workspace

We could think about supporting the workspace layout as a bundle format in the near future. It might take a little effort but there is already a reasonable abstraction of bundle formats (currently Jar file and exploded Jar file) in the BundleImpl. Once we have this in place we could provide a plugin to expose Concierge as an OSGi framework to the Eclipse launcher.

Cheers,

Jan.

Inactive hide details for Tim Verbelen ---08/13/2014 06:41:21 PM---Hi Jochen, I often use bnd to build and run my OSGi bundles.Tim Verbelen ---08/13/2014 06:41:21 PM---Hi Jochen, I often use bnd to build and run my OSGi bundles. You can easily specify

From: Tim Verbelen <tim.verbelen@xxxxxxxxxxxxxx>
To: concierge-dev@xxxxxxxxxxx
Date: 08/13/2014 06:41 PM
Subject: Re: [concierge-dev] Installing bundles from workspace
Sent by: concierge-dev-bounces@xxxxxxxxxxx





Hi Jochen,

I often use bnd to build and run my OSGi bundles. You can easily specify a bndrun file with all the bundles you want and use org.eclipse.concierge as your runtime framework, provided that you have a repository with the latest concierge build in (I use my personal one
http://users.ugent.be/~tverbele/repositories/concierge/)

If you combine this with the bndtools plugin in Eclipse, it is easy to create a bndtools workspace where you can automatically run and update your bundles directly from your workspace.

Cheers,

Tim

On 08/11/2014 09:26 AM, Jochen Hiller wrote:
    Hi Jan, Tim,

    I came across due to integrating more and more bundles which required minor changes, that it is time consuming from a developer perspective always build the bundles first, and then start the Concierge OSGi framework again with updated bundles.

    Did you thought about supporting bundles directly from a workspace? Like Equinox is doing that?

    There is yet an ExplodedJarBundleRevision which could be reused when a bundle is yet "exploded" in workspace. The challenges I see here is that the compiled class files are sometimes in bin folder, sometimes in target/classes folder, dependent on build system. All other resources should be "just there".

    I agree in general that the framework should not be "polluted" by too much code which is not necessary for normal usage. But maybe we find a simple solution without big overhead on code complexity and size.

    Bye, Jochen



    _______________________________________________
    concierge-dev mailing list
    concierge-dev@xxxxxxxxxxx
    To change your delivery options, retrieve your password, or unsubscribe from this list, visit
    https://dev.eclipse.org/mailman/listinfo/concierge-dev


--
Tim Verbelen
Department of Information Technology
Broadband Communication Networks (IBCN)
Ghent University - iMinds
Gaston Crommenlaan 8 (Bus 201), B-9050 Gent, Belgium
T: +32 9 33 14940 ; T Secr: +32 9 33 14900
F: +32 9 33 14899
E:
tim.verbelen@xxxxxxxxxxxxxx
W :
www.ibcn.intec.UGent.be
_______________________________________________
concierge-dev mailing list
concierge-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/concierge-dev

GIF image


Back to the top