[
https://issues.apache.org/jira/browse/KARAF-2665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré resolved KARAF-2665.
-----------------------------------------
Resolution: Fixed
> EIK with custom Karaf distribution on Eclipse 3.8.x and 4.x
> -----------------------------------------------------------
>
> Key: KARAF-2665
> URL: https://issues.apache.org/jira/browse/KARAF-2665
> Project: Karaf
> Issue Type: New Feature
> Components: eik-core
> Affects Versions: eik-0.10.0
> Reporter: Adam Wehner
> Assignee: Jean-Baptiste Onofré
> Fix For: eik-0.10.0
>
> Attachments: eik.patch
>
>
> I had the need to use EIK with a custom Karaf distribution in a newer Eclipse
> version. Both points did not work with EIK. So I have fixed a bunch of issues
> with my colleague Markus Krüger in order to make it work for our scenario:
> 1. An issue with Maven-URLs containing an @id annotation. No artifact
> resolution was possible than. - (General Issue)
> 2. The launch configuration file is not created when the "Karaf Project" is
> created. Because this worked only if the target platform was already set.
> Which can never happen at first start, because the "Karaf Project" with the
> target definition file is not created yet. (General Issue)
> 3. Bundle start levels for the launch configuration are read from the several
> features files now. (Custom Distribution Issue)
> 4. All available bundles are activated for a new launch configuration.
> (General Issue)
> 5. NPE avoided: if target platform not set (General Issue)
> 6. Made EIK runnable on Eclipse 3.8.x and higher. I have tested it with
> Eclipse 3.8.2 and Eclipse 4.3.1. Attention: With this patch EIK is not
> working with Eclipse 3.7.x or lower, because the target definition API has
> changed.
> See the attachement for a patch with our solutions. It would make me very
> happy, if this changes could be merged to the EIK trunk.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
