Return-Path: X-Original-To: apmail-karaf-issues-archive@minotaur.apache.org Delivered-To: apmail-karaf-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id E18C810A3E for ; Fri, 3 Jan 2014 08:28:19 +0000 (UTC) Received: (qmail 38298 invoked by uid 500); 3 Jan 2014 08:28:08 -0000 Delivered-To: apmail-karaf-issues-archive@karaf.apache.org Received: (qmail 38164 invoked by uid 500); 3 Jan 2014 08:27:56 -0000 Mailing-List: contact issues-help@karaf.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@karaf.apache.org Delivered-To: mailing list issues@karaf.apache.org Received: (qmail 38138 invoked by uid 99); 3 Jan 2014 08:27:52 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 03 Jan 2014 08:27:52 +0000 Date: Fri, 3 Jan 2014 08:27:52 +0000 (UTC) From: "Adam Wehner (JIRA)" To: issues@karaf.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (KARAF-2665) EIK with custom Karaf distribution on Eclipse 3.8.x and 4.x MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/KARAF-2665?page=3Dcom.atlassia= n.jira.plugin.system.issuetabpanels:all-tabpanel ] Adam Wehner updated KARAF-2665: ------------------------------- Description:=20 I had the need to use EIK with a custom Karaf distribution in a newer Eclip= se version. Both points did not work with EIK. So I have fixed a bunch of i= ssues with my colleague Markus Kr=C3=BCger in order to make it work for our= scenario: 1. An issue with Maven-URLs containing an @id annotation. No artifact resol= ution 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 sever= al features files now. (Custom Distribution Issue) 4. All available bundles are activated for a new launch configuration. (Gen= eral Issue)=20 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 Ecl= ipse 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 h= appy, if this changes could be merged to the EIK trunk. was: I had the need to use EIK with a custom Karaf distribution in a newer Eclip= se version. Both points did not work with EIK. So I have fixed a bunch of i= ssues with my colleague Markus Kr=C3=BCger in order to make it work for our= scenario: 1. An issue with Maven-URLs containing an @id annotation. No artifact resol= ution 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 sever= al features files now. (Custom Distribution Issue) 4. All available bundles are activated for a new launch configuration. (Gen= eral Issue)=20 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 Ecl= ipse 3.8.2 and Eclipse 4.3.1. See the attachement for a patch with our solutions. It would make me very h= appy, if this changes could be merged to the EIK trunk. > 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 > Attachments: eik.patch > > > I had the need to use EIK with a custom Karaf distribution in a newer Ecl= ipse version. Both points did not work with EIK. So I have fixed a bunch of= issues with my colleague Markus Kr=C3=BCger in order to make it work for o= ur scenario: > 1. An issue with Maven-URLs containing an @id annotation. No artifact res= olution 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 t= he target definition file is not created yet. (General Issue) > 3. Bundle start levels for the launch configuration are read from the sev= eral features files now. (Custom Distribution Issue) > 4. All available bundles are activated for a new launch configuration. (G= eneral Issue)=20 > 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 E= clipse 3.8.2 and Eclipse 4.3.1. Attention: With this patch EIK is not worki= ng with Eclipse 3.7.x or lower, because the target definition API has chang= ed. > 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)