Return-Path: Delivered-To: apmail-incubator-felix-dev-archive@www.apache.org Received: (qmail 92323 invoked from network); 14 Jul 2006 12:44:30 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 14 Jul 2006 12:44:30 -0000 Received: (qmail 23879 invoked by uid 500); 14 Jul 2006 12:44:29 -0000 Delivered-To: apmail-incubator-felix-dev-archive@incubator.apache.org Received: (qmail 23802 invoked by uid 500); 14 Jul 2006 12:44:29 -0000 Mailing-List: contact felix-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: felix-dev@incubator.apache.org Delivered-To: mailing list felix-dev@incubator.apache.org Received: (qmail 23525 invoked by uid 99); 14 Jul 2006 12:44:27 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 14 Jul 2006 05:44:27 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of Jeff_McAffer@ca.ibm.com designates 32.97.182.142 as permitted sender) Received: from [32.97.182.142] (HELO e2.ny.us.ibm.com) (32.97.182.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 14 Jul 2006 05:44:25 -0700 Received: from d01relay04.pok.ibm.com (d01relay04.pok.ibm.com [9.56.227.236]) by e2.ny.us.ibm.com (8.12.11.20060308/8.12.11) with ESMTP id k6EChxDj027893 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Fri, 14 Jul 2006 08:44:00 -0400 Received: from d01av01.pok.ibm.com (d01av01.pok.ibm.com [9.56.224.215]) by d01relay04.pok.ibm.com (8.13.6/NCO/VER7.0) with ESMTP id k6EChxOj291134 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Fri, 14 Jul 2006 08:43:59 -0400 Received: from d01av01.pok.ibm.com (loopback [127.0.0.1]) by d01av01.pok.ibm.com (8.12.11.20060308/8.13.3) with ESMTP id k6EChxix012970 for ; Fri, 14 Jul 2006 08:43:59 -0400 Received: from d25ml04.torolab.ibm.com (d25ml04.torolab.ibm.com [9.26.6.105]) by d01av01.pok.ibm.com (8.12.11.20060308/8.12.11) with ESMTP id k6EChxKx012954 for ; Fri, 14 Jul 2006 08:43:59 -0400 In-Reply-To: <44B78C94.2000208@interfree.it> To: felix-dev@incubator.apache.org Subject: Re: Running Felix within Eclipse MIME-Version: 1.0 X-Mailer: Lotus Notes Release 7.0 HF144 February 01, 2006 From: Jeff McAffer Message-ID: Date: Fri, 14 Jul 2006 08:43:56 -0400 X-MIMETrack: Serialize by Router on D25ML04/25/M/IBM(Release 6.5.4|March 27, 2005) at 07/14/2006 08:43:58, Serialize complete at 07/14/2006 08:43:58 Content-Type: multipart/alternative; boundary="=_alternative 0045AC2D852571AB_=" X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N --=_alternative 0045AC2D852571AB_= Content-Type: text/plain; charset="US-ASCII" I assume here that you are NOT using PDE in eclipse right? That is, from the Eclipse perspective you are just developing Java code in Java projects. It also seems that you are using maven to do the builds. If this is correct, you should end up with a set of Maven created JARs wherever Maven put them. From there all you should have to do is create a Java Launch Configuration and run. Of course if you change the code in the workspace then you have to run Maven again and get new JARs generated. Not knowing Felix code at all but based on our Equinox experience I suspect the problem with Felix not picking up your new code is because Felix copies the JARs when you install the bundles. I recall that Richard added the ability to intsall bundles by reference but don't know the details (I assume it works somewhat like the support in Equinox). Perhaps you could use that for installing your bundles? Note thta you may still have refresh problems when changing manifest information or anything else the Felix (or installed bundles) cache. BTW, in case people don't understand, this is exactly the sort of stuff that PDE is designed to take care of for you. It does the classpath management, package visibility, building, cache management and framework launching. Developers don't have to mess with classpaths, building, ... They just code and run. It would be interesting to see how these facilities could be brought to bear on Felix. For example, since there is no standard way of launching frameworks, PDE currently only launches Equinox. Perhaps someone in the this community would be interested in contributing support for launching Felix? Jeff Stefano Lenzi 07/14/2006 08:22 AM Please respond to felix-dev@incubator.apache.org To felix-dev@incubator.apache.org cc Subject Re: Running Felix within Eclipse > > Yes I had osgi.core in my classpath due to project dependencies of the > project org.apache.felix.main to org.osgi.core so to get it working > had to: > - go to run configuration > - go to classpath > - ensure that felix.jar is there( if you followed the instruction of > Clement should be here) otherwise add it > - move it up so that felix.jar become the first line under User Entries > > Now is working back ^_^ > > I was happy too early... :-S Right now, I'm able to run Felix within Eclipse, but when I update the source code of my bundle and then I start Felix, Felix do not notice the difference(Felix continues to use the old binary code). So I end with a binary that is not synched with the sources and also without the update that I have made to it. Any idea? Stefano "Kismet" Lenzi --=_alternative 0045AC2D852571AB_=--