You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cocoon.apache.org by "Grzegorz Kossakowski (JIRA)" <ji...@apache.org> on 2007/09/02 18:39:19 UTC

[jira] Commented: (COCOON-1836) Cocoon blocks development support

    [ https://issues.apache.org/jira/browse/COCOON-1836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12524360 ] 

Grzegorz Kossakowski commented on COCOON-1836:
----------------------------------------------

How much of these plans is still relevant?

Creation of Cocoon blocks is handled by Maven archetypes and we have no OSGi in Cocoon, yet.

Could someone more involved in this comment?

> Cocoon blocks development support
> ---------------------------------
>
>                 Key: COCOON-1836
>                 URL: https://issues.apache.org/jira/browse/COCOON-1836
>             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 or 
>   a deployment descriptor. Make it configureable so that you can easily switch between bundled
>   versions and exploded bundles mounted as projects in Eclipse
> - Create a Mojo that copies all needed external libraries into ./target/osgi/lib so that they
>   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.