You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@karaf.apache.org by "Jean-Baptiste Onofré (JIRA)" <ji...@apache.org> on 2012/12/20 10:35:13 UTC

[jira] [Commented] (KARAF-1950) Eik pde archetype for Camel

    [ https://issues.apache.org/jira/browse/KARAF-1950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13536890#comment-13536890 ] 

Jean-Baptiste Onofré commented on KARAF-1950:
---------------------------------------------

Fixed on EIK trunk (after some adaptations): http://svn.apache.org/viewvc?view=revision&revision=1424379
                
> Eik pde archetype for Camel
> ---------------------------
>
>                 Key: KARAF-1950
>                 URL: https://issues.apache.org/jira/browse/KARAF-1950
>             Project: Karaf
>          Issue Type: Task
>          Components: eik-core
>            Reporter: filippo balicchia
>            Assignee: Jean-Baptiste Onofré
>             Fix For: eik-0.9.0
>
>         Attachments: archetypes.tar.bz2
>
>
> The goal of EIK is to help user to develop bundle and install it in karaf.
> Most of the archetype present were created using the maven-bundle-plugin, and the bundle created with
> it is difficult to align with eclipse runconfiguration.
> With m2e is possible to do it but alignment between the bundles in the workspace and runconfiguration
> works in random manner
> This need was born from a thread in user/dev group.
> To help karaf user to use EIK for developer bundle I think to create a Camel PDE Archetype.
> Layout of the project is this:
> {noformat}
> ├── META-INF
> │   ├── MANIFEST.MF
> │   └── spring
> │       └── beans.xml
> ├── org.apache.eik.pde.examples.cfg
> ├── pom.xml
> └── src
>     ├── main
>     │   ├── java
>     │   │   └── org
>     │   │       └── apache
>     │   │           ├── MyRouteBuilder.java
>     │   │           └── MyTransform.java
>     │   └── resources
>     └── test
>         └── java
>             └── org
> {noformat}
> I need to put the folder spring/bean.xml under META-INF cause in eclipse workspace spring dm at runtime search that position.
> Usually the file "bean.xml" is under src/resources/spring/ and during compilation in put where spring dm wait descriptor. Obviously the position can be change as indicated in 
> http://static.springsource.org/osgi/docs/1.1.x/reference/html/app-deploy.html#app-deploy:headers
> The jar product works both inside and outside eclipse.
>  
> I don't used maven-bundle-plugin because if you use (Eclipse/PDE integration) manifest is updated at compile time. 
> In this manner you lost the  advantages of use eclipse ide, add import/export package from target platform that EIK create for us.
> The second advantage is the possibility of using tycho.
> Please see the attach. In zip there in folder with archetype and pom with apache licence
> An example of use can be found in eik manual

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira