[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [virgo-dev] Hangout 14.12.2016


I added one more item to the agenda, if time is available I'd like to discuss an idea for bridging PDE and Maven in the context of Virgo, so that one could use PDE and have dependencies automatically managed by Maven.

In the Eclipse echo-system there are two main approaches when working with OSGi, plus a third one if you use the Virgo tools:

1) Eclipse PDE
2) BND Tools
3) Virgo Tools Bundlor

PDE is maybe the most mature tool, but it is unoptimal because it resolves dependencies against a PDE Target Platform Definition (TPD).
A TPD can be created as a collection of folders containing bundles and P2 sites, but it does not support Maven.

Since 1.5 of the Virgo Tools, it's possible to develop for Virgo using PDE. The Tools can read the Virgo Runtime repository config and create a PDE TPD for you automatically. This approach is good for PDE, but you are left with the annoyance of having to collect and copy your dependencies in file system folders that you will list in the Virgo repository config file, so that Virgo finds them at runtime and PDE finds them at compile time as content of the TPD.

I think I found a possible way to bridge PDE, Virgo and Maven toghether, so that PDE could build the target platform from Maven dependencies.

I could extend PDE with a new type of location for bundles (via an already existing extension point).
This new location would be implemented to iterate over all the Virgo projects in the workspace, inspect the content of their Maven classpath container entry, and add contained bundles to the TPD. In addition to that the tools should provide a new classpath container entry that lists the bundles in
/ext and /usr folders (e.g. "Virgo Runtime" classpath entry).

In this way PDE would use a target platform definition that contains the maven dependencies of the
workspace projects.

At publish time, the Maven dependencies should be copied into the stage folder (the extra Virgo repository folder) which is created by the Virgo Tools before starting the server.

It should work.

On Mon, Dec 12, 2016 at 12:12 PM, Daniel Marthaler <dmarthaler@xxxxxxx> wrote:
Hi Tony

It's great that you can join the Hangout as well. I hope to be able to define how to proceed with bug 500758 during our meeting so we can work together towards a solution which works on VM's without the timeout issue.Â


Am 12.12.2016 um 11:32 schrieb Tony Ganchev <tganchev@xxxxxxxxxx>:

Hi all,

I reportedÂBug 500758Âand I'd also joinÂthe Hangout.



From: virgo-dev-bounces@xxxxxxxxxxx <virgo-dev-bounces@xxxxxxxxxxx> on behalf of dmarthaler@xxxxxxx <dmarthaler@xxxxxxx>
Sent: Monday, December 12, 2016 8:53:16 AM
To: Virgo Project
Subject: [virgo-dev] Hangout 14.12.2016

Dear All

Here is the Agenda proposal for our upcoming Hangout this Week on the 14th of December at 9:00pm (CET):

  1. Updating Virgo Wiki for Contributors regarding Git branching model

  2. Virgo Tools status update Plan-Project-Wizard

  3. Virgo Tools documentation publishing

  4. Bundlor version 1.1.3.M01 on Maven Central and Virgo Download page

  5. Update legal notes in virgo-build repo

  6. Reactivation of Snaps Project (thanks to Stefan Zugal for his contribution with Bug 357814)

  7. Help for Bug 500758 is required

  8. Upgrade Spring dependency from 4.2.4 to 4.3.4

  9. Status of Gemini Web 3.0.0

  10. Official release date for Virgo 3.7.0.RELEASE

Link to Hangout: https://hangouts.google.com/hangouts/_/eclipsesource.com/virgo
Link to Google Docs: https://docs.google.com/document/d/1lCsqxdI-pOz7PdpY7D_Q_zGJzK4WKA0aEGgL9BZsBPY/edit#

@Florian & @Giamma: Please review the Agenda and amend it if you feel we should add other topics as well. I really hope we get through all the topics within the Hangout.


virgo-dev mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit

virgo-dev mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit

Gian Maria Romanato
<gm.romanato (at) gmail (dot) com>