From user-return-18548-archive-asf-public=cust-asf.ponee.io@karaf.apache.org Sun May 13 17:47:34 2018 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id D48D8180636 for ; Sun, 13 May 2018 17:47:33 +0200 (CEST) Received: (qmail 88826 invoked by uid 500); 13 May 2018 15:47:32 -0000 Mailing-List: contact user-help@karaf.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@karaf.apache.org Delivered-To: mailing list user@karaf.apache.org Received: (qmail 88816 invoked by uid 99); 13 May 2018 15:47:32 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 13 May 2018 15:47:32 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 5B8991A2886 for ; Sun, 13 May 2018 15:47:32 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 0.3 X-Spam-Level: X-Spam-Status: No, score=0.3 tagged_above=-999 required=6.31 tests=[KAM_LAZY_DOMAIN_SECURITY=1, RCVD_IN_DNSWL_LOW=-0.7] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id KjXx_ZzsQmgf for ; Sun, 13 May 2018 15:47:30 +0000 (UTC) Received: from relay2-d.mail.gandi.net (relay2-d.mail.gandi.net [217.70.183.194]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTPS id E4C575F17B for ; Sun, 13 May 2018 15:47:29 +0000 (UTC) X-Originating-IP: 82.238.224.4 Received: from [192.168.134.132] (bre91-1-82-238-224-4.fbx.proxad.net [82.238.224.4]) (Authenticated sender: jb@nanthrax.net) by relay2-d.mail.gandi.net (Postfix) with ESMTPSA id DF9FC40005 for ; Sun, 13 May 2018 17:47:22 +0200 (CEST) Subject: Re: Odd feature repo behavior in 4.2.0 custom distro To: user@karaf.apache.org References: <8B216C1A-D889-400B-9C6C-94C7035E074C@me.com> <6a968c09-37eb-8f30-ca54-bcfede01017f@openobject.fr> From: =?UTF-8?Q?Jean-Baptiste_Onofr=c3=a9?= Message-ID: Date: Sun, 13 May 2018 17:47:22 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit Hi, eclipselink should be not a startup feature: startup feature is not actually a feature, the bundles contained in the feature are added in etc/startup.properties. So eclipselink should be a boot feature. Same for jndi. The scope runtime on deps means that they will be added in the Karaf repo. I don't see the standard repo in your pom. I advise to fix that first. Regards JB On 13/05/2018 17:12, Erwin Hogeweg wrote: > François, >> >> Can you share your pom.xml from the assembly module ? >> > Attached. > > > > > Erwin >> Le 13/05/2018 à 18:11, Erwin Hogeweg a écrit : >>> Hi François, >>> >>> Thanks for your reply. >>>> >>>> Did the feature:list show your feature un your custom distribution ? >>>> >>> Nope. >>>> >>>> You also set log to debug and see if there is something wrong. >>>> >>> Hmmm… >>> 2018-05-13T15:48:05,948 | DEBUG | activator-1-thread-1 | >>> AetherBasedResolver          | 2 - org.ops4j.pax.url.mvn - 2.5.4 | >>> Resolved >>> (com.seecago.rome.server:rome-features:xml:features:1.0.0-SNAPSHOT) >>> as >>> <…>/Users/erwin/work/Rome/trunk/src/server/karaf.distro/target/assembly/system/com/seecago/rome/server/rome-features/1.0.0-SNAPSHOT/rome-features-1.0.0-SNAPSHOT-features.xml >>> >>> … I think I see what the issue is… the referenced feature is empty, >>> or pretty much empty. >>> >>> >>> >> name="rome-features"/> >>> >>> That is not the feature.xml I had in mind. The one from .m2 looks >>> much different. Wasn’t there a Jira issue raised a couple of weeks >>> ago about feature.xml not being generated completely? Or was that a >>> config file? I can’t find it anymore. >>> >>> >>> >>> Thanks, >>> >>> Erwin >>>> >>>> François >>>> >>>> Le 13 mai 2018 00:43, Erwin Hogeweg >>> > a écrit : >>>> >>>> Hi - >>>> >>>> I ran into an issue with a custom distro. >>>> >>>> Installing a local feature from the console works just fine, but >>>> when I include the feature repo in the >>>> org.apache.karaf.features.cfg file the feature won’t load >>>> because karaf thinks it doesn’t exist. >>>> >>>> This is what I get when I install from the console while the : >>>> >>>> karaf@root()> feature:repo-add mvn:com.myproject/my-features/1.0.0-SNAPSHOT/xml/features >>>> karaf@root()> feature:repo-list >>>>   my-features-1.0.0-SNAPSHOT               │ >>>> mvn:com.myproject/my-features/1.0.0-SNAPSHOT/xml/features >>>> karaf@root()> feature:install my-feature >>>> karaf@root()> >>>> >>>> This is the entry in the distro pom to add the repo to the >>>> config file: >>>> >>>> >>>> com.myproject >>>> my-features >>>> ${project.version} >>>> features >>>> xml >>>> runtime >>>> >>>> >>>> >>>> And this is what I get when I install the feature in the distro: >>>> >>>> feature:repo-list >>>>   my-features                     │ >>>> mvn:com.myproject/my-features/1.0.0-SNAPSHOT/xml/features >>>> karaf@root()> feature:install my-feature >>>> Error executing command: No matching features for my-feature/0 >>>> >>>> Not sure what is going on here. In the first case the Repository >>>> name shown is the feature name as defined in feature.xml, in the >>>> second case it is the feature artifact name as defined in the >>>> pom.xml. >>>> >>>> I checked the docs and compared my distro pom with the 4.2.0 >>>> source code. I don’t see (...) any glaring mistakes, but >>>> obviously something must be wrong. >>>> >>>> Any suggestions are greatly appreciated. >>>> >>>> >>>> Kind Regards, >>>> >>>> Erwin >>>> >>> >> >