cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Fagerstrom (JIRA)" <>
Subject [jira] Commented: (COCOON-1836) Cocoon blocks development support
Date Sun, 02 Sep 2007 18:19:19 GMT


Daniel Fagerstrom commented on COCOON-1836:

The current Cocoon-OSGi development in the white board uses the Felix Maven bundle plugin
that makes it fairly easy to create bundles from ordinary jars. But it doesn't work that well
together with the PDE that (at least a year ago) required that the is fixed rather
than generated. It seem like the Eclipse developers and large parts of the rest OSGi-community
has different philosophy about manifest generation so there is probably not much to do about

The assembly plugin is used in the whiteboard for collecting together all needed bundles,
so there is no need for some special purpose Mojo for that.

So all the items above is either solved or less relevant with the current development strategy.

> Cocoon blocks development support
> ---------------------------------
>                 Key: COCOON-1836
>                 URL:
>             Project: Cocoon
>          Issue Type: Task
>          Components: - Servlet service framework
>            Reporter: Reinhard Poetz
>            Assignee: Reinhard Poetz
> some ideas (DF/RP)
> - go through the tutorial of PDE development in "Eclipse Rich Client Platform"
> - Talk to Equinox and Felix how they manage the development process
> - Talk to the Eclipse PDE community as all resources need to be in the root directory
> - Create a Mojo that creates the target platform containing all bundles out of a pom.xml
>   a deployment descriptor. Make it configureable so that you can easily switch between
>   versions and exploded bundles mounted as projects in Eclipse
> - Create a Mojo that copies all needed external libraries into ./target/osgi/lib so that
>   can be seen by the PDE (a bit of a hack but well ...)
> - extend the Felix OSGi plugin so that you can change the path for integrated plugins

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message