Isn’t this exactly what enRoute was trying to do with the distros?

Regards,

Tim

> On 23 Nov 2016, at 16:05, Raymond Auge <raymond.a...@liferay.com> wrote:
> 
> @Peter this is exactly a scenario I'd love to be able to eliminate by 
> exposing the target runtime as a repo which we can specify as the the BASE 
> for the resolver.
> 
> - Ray
> 
> On Wed, Nov 23, 2016 at 11:04 AM, Tim Ward <t...@telensa.com 
> <mailto:t...@telensa.com>> wrote:
> So, if I manually delete
> 
> org.apache.felix.scr
> 
> from -runbundles then both symptoms go away.
> 
> All I've got to do now is try to find out how to stop the Resolve button 
> putting it back in every time?
> 
> 
> On 23/11/2016 15:58, Peter Kriens wrote:
>>> That sounds a bit like scr is started twice.
>> Sounds? Are their other possible explanations?
>> 
>> Kind regards,
>> 
>>      Peter Kriens
>> 
>>> On 23 Nov 2016, at 16:49, Christian Schneider <ch...@die-schneider.net 
>>> <mailto:ch...@die-schneider.net>> wrote:
>>> 
>>> On 23.11.2016 16:47, Tim Ward wrote:
>>>> OK, doesn't look like configuration.
>>>> 
>>>> - Comment out @RequireConfigureExtender
>>>> - Resolve
>>>> - Confirm that osgi.enroute.configurer.simple.provider no longer appears 
>>>> in -runbundles
>>>> - Confirm that osgi.enroute.configurer.simple.provider no longer appears 
>>>> in Karaf's "list" command
>>>> - Restart Karaf and run it again
>>>> 
>>>> and the same happens.
>>>> 
>>>> By the way, I also get the following from time to time in the log, which 
>>>> I've ignored so far, but it does suggest that my component isn't the only 
>>>> thing being started twice?
>>>> 
>>>> 2016-11-23 15:43:43,266 | INFO  | pool-61-thread-3 | ScrServiceMBeanImpl   
>>>>            | 55 - org.apache.karaf.scr.management - 4.0.7 | Activating the 
>>>> Apache Karaf SCR Service MBean
>>>> 2016-11-23 15:43:43,268 | ERROR | pool-61-thread-3 | ScrServiceMBeanImpl   
>>>>            | 55 - org.apache.karaf.scr.management - 4.0.7 | Exception 
>>>> registering the SCR Management MBean: org.apache.karaf:type=scr,name=root
>>>> javax.management.InstanceAlreadyExistsException: 
>>>> org.apache.karaf:type=scr,name=root
>>>>    at 
>>>> com.sun.jmx.mbeanserver.Repository.addMBean(Repository.java:437)[:1.8.0_60]
>>> That sounds a bit like scr is started twice.
>>> 
>>> Christian
>>> 
>>> -- 
>>> Christian Schneider
>>> http://www.liquid-reality.de <http://www.liquid-reality.de/>
>>> 
>>> Open Source Architect
>>> http://www.talend.com <http://www.talend.com/>
>>> 
>>> _______________________________________________
>>> OSGi Developer Mail List
>>> osgi-dev@mail.osgi.org <mailto:osgi-dev@mail.osgi.org>
>>> https://mail.osgi.org/mailman/listinfo/osgi-dev 
>>> <https://mail.osgi.org/mailman/listinfo/osgi-dev>
>> 
>> 
>> _______________________________________________
>> OSGi Developer Mail List
>> osgi-dev@mail.osgi.org <mailto:osgi-dev@mail.osgi.org>
>> https://mail.osgi.org/mailman/listinfo/osgi-dev 
>> <https://mail.osgi.org/mailman/listinfo/osgi-dev>
> 
> -- 
> Tim Ward
> 
> _______________________________________________
> OSGi Developer Mail List
> osgi-dev@mail.osgi.org <mailto:osgi-dev@mail.osgi.org>
> https://mail.osgi.org/mailman/listinfo/osgi-dev 
> <https://mail.osgi.org/mailman/listinfo/osgi-dev>
> 
> 
> 
> -- 
> Raymond Augé <http://www.liferay.com/web/raymond.auge/profile> (@rotty3000)
> Senior Software Architect Liferay, Inc. <http://www.liferay.com/> (@Liferay)
> Board Member & EEG Co-Chair, OSGi Alliance <http://osgi.org/> (@OSGiAlliance)
> _______________________________________________
> OSGi Developer Mail List
> osgi-dev@mail.osgi.org
> https://mail.osgi.org/mailman/listinfo/osgi-dev

_______________________________________________
OSGi Developer Mail List
osgi-dev@mail.osgi.org
https://mail.osgi.org/mailman/listinfo/osgi-dev

Reply via email to