filippo balicchia created KARAF-1950:
----------------------------------------
Summary: 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
Fix For: eik-3.0.0
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
