[jira] [Closed] (FELIX-5642) string configurations in *.config files breaking behaviour change in 3.6.0
[
https://issues.apache.org/jira/browse/FELIX-5642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ferry Huberts closed FELIX-5642.
Resolution: Cannot Reproduce
> string configurations in *.config files breaking behaviour change in 3.6.0
> --
>
> Key: FELIX-5642
> URL: https://issues.apache.org/jira/browse/FELIX-5642
> Project: Felix
> Issue Type: Bug
> Components: File Install
>Affects Versions: fileinstall-3.6.0
>Reporter: Ferry Huberts
>Assignee: Guillaume Nodet
>Priority: Critical
>
> I have a X.config file with:
> {quote}
> networkInterface="wlp3s0"
> {quote}
> With fileinstall 3.5.8 this gets injected into my ds component's
> configuration as
> {quote}
> networkInterface=wlp3s0
> {quote}
> (so the quotes are removed)
> With fileinstall 3.6.0 this gets injected into my ds component's
> configuration as
> {quote}
> networkInterface="wlp3s0"
> {quote}
> (so the quotes are NOT removed)
> This is a BREAKING change.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (FELIX-5642) string configurations in *.config files breaking behaviour change in 3.6.0
[
https://issues.apache.org/jira/browse/FELIX-5642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16155357#comment-16155357
]
Ferry Huberts commented on FELIX-5642:
--
I can't reproduce it now, strange.
Closing
> string configurations in *.config files breaking behaviour change in 3.6.0
> --
>
> Key: FELIX-5642
> URL: https://issues.apache.org/jira/browse/FELIX-5642
> Project: Felix
> Issue Type: Bug
> Components: File Install
>Affects Versions: fileinstall-3.6.0
>Reporter: Ferry Huberts
>Assignee: Guillaume Nodet
>Priority: Critical
>
> I have a X.config file with:
> {quote}
> networkInterface="wlp3s0"
> {quote}
> With fileinstall 3.5.8 this gets injected into my ds component's
> configuration as
> {quote}
> networkInterface=wlp3s0
> {quote}
> (so the quotes are removed)
> With fileinstall 3.6.0 this gets injected into my ds component's
> configuration as
> {quote}
> networkInterface="wlp3s0"
> {quote}
> (so the quotes are NOT removed)
> This is a BREAKING change.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (FELIX-5642) string configurations in *.config files breaking behaviour change in 3.6.0
[
https://issues.apache.org/jira/browse/FELIX-5642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16131196#comment-16131196
]
Ferry Huberts commented on FELIX-5642:
--
See also #5306
> string configurations in *.config files breaking behaviour change in 3.6.0
> --
>
> Key: FELIX-5642
> URL: https://issues.apache.org/jira/browse/FELIX-5642
> Project: Felix
> Issue Type: Bug
> Components: File Install
>Affects Versions: fileinstall-3.6.0
>Reporter: Ferry Huberts
>Priority: Critical
>
> I have a X.config file with:
> {quote}
> networkInterface="wlp3s0"
> {quote}
> With fileinstall 3.5.8 this gets injected into my ds component's
> configuration as
> {quote}
> networkInterface=wlp3s0
> {quote}
> (so the quotes are removed)
> With fileinstall 3.6.0 this gets injected into my ds component's
> configuration as
> {quote}
> networkInterface="wlp3s0"
> {quote}
> (so the quotes are NOT removed)
> This is a BREAKING change.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (FELIX-5306) Fileinstall can't read floats and doubles in .config files
[
https://issues.apache.org/jira/browse/FELIX-5306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16131195#comment-16131195
]
Ferry Huberts commented on FELIX-5306:
--
See also #5642
> Fileinstall can't read floats and doubles in .config files
> ---
>
> Key: FELIX-5306
> URL: https://issues.apache.org/jira/browse/FELIX-5306
> Project: Felix
> Issue Type: Bug
> Components: File Install
>Reporter: munene kiruja
>
> The format for specifying a float in the .config format is =F" value> and similarly for doubles but with the type character D.
> When the floats and doubles are encountered in the config,
> java.lang.NumberFormatException is thrown with the message like:
> {code}
> java.lang.NumberFormatException: For input string: "400.333"
> at
> java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
> at java.lang.Integer.parseInt(Integer.java:580)
> at java.lang.Integer.parseInt(Integer.java:615)
> {code}
> The code is actually parsing using Integer and Long classes!!
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (FELIX-4741) Comments are not supported in *.config files
[ https://issues.apache.org/jira/browse/FELIX-4741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16109532#comment-16109532 ] Ferry Huberts commented on FELIX-4741: -- fixed by #5261 > Comments are not supported in *.config files > > > Key: FELIX-4741 > URL: https://issues.apache.org/jira/browse/FELIX-4741 > Project: Felix > Issue Type: Bug > Components: File Install >Affects Versions: fileinstall-3.4.0 > Environment: Linux 64 >Reporter: Ferry Huberts > > Comments ( '# .' ) are not supported in *.config files -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (FELIX-4741) Comments are not supported in *.config files
[ https://issues.apache.org/jira/browse/FELIX-4741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ferry Huberts closed FELIX-4741. Resolution: Duplicate > Comments are not supported in *.config files > > > Key: FELIX-4741 > URL: https://issues.apache.org/jira/browse/FELIX-4741 > Project: Felix > Issue Type: Bug > Components: File Install >Affects Versions: fileinstall-3.4.0 > Environment: Linux 64 >Reporter: Ferry Huberts > > Comments ( '# .' ) are not supported in *.config files -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (FELIX-5642) string configurations in *.config files breaking behaviour change in 3.6.0
[
https://issues.apache.org/jira/browse/FELIX-5642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16109530#comment-16109530
]
Ferry Huberts commented on FELIX-5642:
--
ping
critical issue
> string configurations in *.config files breaking behaviour change in 3.6.0
> --
>
> Key: FELIX-5642
> URL: https://issues.apache.org/jira/browse/FELIX-5642
> Project: Felix
> Issue Type: Bug
> Components: File Install
>Affects Versions: fileinstall-3.6.0
>Reporter: Ferry Huberts
>Priority: Critical
>
> I have a X.config file with:
> {quote}
> networkInterface="wlp3s0"
> {quote}
> With fileinstall 3.5.8 this gets injected into my ds component's
> configuration as
> {quote}
> networkInterface=wlp3s0
> {quote}
> (so the quotes are removed)
> With fileinstall 3.6.0 this gets injected into my ds component's
> configuration as
> {quote}
> networkInterface="wlp3s0"
> {quote}
> (so the quotes are NOT removed)
> This is a BREAKING change.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (FELIX-5642) string configurations in *.config files breaking behaviour change in 3.6.0
[
https://issues.apache.org/jira/browse/FELIX-5642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ferry Huberts updated FELIX-5642:
-
Ahem,
- to me - this is quite high priority since it _breaks_ functionality.
Can someone please take a look?
--
Ferry Huberts
> string configurations in *.config files breaking behaviour change in 3.6.0
> --
>
> Key: FELIX-5642
> URL: https://issues.apache.org/jira/browse/FELIX-5642
> Project: Felix
> Issue Type: Bug
> Components: File Install
>Affects Versions: fileinstall-3.6.0
>Reporter: Ferry Huberts
>Priority: Critical
>
> I have a X.config file with:
> {quote}
> networkInterface="wlp3s0"
> {quote}
> With fileinstall 3.5.8 this gets injected into my ds component's
> configuration as
> {quote}
> networkInterface=wlp3s0
> {quote}
> (so the quotes are removed)
> With fileinstall 3.6.0 this gets injected into my ds component's
> configuration as
> {quote}
> networkInterface="wlp3s0"
> {quote}
> (so the quotes are NOT removed)
> This is a BREAKING change.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (FELIX-5642) string configurations in *.config files breaking behaviour change in 3.6.0
[
https://issues.apache.org/jira/browse/FELIX-5642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16014342#comment-16014342
]
Ferry Huberts commented on FELIX-5642:
--
from a quick look, it seems that r1790563 broke this
> string configurations in *.config files breaking behaviour change in 3.6.0
> --
>
> Key: FELIX-5642
> URL: https://issues.apache.org/jira/browse/FELIX-5642
> Project: Felix
> Issue Type: Bug
> Components: File Install
>Affects Versions: fileinstall-3.6.0
>Reporter: Ferry Huberts
>Priority: Critical
>
> I have a X.config file with:
> {quote}
> networkInterface="wlp3s0"
> {quote}
> With fileinstall 3.5.8 this gets injected into my ds component's
> configuration as
> {quote}
> networkInterface=wlp3s0
> {quote}
> (so the quotes are removed)
> With fileinstall 3.6.0 this gets injected into my ds component's
> configuration as
> {quote}
> networkInterface="wlp3s0"
> {quote}
> (so the quotes are NOT removed)
> This is a BREAKING change.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (FELIX-5642) string configurations in *.config files breaking behaviour change in 3.6.0
[
https://issues.apache.org/jira/browse/FELIX-5642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16014334#comment-16014334
]
Ferry Huberts commented on FELIX-5642:
--
Also,
{quote}
bla=i"21"
{quote}
is no longer parsed.
it seems like the parser was replaced with something that has a totally
different behaviour.
IMHO that change must be reverted asap.
> string configurations in *.config files breaking behaviour change in 3.6.0
> --
>
> Key: FELIX-5642
> URL: https://issues.apache.org/jira/browse/FELIX-5642
> Project: Felix
> Issue Type: Bug
> Components: File Install
>Affects Versions: fileinstall-3.6.0
>Reporter: Ferry Huberts
>Priority: Critical
>
> I have a X.config file with:
> {quote}
> networkInterface="wlp3s0"
> {quote}
> With fileinstall 3.5.8 this gets injected into my ds component's
> configuration as
> {quote}
> networkInterface=wlp3s0
> {quote}
> (so the quotes are removed)
> With fileinstall 3.6.0 this gets injected into my ds component's
> configuration as
> {quote}
> networkInterface="wlp3s0"
> {quote}
> (so the quotes are NOT removed)
> This is a BREAKING change.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (FELIX-5642) string configurations in *.config files breaking behaviour change in 3.6.0
[
https://issues.apache.org/jira/browse/FELIX-5642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ferry Huberts updated FELIX-5642:
-
Description:
I have a X.config file with:
{quote}
networkInterface="wlp3s0"
{quote}
With fileinstall 3.5.8 this gets injected into my ds component's configuration
as
{quote}
networkInterface=wlp3s0
{quote}
(so the quotes are removed)
With fileinstall 3.6.0 this gets injected into my ds component's configuration
as
{quote}
networkInterface="wlp3s0"
{quote}
(so the quotes are NOT removed)
This is a BREAKING change.
was:
I have a X.config file with:
{quote}
networkInterface="wlp3s0"
{quote}
With fileinstall 3.5.8 this gets injected into my ds component's configuration
as
{quote}
networkInterface=wlp3s0
{quote}
(so the quotes are removed)
With fileinstall 3.6.1 this gets injected into my ds component's configuration
as
{quote}
networkInterface="wlp3s0"
{quote}
(so the quotes are NOT removed)
This is a BREAKING change.
I took 3.6.1 from maven central (maybe it was published by accident?)
Summary: string configurations in *.config files breaking behaviour
change in 3.6.0 (was: string configurations in *.config files breaking
behaviour change in 3.6.1)
> string configurations in *.config files breaking behaviour change in 3.6.0
> --
>
> Key: FELIX-5642
> URL: https://issues.apache.org/jira/browse/FELIX-5642
> Project: Felix
> Issue Type: Bug
> Components: File Install
>Affects Versions: fileinstall-3.6.0
>Reporter: Ferry Huberts
>Priority: Critical
>
> I have a X.config file with:
> {quote}
> networkInterface="wlp3s0"
> {quote}
> With fileinstall 3.5.8 this gets injected into my ds component's
> configuration as
> {quote}
> networkInterface=wlp3s0
> {quote}
> (so the quotes are removed)
> With fileinstall 3.6.0 this gets injected into my ds component's
> configuration as
> {quote}
> networkInterface="wlp3s0"
> {quote}
> (so the quotes are NOT removed)
> This is a BREAKING change.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (FELIX-5642) string configurations in *.config files breaking behaviour change in 3.6.1
Ferry Huberts created FELIX-5642:
Summary: string configurations in *.config files breaking
behaviour change in 3.6.1
Key: FELIX-5642
URL: https://issues.apache.org/jira/browse/FELIX-5642
Project: Felix
Issue Type: Bug
Components: File Install
Affects Versions: fileinstall-3.6.0
Reporter: Ferry Huberts
Priority: Critical
I have a X.config file with:
{quote}
networkInterface="wlp3s0"
{quote}
With fileinstall 3.5.8 this gets injected into my ds component's configuration
as
{quote}
networkInterface=wlp3s0
{quote}
(so the quotes are removed)
With fileinstall 3.6.1 this gets injected into my ds component's configuration
as
{quote}
networkInterface="wlp3s0"
{quote}
(so the quotes are NOT removed)
This is a BREAKING change.
I took 3.6.1 from maven central (maybe it was published by accident?)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (FELIX-5568) SCR contains compact3 profile code
[
https://issues.apache.org/jira/browse/FELIX-5568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15950984#comment-15950984
]
Ferry Huberts commented on FELIX-5568:
--
Ah yes, thanks for reminding me.
I did know that, but it didn't pop up when replying :-)
> SCR contains compact3 profile code
> --
>
> Key: FELIX-5568
> URL: https://issues.apache.org/jira/browse/FELIX-5568
> Project: Felix
> Issue Type: Bug
> Components: Declarative Services (SCR)
>Affects Versions: scr-2.0.8
> Environment: Fedora 25 x64
>Reporter: Ferry Huberts
>Assignee: Carsten Ziegeler
> Fix For: scr-2.1.0
>
>
> {quote}
> $ jdeps -P *.jar |grep compact3
> org.apache.felix.scr-2.0.8.jar ->
> /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.121-1.b14.fc25.x86_64/jre/lib/rt.jar
> (compact3)
> -> java.lang.management compact3
> {quote}
> Maybe split off the compact3 part as an optional extension/fragment?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (FELIX-5567) EventAdmin contains compact3 profile code
[
https://issues.apache.org/jira/browse/FELIX-5567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15950938#comment-15950938
]
Ferry Huberts commented on FELIX-5567:
--
ah yes, completely right. ignore my remark :-)
> EventAdmin contains compact3 profile code
> -
>
> Key: FELIX-5567
> URL: https://issues.apache.org/jira/browse/FELIX-5567
> Project: Felix
> Issue Type: Bug
> Components: Event Admin
>Affects Versions: eventadmin-1.4.8
> Environment: Fedora 25 x64
>Reporter: Ferry Huberts
>Assignee: Carsten Ziegeler
> Fix For: eventadmin-1.4.10
>
>
> {quote}
> $ jdeps -P *.jar |grep compact
> org.apache.felix.eventadmin-1.4.8.jar ->
> /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.121-1.b14.fc25.x86_64/jre/lib/rt.jar
> (compact3)
> -> java.iocompact1
> -> java.lang compact1
> -> java.security compact1
> -> java.util compact1
> -> java.lang compact1
> -> java.util compact1
> -> java.lang compact1
> -> java.security compact1
> -> java.util compact1
> -> java.util.concurrent compact1
> -> java.lang compact1
> -> java.security compact1
> -> java.lang compact1
> -> java.lang.management compact3
> -> java.util compact1
> -> java.util.concurrent compact1
> -> java.util.concurrent.atomiccompact1
> -> java.iocompact1
> -> java.lang compact1
> -> java.util compact1
> -> java.iocompact1
> -> java.lang compact1
> -> java.security compact1
> -> java.util compact1
> -> java.lang compact1
> -> java.lang.reflect compact1
> -> java.util compact1
> {quote}
> Maybe try to split of the compact3 part as an optional extension?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (FELIX-5568) SCR contains compact3 profile code
[
https://issues.apache.org/jira/browse/FELIX-5568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15950935#comment-15950935
]
Ferry Huberts commented on FELIX-5568:
--
Upon better inspection of the requirement it seems wrong.
It appears to exclude Java 1.7.
should probably be:
Require-Capability: osgi.ee; filter:="(| (&(osgi.ee=JavaSE)(version=1.6))
(&(osgi.ee=JavaSE)(version=1.7)) (&(osgi.ee=JavaSE/compact1)(version=1.8)) )"
But what to do with Java 1.9 (and up) ?
> SCR contains compact3 profile code
> --
>
> Key: FELIX-5568
> URL: https://issues.apache.org/jira/browse/FELIX-5568
> Project: Felix
> Issue Type: Bug
> Components: Declarative Services (SCR)
>Affects Versions: scr-2.0.8
> Environment: Fedora 25 x64
>Reporter: Ferry Huberts
>Assignee: Carsten Ziegeler
> Fix For: scr-2.1.0
>
>
> {quote}
> $ jdeps -P *.jar |grep compact3
> org.apache.felix.scr-2.0.8.jar ->
> /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.121-1.b14.fc25.x86_64/jre/lib/rt.jar
> (compact3)
> -> java.lang.management compact3
> {quote}
> Maybe split off the compact3 part as an optional extension/fragment?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (FELIX-5567) EventAdmin contains compact3 profile code
[
https://issues.apache.org/jira/browse/FELIX-5567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15950924#comment-15950924
]
Ferry Huberts commented on FELIX-5567:
--
Could you then also add the corresponding requirement to its manifest please,
like with SCR?
> EventAdmin contains compact3 profile code
> -
>
> Key: FELIX-5567
> URL: https://issues.apache.org/jira/browse/FELIX-5567
> Project: Felix
> Issue Type: Bug
> Components: Event Admin
>Affects Versions: eventadmin-1.4.8
> Environment: Fedora 25 x64
>Reporter: Ferry Huberts
>Assignee: Carsten Ziegeler
> Fix For: eventadmin-1.4.10
>
>
> {quote}
> $ jdeps -P *.jar |grep compact
> org.apache.felix.eventadmin-1.4.8.jar ->
> /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.121-1.b14.fc25.x86_64/jre/lib/rt.jar
> (compact3)
> -> java.iocompact1
> -> java.lang compact1
> -> java.security compact1
> -> java.util compact1
> -> java.lang compact1
> -> java.util compact1
> -> java.lang compact1
> -> java.security compact1
> -> java.util compact1
> -> java.util.concurrent compact1
> -> java.lang compact1
> -> java.security compact1
> -> java.lang compact1
> -> java.lang.management compact3
> -> java.util compact1
> -> java.util.concurrent compact1
> -> java.util.concurrent.atomiccompact1
> -> java.iocompact1
> -> java.lang compact1
> -> java.util compact1
> -> java.iocompact1
> -> java.lang compact1
> -> java.security compact1
> -> java.util compact1
> -> java.lang compact1
> -> java.lang.reflect compact1
> -> java.util compact1
> {quote}
> Maybe try to split of the compact3 part as an optional extension?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (FELIX-5568) SCR contains compact3 profile code
[
https://issues.apache.org/jira/browse/FELIX-5568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15945891#comment-15945891
]
Ferry Huberts commented on FELIX-5568:
--
BTW I have filed 'the same' issue on EventAdmin:
https://issues.apache.org/jira/browse/FELIX-5567
> SCR contains compact3 profile code
> --
>
> Key: FELIX-5568
> URL: https://issues.apache.org/jira/browse/FELIX-5568
> Project: Felix
> Issue Type: Bug
> Components: Declarative Services (SCR)
>Affects Versions: scr-2.0.8
> Environment: Fedora 25 x64
>Reporter: Ferry Huberts
>
> {quote}
> $ jdeps -P *.jar |grep compact3
> org.apache.felix.scr-2.0.8.jar ->
> /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.121-1.b14.fc25.x86_64/jre/lib/rt.jar
> (compact3)
> -> java.lang.management compact3
> {quote}
> Maybe split off the compact3 part as an optional extension/fragment?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (FELIX-5568) SCR contains compact3 profile code
[
https://issues.apache.org/jira/browse/FELIX-5568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15945889#comment-15945889
]
Ferry Huberts commented on FELIX-5568:
--
Even better!
Thanks Thomas
> SCR contains compact3 profile code
> --
>
> Key: FELIX-5568
> URL: https://issues.apache.org/jira/browse/FELIX-5568
> Project: Felix
> Issue Type: Bug
> Components: Declarative Services (SCR)
>Affects Versions: scr-2.0.8
> Environment: Fedora 25 x64
>Reporter: Ferry Huberts
>
> {quote}
> $ jdeps -P *.jar |grep compact3
> org.apache.felix.scr-2.0.8.jar ->
> /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.121-1.b14.fc25.x86_64/jre/lib/rt.jar
> (compact3)
> -> java.lang.management compact3
> {quote}
> Maybe split off the compact3 part as an optional extension/fragment?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (FELIX-5568) SCR contains compact3 profile code
[
https://issues.apache.org/jira/browse/FELIX-5568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15942811#comment-15942811
]
Ferry Huberts commented on FELIX-5568:
--
> Well, no one could come up with a clear good way of documenting this so far.
> Again, it's not unclear "what" to do but "how"!
Well, you could add a pseudo manifest header, something like:
Bundle-Profile-Compatibility: profile1
> As explained, splitting of the code does not make sense at all
Not to you, it does to me ;-)
> SCR contains compact3 profile code
> --
>
> Key: FELIX-5568
> URL: https://issues.apache.org/jira/browse/FELIX-5568
> Project: Felix
> Issue Type: Bug
> Components: Declarative Services (SCR)
>Affects Versions: scr-2.0.8
> Environment: Fedora 25 x64
>Reporter: Ferry Huberts
>
> {quote}
> $ jdeps -P *.jar |grep compact3
> org.apache.felix.scr-2.0.8.jar ->
> /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.121-1.b14.fc25.x86_64/jre/lib/rt.jar
> (compact3)
> -> java.lang.management compact3
> {quote}
> Maybe split off the compact3 part as an optional extension/fragment?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (FELIX-5568) SCR contains compact3 profile code
[
https://issues.apache.org/jira/browse/FELIX-5568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15942798#comment-15942798
]
Ferry Huberts commented on FELIX-5568:
--
What?
How can that be unclear?
The _very_ least is to document it that SCR is profile1 compatible since the
profile3 import is actually optional.
Better is to split off that code, but it appears that you're now willing to do
that.
> SCR contains compact3 profile code
> --
>
> Key: FELIX-5568
> URL: https://issues.apache.org/jira/browse/FELIX-5568
> Project: Felix
> Issue Type: Bug
> Components: Declarative Services (SCR)
>Affects Versions: scr-2.0.8
> Environment: Fedora 25 x64
>Reporter: Ferry Huberts
>
> {quote}
> $ jdeps -P *.jar |grep compact3
> org.apache.felix.scr-2.0.8.jar ->
> /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.121-1.b14.fc25.x86_64/jre/lib/rt.jar
> (compact3)
> -> java.lang.management compact3
> {quote}
> Maybe split off the compact3 part as an optional extension/fragment?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (FELIX-5568) SCR contains compact3 profile code
[
https://issues.apache.org/jira/browse/FELIX-5568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15935831#comment-15935831
]
Ferry Huberts commented on FELIX-5568:
--
The _actual_ problem is that scr uses profile3 packages but there is no way for
me - the end user - to know that this is optional.
I didn't know it is optional when I filed the issue. Now I know but it is not
clear at all, nor documented anywhere.
A simple jdeps tells me I can't use SCR on profile1 or profile2.
If it was made clear somewhere that SCR is explicitly compatible with profile1
then I would not have filed the issue :-)
Doesn't seem to me like a lot of complaining, just a lot of confusion
> SCR contains compact3 profile code
> --
>
> Key: FELIX-5568
> URL: https://issues.apache.org/jira/browse/FELIX-5568
> Project: Felix
> Issue Type: Bug
> Components: Declarative Services (SCR)
>Affects Versions: scr-2.0.8
> Environment: Fedora 25 x64
>Reporter: Ferry Huberts
>Assignee: Carsten Ziegeler
> Fix For: scr-2.1.0
>
>
> {quote}
> $ jdeps -P *.jar |grep compact3
> org.apache.felix.scr-2.0.8.jar ->
> /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.121-1.b14.fc25.x86_64/jre/lib/rt.jar
> (compact3)
> -> java.lang.management compact3
> {quote}
> Maybe split off the compact3 part as an optional extension/fragment?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (FELIX-5568) SCR contains compact3 profile code
[
https://issues.apache.org/jira/browse/FELIX-5568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15933086#comment-15933086
]
Ferry Huberts commented on FELIX-5568:
--
Like before:
> Maybe split off the compact3 part as an optional extension/fragment?
For our embedded product we would _very_ much like to run on profile1, which we
now could theoretically do but there is zero guarantee that it will work since
it uses profile3 classes.
I have no testcase to test it, also because I (obviously) don't know the
internals of SCR.
I can only see an import of profile3 classes and therefore _have_ to conclude
that it will not work on profile1 (or even profile2).
Splitting off that part so that SCR only imports profile1 classes ensures me it
will all work.
I am not interested in a thread dump so having it in SCR actually bothers me,
having it in an extension/fragment allows me to not deploy that part.
> SCR contains compact3 profile code
> --
>
> Key: FELIX-5568
> URL: https://issues.apache.org/jira/browse/FELIX-5568
> Project: Felix
> Issue Type: Bug
> Components: Declarative Services (SCR)
>Affects Versions: scr-2.0.8
> Environment: Fedora 25 x64
>Reporter: Ferry Huberts
>Assignee: Carsten Ziegeler
> Fix For: scr-2.1.0
>
>
> {quote}
> $ jdeps -P *.jar |grep compact3
> org.apache.felix.scr-2.0.8.jar ->
> /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.121-1.b14.fc25.x86_64/jre/lib/rt.jar
> (compact3)
> -> java.lang.management compact3
> {quote}
> Maybe split off the compact3 part as an optional extension/fragment?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (FELIX-5568) SCR contains compact3 profile code
[
https://issues.apache.org/jira/browse/FELIX-5568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15888446#comment-15888446
]
Ferry Huberts commented on FELIX-5568:
--
Well, we tried connecting with jconsole to our app and it blew up.
Might also be EventAdmin, might be SCR, we didn't actually look that deep into
it.
> SCR contains compact3 profile code
> --
>
> Key: FELIX-5568
> URL: https://issues.apache.org/jira/browse/FELIX-5568
> Project: Felix
> Issue Type: Bug
> Components: Declarative Services (SCR)
>Affects Versions: scr-2.0.8
> Environment: Fedora 25 x64
>Reporter: Ferry Huberts
>
> {quote}
> $ jdeps -P *.jar |grep compact3
> org.apache.felix.scr-2.0.8.jar ->
> /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.121-1.b14.fc25.x86_64/jre/lib/rt.jar
> (compact3)
> -> java.lang.management compact3
> {quote}
> Maybe split off the compact3 part as an optional extension/fragment?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (FELIX-5568) SCR contains compact3 profile code
[
https://issues.apache.org/jira/browse/FELIX-5568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15888444#comment-15888444
]
Ferry Huberts commented on FELIX-5568:
--
Quick-and-Dirty:
{quote}
final ThreadGroup currentGroup = Thread.currentThread().getThreadGroup();
final int noThreads = currentGroup.activeCount();
final Thread[] lstThreads = new Thread[noThreads];
currentGroup.enumerate(lstThreads);
for (int i = 0; i < noThreads; i++) {
System.out.println();
System.out.println("Thread No:" + i + " = " + lstThreads[i].getName());
final StackTraceElement[] st = lstThreads[i].getStackTrace();
for (final StackTraceElement element : st) {
System.out.println(" " + element);
}
}
{quote}
> SCR contains compact3 profile code
> --
>
> Key: FELIX-5568
> URL: https://issues.apache.org/jira/browse/FELIX-5568
> Project: Felix
> Issue Type: Bug
> Components: Declarative Services (SCR)
>Affects Versions: scr-2.0.8
> Environment: Fedora 25 x64
>Reporter: Ferry Huberts
>
> {quote}
> $ jdeps -P *.jar |grep compact3
> org.apache.felix.scr-2.0.8.jar ->
> /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.121-1.b14.fc25.x86_64/jre/lib/rt.jar
> (compact3)
> -> java.lang.management compact3
> {quote}
> Maybe split off the compact3 part as an optional extension/fragment?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (FELIX-5567) EventAdmin contains compact3 profile code
[
https://issues.apache.org/jira/browse/FELIX-5567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15888043#comment-15888043
]
Ferry Huberts commented on FELIX-5567:
--
It does run under compact1.
However, trying to connect with jconsole to it (obviously) crashes it since
jconsole uses JMX (compact3)
> EventAdmin contains compact3 profile code
> -
>
> Key: FELIX-5567
> URL: https://issues.apache.org/jira/browse/FELIX-5567
> Project: Felix
> Issue Type: Bug
> Components: Event Admin
>Affects Versions: eventadmin-1.4.8
> Environment: Fedora 25 x64
>Reporter: Ferry Huberts
>
> {quote}
> $ jdeps -P *.jar |grep compact
> org.apache.felix.eventadmin-1.4.8.jar ->
> /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.121-1.b14.fc25.x86_64/jre/lib/rt.jar
> (compact3)
> -> java.iocompact1
> -> java.lang compact1
> -> java.security compact1
> -> java.util compact1
> -> java.lang compact1
> -> java.util compact1
> -> java.lang compact1
> -> java.security compact1
> -> java.util compact1
> -> java.util.concurrent compact1
> -> java.lang compact1
> -> java.security compact1
> -> java.lang compact1
> -> java.lang.management compact3
> -> java.util compact1
> -> java.util.concurrent compact1
> -> java.util.concurrent.atomiccompact1
> -> java.iocompact1
> -> java.lang compact1
> -> java.util compact1
> -> java.iocompact1
> -> java.lang compact1
> -> java.security compact1
> -> java.util compact1
> -> java.lang compact1
> -> java.lang.reflect compact1
> -> java.util compact1
> {quote}
> Maybe try to split of the compact3 part as an optional extension?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (FELIX-5568) SCR contains compact3 profile code
[
https://issues.apache.org/jira/browse/FELIX-5568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15888042#comment-15888042
]
Ferry Huberts commented on FELIX-5568:
--
It does run under compact1.
However, trying to connect with jconsole to it (obviously) crashes it since
jconsole uses JMX (compact3)
> SCR contains compact3 profile code
> --
>
> Key: FELIX-5568
> URL: https://issues.apache.org/jira/browse/FELIX-5568
> Project: Felix
> Issue Type: Bug
> Components: Declarative Services (SCR)
>Affects Versions: scr-2.0.8
> Environment: Fedora 25 x64
>Reporter: Ferry Huberts
>
> {quote}
> $ jdeps -P *.jar |grep compact3
> org.apache.felix.scr-2.0.8.jar ->
> /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.121-1.b14.fc25.x86_64/jre/lib/rt.jar
> (compact3)
> -> java.lang.management compact3
> {quote}
> Maybe split off the compact3 part as an optional extension/fragment?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (FELIX-5567) EventAdmin contains compact3 profile code
[
https://issues.apache.org/jira/browse/FELIX-5567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ferry Huberts updated FELIX-5567:
-
Summary: EventAdmin contains compact3 profile code (was: EventAdmin does
not run under compact1 profile)
> EventAdmin contains compact3 profile code
> -
>
> Key: FELIX-5567
> URL: https://issues.apache.org/jira/browse/FELIX-5567
> Project: Felix
> Issue Type: Bug
> Components: Event Admin
>Affects Versions: eventadmin-1.4.8
> Environment: Fedora 25 x64
>Reporter: Ferry Huberts
>
> {quote}
> $ jdeps -P *.jar |grep compact
> org.apache.felix.eventadmin-1.4.8.jar ->
> /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.121-1.b14.fc25.x86_64/jre/lib/rt.jar
> (compact3)
> -> java.iocompact1
> -> java.lang compact1
> -> java.security compact1
> -> java.util compact1
> -> java.lang compact1
> -> java.util compact1
> -> java.lang compact1
> -> java.security compact1
> -> java.util compact1
> -> java.util.concurrent compact1
> -> java.lang compact1
> -> java.security compact1
> -> java.lang compact1
> -> java.lang.management compact3
> -> java.util compact1
> -> java.util.concurrent compact1
> -> java.util.concurrent.atomiccompact1
> -> java.iocompact1
> -> java.lang compact1
> -> java.util compact1
> -> java.iocompact1
> -> java.lang compact1
> -> java.security compact1
> -> java.util compact1
> -> java.lang compact1
> -> java.lang.reflect compact1
> -> java.util compact1
> {quote}
> Maybe try to split of the compact3 part as an optional extension?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (FELIX-5568) SCR contains compact3 profile code
[
https://issues.apache.org/jira/browse/FELIX-5568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ferry Huberts updated FELIX-5568:
-
Summary: SCR contains compact3 profile code (was: SCR contains compact3
profile)
> SCR contains compact3 profile code
> --
>
> Key: FELIX-5568
> URL: https://issues.apache.org/jira/browse/FELIX-5568
> Project: Felix
> Issue Type: Bug
> Components: Declarative Services (SCR)
>Affects Versions: scr-2.0.8
> Environment: Fedora 25 x64
>Reporter: Ferry Huberts
>
> {quote}
> $ jdeps -P *.jar |grep compact3
> org.apache.felix.scr-2.0.8.jar ->
> /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.121-1.b14.fc25.x86_64/jre/lib/rt.jar
> (compact3)
> -> java.lang.management compact3
> {quote}
> Maybe split off the compact3 part as an optional extension/fragment?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (FELIX-5568) SCR contains compact3 profile
[
https://issues.apache.org/jira/browse/FELIX-5568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ferry Huberts updated FELIX-5568:
-
Summary: SCR contains compact3 profile (was: SCR does not run under
compact1 profile)
> SCR contains compact3 profile
> -
>
> Key: FELIX-5568
> URL: https://issues.apache.org/jira/browse/FELIX-5568
> Project: Felix
> Issue Type: Bug
> Components: Declarative Services (SCR)
>Affects Versions: scr-2.0.8
> Environment: Fedora 25 x64
>Reporter: Ferry Huberts
>
> {quote}
> $ jdeps -P *.jar |grep compact3
> org.apache.felix.scr-2.0.8.jar ->
> /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.121-1.b14.fc25.x86_64/jre/lib/rt.jar
> (compact3)
> -> java.lang.management compact3
> {quote}
> Maybe split off the compact3 part as an optional extension/fragment?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (FELIX-5567) EventAdmin does not run under compact1 profile
[
https://issues.apache.org/jira/browse/FELIX-5567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15884157#comment-15884157
]
Ferry Huberts commented on FELIX-5567:
--
on master (git-svn-id: http://svn.apache.org/repos/asf/felix/trunk@1784269
13f79535-47bb-0310-9956-ffa450edef68):
{quote}
$ grep -nri import *|grep java.lang.management
impl/src/main/java/org/apache/felix/eventadmin/impl/tasks/HandlerTask.java:21:import
java.lang.management.ManagementFactory;
impl/src/main/java/org/apache/felix/eventadmin/impl/tasks/HandlerTask.java:22:import
java.lang.management.ThreadMXBean;
{quote}
> EventAdmin does not run under compact1 profile
> --
>
> Key: FELIX-5567
> URL: https://issues.apache.org/jira/browse/FELIX-5567
> Project: Felix
> Issue Type: Bug
> Components: Event Admin
>Affects Versions: eventadmin-1.4.8
> Environment: Fedora 25 x64
>Reporter: Ferry Huberts
>
> {quote}
> $ jdeps -P *.jar |grep compact
> org.apache.felix.eventadmin-1.4.8.jar ->
> /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.121-1.b14.fc25.x86_64/jre/lib/rt.jar
> (compact3)
> -> java.iocompact1
> -> java.lang compact1
> -> java.security compact1
> -> java.util compact1
> -> java.lang compact1
> -> java.util compact1
> -> java.lang compact1
> -> java.security compact1
> -> java.util compact1
> -> java.util.concurrent compact1
> -> java.lang compact1
> -> java.security compact1
> -> java.lang compact1
> -> java.lang.management compact3
> -> java.util compact1
> -> java.util.concurrent compact1
> -> java.util.concurrent.atomiccompact1
> -> java.iocompact1
> -> java.lang compact1
> -> java.util compact1
> -> java.iocompact1
> -> java.lang compact1
> -> java.security compact1
> -> java.util compact1
> -> java.lang compact1
> -> java.lang.reflect compact1
> -> java.util compact1
> {quote}
> Maybe try to split of the compact3 part as an optional extension?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (FELIX-5568) SCR does not run under compact1 profile
[
https://issues.apache.org/jira/browse/FELIX-5568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15884156#comment-15884156
]
Ferry Huberts commented on FELIX-5568:
--
on master (git-svn-id: http://svn.apache.org/repos/asf/felix/trunk@1784269
13f79535-47bb-0310-9956-ffa450edef68):
{quote}
$ grep -nri import *|grep java.lang.management
impl/manager/ThreadDump.java:21:import java.lang.management.ManagementFactory;
impl/manager/ThreadDump.java:22:import java.lang.management.ThreadInfo;
impl/manager/ThreadDump.java:23:import java.lang.management.ThreadMXBean;
{quote}
> SCR does not run under compact1 profile
> ---
>
> Key: FELIX-5568
> URL: https://issues.apache.org/jira/browse/FELIX-5568
> Project: Felix
> Issue Type: Bug
> Components: Declarative Services (SCR)
>Affects Versions: scr-2.0.8
> Environment: Fedora 25 x64
>Reporter: Ferry Huberts
>
> {quote}
> $ jdeps -P *.jar |grep compact3
> org.apache.felix.scr-2.0.8.jar ->
> /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.121-1.b14.fc25.x86_64/jre/lib/rt.jar
> (compact3)
> -> java.lang.management compact3
> {quote}
> Maybe split off the compact3 part as an optional extension/fragment?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (FELIX-5568) SCR does not run under compact1 profile
Ferry Huberts created FELIX-5568:
Summary: SCR does not run under compact1 profile
Key: FELIX-5568
URL: https://issues.apache.org/jira/browse/FELIX-5568
Project: Felix
Issue Type: Bug
Components: Declarative Services (SCR)
Affects Versions: scr-2.0.8
Environment: Fedora 25 x64
Reporter: Ferry Huberts
{quote}
$ jdeps -P *.jar |grep compact3
org.apache.felix.scr-2.0.8.jar ->
/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.121-1.b14.fc25.x86_64/jre/lib/rt.jar
(compact3)
-> java.lang.management compact3
{quote}
Maybe split off the compact3 part as an optional extension/fragment?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (FELIX-5567) EventAdmin does not run under compact1 profile
Ferry Huberts created FELIX-5567:
Summary: EventAdmin does not run under compact1 profile
Key: FELIX-5567
URL: https://issues.apache.org/jira/browse/FELIX-5567
Project: Felix
Issue Type: Bug
Components: Event Admin
Affects Versions: eventadmin-1.4.8
Environment: Fedora 25 x64
Reporter: Ferry Huberts
{quote}
$ jdeps -P *.jar |grep compact
org.apache.felix.eventadmin-1.4.8.jar ->
/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.121-1.b14.fc25.x86_64/jre/lib/rt.jar
(compact3)
-> java.iocompact1
-> java.lang compact1
-> java.security compact1
-> java.util compact1
-> java.lang compact1
-> java.util compact1
-> java.lang compact1
-> java.security compact1
-> java.util compact1
-> java.util.concurrent compact1
-> java.lang compact1
-> java.security compact1
-> java.lang compact1
-> java.lang.management compact3
-> java.util compact1
-> java.util.concurrent compact1
-> java.util.concurrent.atomiccompact1
-> java.iocompact1
-> java.lang compact1
-> java.util compact1
-> java.iocompact1
-> java.lang compact1
-> java.security compact1
-> java.util compact1
-> java.lang compact1
-> java.lang.reflect compact1
-> java.util compact1
{quote}
Maybe try to split of the compact3 part as an optional extension?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (FELIX-5261) FileInstall: allow comments in *.config files
[ https://issues.apache.org/jira/browse/FELIX-5261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15544990#comment-15544990 ] Ferry Huberts commented on FELIX-5261: -- Ok, investigated these changes: org.osgi.service.cm 1.3 --> 1.5 = OSGi 4.2 --> 5.0 org.osgi.util.tracker 1.4 --> 1.5 = OSGi 4.2 --> 4.3 Can you guys PLEASE PLEASE PLEASE do a release of FileInstall? > FileInstall: allow comments in *.config files > - > > Key: FELIX-5261 > URL: https://issues.apache.org/jira/browse/FELIX-5261 > Project: Felix > Issue Type: Improvement > Components: File Install >Affects Versions: fileinstall-3.5.4 > Environment: All >Reporter: Ferry Huberts >Assignee: Guillaume Nodet > Fix For: fileinstall-3.5.6 > > > Previous updates to ConfigAdmin forgot to update FileInstall. > FileInstall only uses a single class from ConfigAdmin, but upgrading that > dependency to the latest ConfigAdmin enables comments in *.config files. > This enables me to get rid of all the *.config.txt files in my project (that > are used to document for users what options are available) > I have already summitted a PR on GitHub: > https://github.com/apache/felix/pull/67 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (FELIX-4896) Jetty web server 'no cipher suites in common' bug
[
https://issues.apache.org/jira/browse/FELIX-4896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15505931#comment-15505931
]
Ferry Huberts commented on FELIX-4896:
--
Will have to check after my vacation.
What more information do you want?
The DEBUG log is already attached
> Jetty web server 'no cipher suites in common' bug
> -
>
> Key: FELIX-4896
> URL: https://issues.apache.org/jira/browse/FELIX-4896
> Project: Felix
> Issue Type: Bug
> Components: HTTP Service
>Affects Versions: http.jetty-3.0.2
> Environment: Fedora 21 x64
>Reporter: Ferry Huberts
> Attachments: jetty-ssl-cipher-suite-error
>
>
> I can no longer connect to the webconsole.
> I'm using
> {noformat}
> ./org.apache.felix.configadmin/org.apache.felix.configadmin-1.8.2.jar
> ./org.apache.felix.eventadmin/org.apache.felix.eventadmin-1.4.2.jar
> ./org.apache.felix.fileinstall/org.apache.felix.fileinstall-3.5.0.jar
> ./org.apache.felix.framework/org.apache.felix.framework-4.6.1.jar
> ./org.apache.felix.gogo.command/org.apache.felix.gogo.command-0.14.0.jar
> ./org.apache.felix.gogo.runtime/org.apache.felix.gogo.runtime-0.16.2.jar
> ./org.apache.felix.gogo.shell/org.apache.felix.gogo.shell-0.10.0.jar
> ./org.apache.felix.http.api/org.apache.felix.http.api-2.3.2.jar
> ./org.apache.felix.http.jetty/org.apache.felix.http.jetty-3.0.2.jar
> ./org.apache.felix.http.servlet-api/org.apache.felix.http.servlet-api-1.1.0.jar
> ./org.apache.felix.metatype/org.apache.felix.metatype-1.0.12.jar
> ./org.apache.felix.scr/org.apache.felix.scr-1.8.2.jar
> ./org.apache.felix.webconsole/org.apache.felix.webconsole-4.2.8.jar
> {noformat}
> I will attach the DEBUG log on connection establishment.
> The relevant error is:
> {noformat}
> javax.net.ssl.SSLHandshakeException: no cipher suites in common
> at sun.security.ssl.Handshaker.checkThrown(Handshaker.java:1431)
> at
> sun.security.ssl.SSLEngineImpl.checkTaskThrown(SSLEngineImpl.java:535)
> at sun.security.ssl.SSLEngineImpl.readNetRecord(SSLEngineImpl.java:813)
> at sun.security.ssl.SSLEngineImpl.unwrap(SSLEngineImpl.java:781)
> at javax.net.ssl.SSLEngine.unwrap(SSLEngine.java:624)
> at
> org.eclipse.jetty.io.ssl.SslConnection$DecryptedEndPoint.fill(SslConnection.java:516)
> at
> org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:239)
> at
> org.eclipse.jetty.io.AbstractConnection$2.run(AbstractConnection.java:540)
> at
> org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:635)
> at
> org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:555)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: javax.net.ssl.SSLHandshakeException: no cipher suites in common
> at sun.security.ssl.Alerts.getSSLException(Alerts.java:192)
> at sun.security.ssl.SSLEngineImpl.fatal(SSLEngineImpl.java:1666)
> at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:304)
> at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:292)
> at
> sun.security.ssl.ServerHandshaker.chooseCipherSuite(ServerHandshaker.java:1014)
> at
> sun.security.ssl.ServerHandshaker.clientHello(ServerHandshaker.java:731)
> at
> sun.security.ssl.ServerHandshaker.processMessage(ServerHandshaker.java:213)
> at sun.security.ssl.Handshaker.processLoop(Handshaker.java:979)
> at sun.security.ssl.Handshaker$1.run(Handshaker.java:919)
> at sun.security.ssl.Handshaker$1.run(Handshaker.java:916)
> at java.security.AccessController.doPrivileged(Native Method)
> at sun.security.ssl.Handshaker$DelegatedTask.run(Handshaker.java:1369)
> at
> org.eclipse.jetty.io.ssl.SslConnection$DecryptedEndPoint.fill(SslConnection.java:612)
> ... 5 common frames omitted
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (FELIX-5261) FileInstall: allow comments in *.config files
[
https://issues.apache.org/jira/browse/FELIX-5261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15420890#comment-15420890
]
Ferry Huberts commented on FELIX-5261:
--
I did see 2 changes in imported packages:
{code}
-
+
-
+
{code}
> FileInstall: allow comments in *.config files
> -
>
> Key: FELIX-5261
> URL: https://issues.apache.org/jira/browse/FELIX-5261
> Project: Felix
> Issue Type: Improvement
> Components: File Install
>Affects Versions: fileinstall-3.5.4
> Environment: All
>Reporter: Ferry Huberts
>Assignee: Guillaume Nodet
> Fix For: fileinstall-3.5.6
>
>
> Previous updates to ConfigAdmin forgot to update FileInstall.
> FileInstall only uses a single class from ConfigAdmin, but upgrading that
> dependency to the latest ConfigAdmin enables comments in *.config files.
> This enables me to get rid of all the *.config.txt files in my project (that
> are used to document for users what options are available)
> I have already summitted a PR on GitHub:
> https://github.com/apache/felix/pull/67
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (FELIX-5261) FileInstall: allow comments in *.config files
[ https://issues.apache.org/jira/browse/FELIX-5261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15420839#comment-15420839 ] Ferry Huberts commented on FELIX-5261: -- Can I please ask for a new release of FileInstall? I'd like to make use of this fixed issue, obviously :-) > FileInstall: allow comments in *.config files > - > > Key: FELIX-5261 > URL: https://issues.apache.org/jira/browse/FELIX-5261 > Project: Felix > Issue Type: Improvement > Components: File Install >Affects Versions: fileinstall-3.5.4 > Environment: All >Reporter: Ferry Huberts >Assignee: Guillaume Nodet > Fix For: fileinstall-3.5.6 > > > Previous updates to ConfigAdmin forgot to update FileInstall. > FileInstall only uses a single class from ConfigAdmin, but upgrading that > dependency to the latest ConfigAdmin enables comments in *.config files. > This enables me to get rid of all the *.config.txt files in my project (that > are used to document for users what options are available) > I have already summitted a PR on GitHub: > https://github.com/apache/felix/pull/67 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (FELIX-5197) non-fatal circularities in SCR should be info, not error, in log
[
https://issues.apache.org/jira/browse/FELIX-5197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15387524#comment-15387524
]
Ferry Huberts commented on FELIX-5197:
--
I've upgraded to SCR 2.0.4 and now I'm getting 2 ERROR stacktraces in my logs,
before it was just 1.
So it's become worse for me, for a perfectly valid use-case...
Can you please fix this, it is completely spamming my logs
> non-fatal circularities in SCR should be info, not error, in log
>
>
> Key: FELIX-5197
> URL: https://issues.apache.org/jira/browse/FELIX-5197
> Project: Felix
> Issue Type: Improvement
> Components: Framework
>Affects Versions: scr-2.0.2
>Reporter: Benson Margulies
>
> I have two components that have a pseudo-circular dependency.
> Component 'WorkerInterface' has a reference like:
> {code}
> @Reference(cardinality = ReferenceCardinality.MULTIPLE, policy =
> ReferencePolicy.DYNAMIC, policyOption = ReferencePolicyOption.GREEDY)
> public void setWorkerComponentService(WorkerComponentService
> workerComponentService) { ... }
> {code}
> one of the components that provides 'WorkerComponentService' has:
> {code}
> @Reference(cardinality = ReferenceCardinality.OPTIONAL, policy =
> ReferencePolicy.DYNAMIC, unbind = "unbindWorkerInterface")
> public void setWorkerInterface(WorkerInterface workerInterface) { .. }
> {code}
> This all works: The second activates, the first activates, and then
> the second gets called with the reference to the first. However, along
> the way, an alarming ERROR-level log message is delivered, as below.
> I submit that this should be no louder than INFO.
> {noformat}
> 2016-02-24 10:25:30,963 | ERROR | lixDispatchQueue |
> rosapi-worker-rni-rnt-sdk| 51 -
> com.basistech.ws.rosapi-worker-rni-rnt-sdk - 0.8.101.v20160224031931 |
> FrameworkEvent ERROR - com.basistech.ws.rosapi-worker-rni-rnt-sdk
> org.osgi.framework.ServiceException: ServiceFactory.getService()
> resulted in a cycle.
> at
> org.apache.felix.framework.ServiceRegistry.getService(ServiceRegistry.java:301)[org.apache.felix.framework-5.4.0.jar:]
> at
> org.apache.felix.framework.Felix.getService(Felix.java:3699)[org.apache.felix.framework-5.4.0.jar:]
> at
> org.apache.felix.framework.BundleContextImpl.getService(BundleContextImpl.java:470)[org.apache.felix.framework-5.4.0.jar:]
> at
> org.apache.felix.scr.impl.manager.SingleRefPair.getServiceObject(SingleRefPair.java:72)[129:org.apache.felix.scr:2.0.2]
> at
> org.apache.felix.scr.impl.helper.BindMethod.getServiceObject(BindMethod.java:646)[129:org.apache.felix.scr:2.0.2]
> at
> org.apache.felix.scr.impl.manager.DependencyManager.getServiceObject(DependencyManager.java:2137)[129:org.apache.felix.scr:2.0.2]
> at
> org.apache.felix.scr.impl.manager.DependencyManager$SingleDynamicCustomizer.prebind(DependencyManager.java:872)[129:org.apache.felix.scr:2.0.2]
> at
> org.apache.felix.scr.impl.manager.DependencyManager.prebind(DependencyManager.java:1457)[129:org.apache.felix.scr:2.0.2]
> at
> org.apache.felix.scr.impl.manager.AbstractComponentManager.collectDependencies(AbstractComponentManager.java:983)[129:org.apache.felix.scr:2.0.2]
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (FELIX-5261) FileInstall: allow comments in *.config files
[ https://issues.apache.org/jira/browse/FELIX-5261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15327299#comment-15327299 ] Ferry Huberts commented on FELIX-5261: -- Thank you! (a bit pushy, I know) Is there a release coming now? :-) > FileInstall: allow comments in *.config files > - > > Key: FELIX-5261 > URL: https://issues.apache.org/jira/browse/FELIX-5261 > Project: Felix > Issue Type: Improvement > Components: File Install >Affects Versions: fileinstall-3.5.4 > Environment: All >Reporter: Ferry Huberts >Assignee: Guillaume Nodet > Fix For: fileinstall-3.5.6 > > > Previous updates to ConfigAdmin forgot to update FileInstall. > FileInstall only uses a single class from ConfigAdmin, but upgrading that > dependency to the latest ConfigAdmin enables comments in *.config files. > This enables me to get rid of all the *.config.txt files in my project (that > are used to document for users what options are available) > I have already summitted a PR on GitHub: > https://github.com/apache/felix/pull/67 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (FELIX-5261) FileInstall: allow comments in *.config files
[ https://issues.apache.org/jira/browse/FELIX-5261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15327235#comment-15327235 ] Ferry Huberts commented on FELIX-5261: -- No response in 3 weeks. What can I do to get this merged? > FileInstall: allow comments in *.config files > - > > Key: FELIX-5261 > URL: https://issues.apache.org/jira/browse/FELIX-5261 > Project: Felix > Issue Type: Improvement > Components: File Install >Affects Versions: fileinstall-3.5.4 > Environment: All >Reporter: Ferry Huberts > Fix For: fileinstall-3.5.6 > > > Previous updates to ConfigAdmin forgot to update FileInstall. > FileInstall only uses a single class from ConfigAdmin, but upgrading that > dependency to the latest ConfigAdmin enables comments in *.config files. > This enables me to get rid of all the *.config.txt files in my project (that > are used to document for users what options are available) > I have already summitted a PR on GitHub: > https://github.com/apache/felix/pull/67 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (FELIX-5261) FileInstall: allow comments in *.config files
Ferry Huberts created FELIX-5261: Summary: FileInstall: allow comments in *.config files Key: FELIX-5261 URL: https://issues.apache.org/jira/browse/FELIX-5261 Project: Felix Issue Type: Improvement Components: File Install Affects Versions: fileinstall-3.5.4 Environment: All Reporter: Ferry Huberts Fix For: fileinstall-3.5.6 Previous updates to ConfigAdmin forgot to update FileInstall. FileInstall only uses a single class from ConfigAdmin, but upgrading that dependency to the latest ConfigAdmin enables comments in *.config files. This enables me to get rid of all the *.config.txt files in my project (that are used to document for users what options are available) I have already summitted a PR on GitHub: https://github.com/apache/felix/pull/67 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (FELIX-5197) non-fatal circularities in SCR should be info, not error, in log
[
https://issues.apache.org/jira/browse/FELIX-5197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15294840#comment-15294840
]
Ferry Huberts commented on FELIX-5197:
--
IMHO it _should_ be changed (for scenarios involving at least one optional
reference) because the log message is NOT TRUE _and_ it is polluting the log
> non-fatal circularities in SCR should be info, not error, in log
>
>
> Key: FELIX-5197
> URL: https://issues.apache.org/jira/browse/FELIX-5197
> Project: Felix
> Issue Type: Improvement
> Components: Framework
>Affects Versions: scr-2.0.2
>Reporter: Benson Margulies
>
> I have two components that have a pseudo-circular dependency.
> Component 'WorkerInterface' has a reference like:
> {code}
> @Reference(cardinality = ReferenceCardinality.MULTIPLE, policy =
> ReferencePolicy.DYNAMIC, policyOption = ReferencePolicyOption.GREEDY)
> public void setWorkerComponentService(WorkerComponentService
> workerComponentService) { ... }
> {code}
> one of the components that provides 'WorkerComponentService' has:
> {code}
> @Reference(cardinality = ReferenceCardinality.OPTIONAL, policy =
> ReferencePolicy.DYNAMIC, unbind = "unbindWorkerInterface")
> public void setWorkerInterface(WorkerInterface workerInterface) { .. }
> {code}
> This all works: The second activates, the first activates, and then
> the second gets called with the reference to the first. However, along
> the way, an alarming ERROR-level log message is delivered, as below.
> I submit that this should be no louder than INFO.
> {noformat}
> 2016-02-24 10:25:30,963 | ERROR | lixDispatchQueue |
> rosapi-worker-rni-rnt-sdk| 51 -
> com.basistech.ws.rosapi-worker-rni-rnt-sdk - 0.8.101.v20160224031931 |
> FrameworkEvent ERROR - com.basistech.ws.rosapi-worker-rni-rnt-sdk
> org.osgi.framework.ServiceException: ServiceFactory.getService()
> resulted in a cycle.
> at
> org.apache.felix.framework.ServiceRegistry.getService(ServiceRegistry.java:301)[org.apache.felix.framework-5.4.0.jar:]
> at
> org.apache.felix.framework.Felix.getService(Felix.java:3699)[org.apache.felix.framework-5.4.0.jar:]
> at
> org.apache.felix.framework.BundleContextImpl.getService(BundleContextImpl.java:470)[org.apache.felix.framework-5.4.0.jar:]
> at
> org.apache.felix.scr.impl.manager.SingleRefPair.getServiceObject(SingleRefPair.java:72)[129:org.apache.felix.scr:2.0.2]
> at
> org.apache.felix.scr.impl.helper.BindMethod.getServiceObject(BindMethod.java:646)[129:org.apache.felix.scr:2.0.2]
> at
> org.apache.felix.scr.impl.manager.DependencyManager.getServiceObject(DependencyManager.java:2137)[129:org.apache.felix.scr:2.0.2]
> at
> org.apache.felix.scr.impl.manager.DependencyManager$SingleDynamicCustomizer.prebind(DependencyManager.java:872)[129:org.apache.felix.scr:2.0.2]
> at
> org.apache.felix.scr.impl.manager.DependencyManager.prebind(DependencyManager.java:1457)[129:org.apache.felix.scr:2.0.2]
> at
> org.apache.felix.scr.impl.manager.AbstractComponentManager.collectDependencies(AbstractComponentManager.java:983)[129:org.apache.felix.scr:2.0.2]
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (FELIX-3811) http service should allow the interfaces bound to be configured
[ https://issues.apache.org/jira/browse/FELIX-3811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14660548#comment-14660548 ] Ferry Huberts commented on FELIX-3811: -- Java can't really bind to an interface, only to an address-port pair. In the presence of duplicates (which can really happen) this will fail, in the sense that you will not know to which interface the socket will be bound. I have run into this multiple times. If there is a true solution I'd be happy to hear it :-) http service should allow the interfaces bound to be configured --- Key: FELIX-3811 URL: https://issues.apache.org/jira/browse/FELIX-3811 Project: Felix Issue Type: Wish Components: Lightweight HTTP Service Reporter: Ed Schaller Assignee: Ken Gilmer Priority: Minor Labels: patch Attachments: httplite.bind.patch As I primarily use the lightweight http service to debug using the webconsole it would be nice to only bind it to the local interface to limit access to the webconsole. This could be done by providing a configuration paramater to specify the host address to bind to and could also be useful for those running lightweight http on multihomed hosts. I have created a patch against 0.1.5-SNAPSHOT that includes such functionality. It uses org.apache.felix.http.host as the configuration key but this could be changed. The semantics of what should be done when the host specified cannot be resolved (eg: InetAddress.getByName() fails) may also be worth changing. Presently it just binds to all interfaces if it is unable to resolve/parse the address. Failing closed would be better in my opinion but might not be the most intuitive. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (FELIX-4888) ServletHandler's are not sorted by longest matching path
[ https://issues.apache.org/jira/browse/FELIX-4888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14552532#comment-14552532 ] Ferry Huberts commented on FELIX-4888: -- See https://issues.apache.org/jira/browse/FELIX-4896 ServletHandler's are not sorted by longest matching path Key: FELIX-4888 URL: https://issues.apache.org/jira/browse/FELIX-4888 Project: Felix Issue Type: Sub-task Components: HTTP Service Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: http.base-3.0.0 If more than one servlet handler matches the request, the result is sorted by service ranking and not by longest matching path. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FELIX-4896) Jetty web server 'no cipher suites in common' bug
[
https://issues.apache.org/jira/browse/FELIX-4896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ferry Huberts updated FELIX-4896:
-
Attachment: jetty-ssl-cipher-suite-error
The connection establishment DEBUG log
Jetty web server 'no cipher suites in common' bug
-
Key: FELIX-4896
URL: https://issues.apache.org/jira/browse/FELIX-4896
Project: Felix
Issue Type: Bug
Components: HTTP Service
Affects Versions: http.jetty-3.0.2
Environment: Fedora 21 x64
Reporter: Ferry Huberts
Attachments: jetty-ssl-cipher-suite-error
I can no longer connect to the webconsole.
I'm using
{noformat}
./org.apache.felix.configadmin/org.apache.felix.configadmin-1.8.2.jar
./org.apache.felix.eventadmin/org.apache.felix.eventadmin-1.4.2.jar
./org.apache.felix.fileinstall/org.apache.felix.fileinstall-3.5.0.jar
./org.apache.felix.framework/org.apache.felix.framework-4.6.1.jar
./org.apache.felix.gogo.command/org.apache.felix.gogo.command-0.14.0.jar
./org.apache.felix.gogo.runtime/org.apache.felix.gogo.runtime-0.16.2.jar
./org.apache.felix.gogo.shell/org.apache.felix.gogo.shell-0.10.0.jar
./org.apache.felix.http.api/org.apache.felix.http.api-2.3.2.jar
./org.apache.felix.http.jetty/org.apache.felix.http.jetty-3.0.2.jar
./org.apache.felix.http.servlet-api/org.apache.felix.http.servlet-api-1.1.0.jar
./org.apache.felix.metatype/org.apache.felix.metatype-1.0.12.jar
./org.apache.felix.scr/org.apache.felix.scr-1.8.2.jar
./org.apache.felix.webconsole/org.apache.felix.webconsole-4.2.8.jar
{noformat}
I will attach the DEBUG log on connection establishment.
The relevant error is:
{noformat}
javax.net.ssl.SSLHandshakeException: no cipher suites in common
at sun.security.ssl.Handshaker.checkThrown(Handshaker.java:1431)
at
sun.security.ssl.SSLEngineImpl.checkTaskThrown(SSLEngineImpl.java:535)
at sun.security.ssl.SSLEngineImpl.readNetRecord(SSLEngineImpl.java:813)
at sun.security.ssl.SSLEngineImpl.unwrap(SSLEngineImpl.java:781)
at javax.net.ssl.SSLEngine.unwrap(SSLEngine.java:624)
at
org.eclipse.jetty.io.ssl.SslConnection$DecryptedEndPoint.fill(SslConnection.java:516)
at
org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:239)
at
org.eclipse.jetty.io.AbstractConnection$2.run(AbstractConnection.java:540)
at
org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:635)
at
org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:555)
at java.lang.Thread.run(Thread.java:745)
Caused by: javax.net.ssl.SSLHandshakeException: no cipher suites in common
at sun.security.ssl.Alerts.getSSLException(Alerts.java:192)
at sun.security.ssl.SSLEngineImpl.fatal(SSLEngineImpl.java:1666)
at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:304)
at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:292)
at
sun.security.ssl.ServerHandshaker.chooseCipherSuite(ServerHandshaker.java:1014)
at
sun.security.ssl.ServerHandshaker.clientHello(ServerHandshaker.java:731)
at
sun.security.ssl.ServerHandshaker.processMessage(ServerHandshaker.java:213)
at sun.security.ssl.Handshaker.processLoop(Handshaker.java:979)
at sun.security.ssl.Handshaker$1.run(Handshaker.java:919)
at sun.security.ssl.Handshaker$1.run(Handshaker.java:916)
at java.security.AccessController.doPrivileged(Native Method)
at sun.security.ssl.Handshaker$DelegatedTask.run(Handshaker.java:1369)
at
org.eclipse.jetty.io.ssl.SslConnection$DecryptedEndPoint.fill(SslConnection.java:612)
... 5 common frames omitted
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (FELIX-4888) ServletHandler's are not sorted by longest matching path
[ https://issues.apache.org/jira/browse/FELIX-4888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14552399#comment-14552399 ] Ferry Huberts commented on FELIX-4888: -- Hi Carsten, Is there an ETA on the release of this fix? It's biting me :-( ServletHandler's are not sorted by longest matching path Key: FELIX-4888 URL: https://issues.apache.org/jira/browse/FELIX-4888 Project: Felix Issue Type: Sub-task Components: HTTP Service Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: http.base-3.0.0 If more than one servlet handler matches the request, the result is sorted by service ranking and not by longest matching path. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (FELIX-4888) ServletHandler's are not sorted by longest matching path
[
https://issues.apache.org/jira/browse/FELIX-4888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14552452#comment-14552452
]
Ferry Huberts commented on FELIX-4888:
--
I have the same problem as David, I followed the thread
{noformat}
Hi all,
I was wondering whether anyone has got the webconsole with the latest
Felix HTTP implementation running yet?
webconsole 4.2.9-SNAPSHOT works perfectly fine with http api/jetty
2.3.2, but doesn't seem to work with 3.0.x-SNAPSHOT of these. It does
resolve, but it does not render properly. Is that simply a TODO or is
there something I need to do to enable this?
Thanks,
David
{noformat}
In the thread you say issue 4888 is for that bug.
I'm using
{noformat}
./org.apache.felix.configadmin/org.apache.felix.configadmin-1.8.2.jar
./org.apache.felix.eventadmin/org.apache.felix.eventadmin-1.4.2.jar
./org.apache.felix.fileinstall/org.apache.felix.fileinstall-3.5.0.jar
./org.apache.felix.framework/org.apache.felix.framework-4.6.1.jar
./org.apache.felix.gogo.command/org.apache.felix.gogo.command-0.14.0.jar
./org.apache.felix.gogo.runtime/org.apache.felix.gogo.runtime-0.16.2.jar
./org.apache.felix.gogo.shell/org.apache.felix.gogo.shell-0.10.0.jar
./org.apache.felix.http.api/org.apache.felix.http.api-2.3.2.jar
./org.apache.felix.http.jetty/org.apache.felix.http.jetty-3.0.2.jar
./org.apache.felix.http.servlet-api/org.apache.felix.http.servlet-api-1.1.0.jar
./org.apache.felix.metatype/org.apache.felix.metatype-1.0.12.jar
./org.apache.felix.scr/org.apache.felix.scr-1.8.2.jar
./org.apache.felix.webconsole/org.apache.felix.webconsole-4.2.8.jar
{noformat}
ServletHandler's are not sorted by longest matching path
Key: FELIX-4888
URL: https://issues.apache.org/jira/browse/FELIX-4888
Project: Felix
Issue Type: Sub-task
Components: HTTP Service
Reporter: Carsten Ziegeler
Assignee: Carsten Ziegeler
Fix For: http.base-3.0.0
If more than one servlet handler matches the request, the result is sorted by
service ranking and not by longest matching path.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (FELIX-4671) Provide an expression parser
[ https://issues.apache.org/jira/browse/FELIX-4671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14270205#comment-14270205 ] Ferry Huberts commented on FELIX-4671: -- Please reopen, see https://issues.apache.org/jira/browse/FELIX-4697 Provide an expression parser Key: FELIX-4671 URL: https://issues.apache.org/jira/browse/FELIX-4671 Project: Felix Issue Type: New Feature Components: Gogo Runtime Reporter: Guillaume Nodet Assignee: Guillaume Nodet Fix For: gogo.runtime-0.14.0 Gogo provides no way to do arithmetic operations or to provide boolean operators. This makes writing scripted loops or conditions extremely difficult. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (FELIX-4697) Error parsing the default gosh_profile.
[
https://issues.apache.org/jira/browse/FELIX-4697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14270178#comment-14270178
]
Ferry Huberts commented on FELIX-4697:
--
Just had it too. Have to revert back to 0.12.1
Error parsing the default gosh_profile.
---
Key: FELIX-4697
URL: https://issues.apache.org/jira/browse/FELIX-4697
Project: Felix
Issue Type: Bug
Components: Gogo Runtime
Affects Versions: gogo.runtime-0.14.0
Reporter: J.W. Janssen
It appears that the implementation of FELIX-4671 has caused an unexpected
side-effect in the parsing of the default {{gosh_profile}}. More
specifically: the Tokenizer now bails out on the following expression:
{code}
addcommand system (((${.context} bundles) 0) loadclass java.lang.System)
{code}
The reason for this is that the {{((}} makes the Tokenizer believe that it
should keep parsing until {{))}} is found, which isn't the case in the above
situation.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (FELIX-4742) Documentation on supported *.cfg and *.config files is missing
Ferry Huberts created FELIX-4742: Summary: Documentation on supported *.cfg and *.config files is missing Key: FELIX-4742 URL: https://issues.apache.org/jira/browse/FELIX-4742 Project: Felix Issue Type: Bug Components: File Install Affects Versions: fileinstall-3.4.0 Environment: Linux 64 Reporter: Ferry Huberts -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (FELIX-4741) Comments are not supported in *.config files
Ferry Huberts created FELIX-4741: Summary: Comments are not supported in *.config files Key: FELIX-4741 URL: https://issues.apache.org/jira/browse/FELIX-4741 Project: Felix Issue Type: Bug Components: File Install Affects Versions: fileinstall-3.4.0 Environment: Linux 64 Reporter: Ferry Huberts Comments ( '# .' ) are not supported in *.config files -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (FELIX-4743) Have to escape '=' characters in quoted values in *.config files
Ferry Huberts created FELIX-4743: Summary: Have to escape '=' characters in quoted values in *.config files Key: FELIX-4743 URL: https://issues.apache.org/jira/browse/FELIX-4743 Project: Felix Issue Type: Bug Components: File Install Affects Versions: fileinstall-3.4.0 Environment: Linux 64 Reporter: Ferry Huberts I have to escape '=' characters in quoted values in *.config files, the parser appears to be not-so-smart. Looking at the code, the parser can use some TLC -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FELIX-4742) Documentation on syntax of supported *.cfg and *.config files is missing
[ https://issues.apache.org/jira/browse/FELIX-4742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ferry Huberts updated FELIX-4742: - Summary: Documentation on syntax of supported *.cfg and *.config files is missing (was: Documentation on supported *.cfg and *.config files is missing) Documentation on syntax of supported *.cfg and *.config files is missing Key: FELIX-4742 URL: https://issues.apache.org/jira/browse/FELIX-4742 Project: Felix Issue Type: Bug Components: File Install Affects Versions: fileinstall-3.4.0 Environment: Linux 64 Reporter: Ferry Huberts -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FELIX-4568) webconsole doesn't recognise pipe '|' as list separator
[ https://issues.apache.org/jira/browse/FELIX-4568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ferry Huberts updated FELIX-4568: - Attachment: bug.webconsole.BugWebconsole.cfg bug.webconsole.jar minimal bundle and corresponding (fileinstall) config file the defaults work ok, uncomment the 2nd line in the config file and it doesn't work correctly webconsole 4.2.2.all webconsole doesn't recognise pipe '|' as list separator --- Key: FELIX-4568 URL: https://issues.apache.org/jira/browse/FELIX-4568 Project: Felix Issue Type: Bug Components: Web Console Affects Versions: webconsole-4.2.2 Environment: Linux x64 Reporter: Ferry Huberts Attachments: Screenshot of the example.png, bug.webconsole.BugWebconsole.cfg, bug.webconsole.jar with (bnd call) Config config = Configurable.createConfigurable(Config.class, props); I create a Config object. In Config is a ListString entries(); the default for this is 'a|b|c' bnd uses the pipe '|' character to split the Strings webconsole uses the comma ',' character to split which one is it doing the right thing? :-) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (FELIX-4568) webconsole doesn't recognise pipe '|' as list separator
[ https://issues.apache.org/jira/browse/FELIX-4568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14260150#comment-14260150 ] Ferry Huberts commented on FELIX-4568: -- Thanks,I'll try that once back at work. webconsole doesn't recognise pipe '|' as list separator --- Key: FELIX-4568 URL: https://issues.apache.org/jira/browse/FELIX-4568 Project: Felix Issue Type: Bug Components: Web Console Affects Versions: webconsole-4.2.2 Environment: Linux x64 Reporter: Ferry Huberts Attachments: Screenshot of the example.png, bug.webconsole.BugWebconsole.cfg, bug.webconsole.jar with (bnd call) Config config = Configurable.createConfigurable(Config.class, props); I create a Config object. In Config is a ListString entries(); the default for this is 'a|b|c' bnd uses the pipe '|' character to split the Strings webconsole uses the comma ',' character to split which one is it doing the right thing? :-) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (FELIX-4568) webconsole doesn't recognise pipe '|' as list separator
[
https://issues.apache.org/jira/browse/FELIX-4568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14069983#comment-14069983
]
Ferry Huberts commented on FELIX-4568:
--
ok.
the Config class:
{noformat}
package example;
import java.util.List;
import aQute.bnd.annotation.metatype.Meta;
@Meta.OCD(name = Example, description = Example)
public interface Config {
static final String DEFAULT_EXAMPLE = string1=a,b|string2=c,d|string3=e,f;
@Meta.AD(deflt = DEFAULT_EXAMPLE, required = false, description = The
example (default = + DEFAULT_EXAMPLE + ))
ListString examples();
}
{noformat}
I'll attach be corresponding screenshot.
webconsole 4.2.2 (all in one)
webconsole doesn't recognise pipe '|' as list separator
---
Key: FELIX-4568
URL: https://issues.apache.org/jira/browse/FELIX-4568
Project: Felix
Issue Type: Bug
Components: Web Console
Affects Versions: webconsole-4.2.2
Environment: Linux x64
Reporter: Ferry Huberts
with (bnd call)
Config config = Configurable.createConfigurable(Config.class, props);
I create a Config object.
In Config is a
ListString entries();
the default for this is 'a|b|c'
bnd uses the pipe '|' character to split the Strings
webconsole uses the comma ',' character to split
which one is it doing the right thing? :-)
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Updated] (FELIX-4568) webconsole doesn't recognise pipe '|' as list separator
[ https://issues.apache.org/jira/browse/FELIX-4568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ferry Huberts updated FELIX-4568: - Attachment: Screenshot of the example.png Screenshot of the example webconsole doesn't recognise pipe '|' as list separator --- Key: FELIX-4568 URL: https://issues.apache.org/jira/browse/FELIX-4568 Project: Felix Issue Type: Bug Components: Web Console Affects Versions: webconsole-4.2.2 Environment: Linux x64 Reporter: Ferry Huberts Attachments: Screenshot of the example.png with (bnd call) Config config = Configurable.createConfigurable(Config.class, props); I create a Config object. In Config is a ListString entries(); the default for this is 'a|b|c' bnd uses the pipe '|' character to split the Strings webconsole uses the comma ',' character to split which one is it doing the right thing? :-) -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (FELIX-4568) webconsole doesn't recognise pipe '|' as list separator
[
https://issues.apache.org/jira/browse/FELIX-4568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14070171#comment-14070171
]
Ferry Huberts commented on FELIX-4568:
--
Right, so bnd is at fault according to the spec then I guess.
Here's the metatype xml:
{noformat}
?xml version='1.0'?
metatype:MetaData xmlns:metatype=http://www.osgi.org/xmlns/metatype/v1.1.0;
localization=example.Config
OCD name=Example id=example.Service description=Example
AD name=Examples
id=examples
cardinality=-2147483648
required=false
default=string1=a,b|string2=c,d|string3=e,f
type=String
description=The example (default =
string1=a,b|string2=c,d|string3=e,f)/
/OCD
Designate pid=example.Service
Object ocdref=example.Service/
/Designate
/metatype:MetaData
{noformat}
So how _should_ it look then?
webconsole doesn't recognise pipe '|' as list separator
---
Key: FELIX-4568
URL: https://issues.apache.org/jira/browse/FELIX-4568
Project: Felix
Issue Type: Bug
Components: Web Console
Affects Versions: webconsole-4.2.2
Environment: Linux x64
Reporter: Ferry Huberts
Attachments: Screenshot of the example.png
with (bnd call)
Config config = Configurable.createConfigurable(Config.class, props);
I create a Config object.
In Config is a
ListString entries();
the default for this is 'a|b|c'
bnd uses the pipe '|' character to split the Strings
webconsole uses the comma ',' character to split
which one is it doing the right thing? :-)
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Closed] (FELIX-4568) webconsole doesn't recognise pipe '|' as list separator
[ https://issues.apache.org/jira/browse/FELIX-4568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ferry Huberts closed FELIX-4568. Resolution: Not a Problem Is a bnd issue webconsole doesn't recognise pipe '|' as list separator --- Key: FELIX-4568 URL: https://issues.apache.org/jira/browse/FELIX-4568 Project: Felix Issue Type: Bug Components: Web Console Affects Versions: webconsole-4.2.2 Environment: Linux x64 Reporter: Ferry Huberts Attachments: Screenshot of the example.png with (bnd call) Config config = Configurable.createConfigurable(Config.class, props); I create a Config object. In Config is a ListString entries(); the default for this is 'a|b|c' bnd uses the pipe '|' character to split the Strings webconsole uses the comma ',' character to split which one is it doing the right thing? :-) -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (FELIX-4568) webconsole doesn't recognise pipe '|' as list separator
[ https://issues.apache.org/jira/browse/FELIX-4568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14070186#comment-14070186 ] Ferry Huberts commented on FELIX-4568: -- Thanks Carsten! :-) webconsole doesn't recognise pipe '|' as list separator --- Key: FELIX-4568 URL: https://issues.apache.org/jira/browse/FELIX-4568 Project: Felix Issue Type: Bug Components: Web Console Affects Versions: webconsole-4.2.2 Environment: Linux x64 Reporter: Ferry Huberts Attachments: Screenshot of the example.png with (bnd call) Config config = Configurable.createConfigurable(Config.class, props); I create a Config object. In Config is a ListString entries(); the default for this is 'a|b|c' bnd uses the pipe '|' character to split the Strings webconsole uses the comma ',' character to split which one is it doing the right thing? :-) -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (FELIX-4568) webconsole doesn't recognise pipe '|' as list separator
Ferry Huberts created FELIX-4568: Summary: webconsole doesn't recognise pipe '|' as list separator Key: FELIX-4568 URL: https://issues.apache.org/jira/browse/FELIX-4568 Project: Felix Issue Type: Bug Components: Web Console Affects Versions: webconsole-4.2.2 Environment: Linux x64 Reporter: Ferry Huberts with (bnd call) Config config = Configurable.createConfigurable(Config.class, props); I create a Config object. In Config is a ListString entries(); the default for this is 'a|b|c' bnd uses the pipe '|' character to split the Strings webconsole uses the comma ',' character to split which one is it doing the right thing? :-) -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (FELIX-3601) Incorrect namespace in component XML for DS Annotations
[ https://issues.apache.org/jira/browse/FELIX-3601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13619517#comment-13619517 ] Ferry Huberts commented on FELIX-3601: -- [~mcculls] A heads-up: we're about to release bnd bndtools 2.1.0. Is it possible that you wait for that? Incorrect namespace in component XML for DS Annotations --- Key: FELIX-3601 URL: https://issues.apache.org/jira/browse/FELIX-3601 Project: Felix Issue Type: Bug Components: Maven Bundle Plugin Affects Versions: maven-bundle-plugin-2.3.7 Reporter: Marcel Schlegel Labels: maven Fix For: maven-bundle-plugin-2.4.0 BND issue reference https://github.com/bndtools/bnd/issues/136: When using DS annotations, bnd will generate component description XML with invalid namespace values. The version segment of the namespace value must start with 'v' as in http://www.osgi.org/xmlns/scr/v1.1.0 bnd is generating them without the 'v' as in http://www.osgi.org/xmlns/scr/1.1.0 The incorrect namespace causes DS to not recognize the generated component descriptions. Maven-Bundle-Plugin has references to the old bndlib 1.50.0(why is no newer version available at the maven central repository?), which include the above issue. Fixed in Bundle-Plugin 2.4.0-SNAPSHOT: https://repository.apache.org/content/repositories/snapshots/org/apache/felix/maven-bundle-plugin/2.4.0-SNAPSHOT/ -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (FELIX-3996) Upgrade to latest bnd version
[ https://issues.apache.org/jira/browse/FELIX-3996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13615306#comment-13615306 ] Ferry Huberts commented on FELIX-3996: -- We're about to release a new version of bnd and bndtools in the coming days. Maybe you can incorporate the new bnd version? (also for the bundle plugin) Ferry -- Ferry Huberts Upgrade to latest bnd version - Key: FELIX-3996 URL: https://issues.apache.org/jira/browse/FELIX-3996 Project: Felix Issue Type: Improvement Components: Dependency Manager Reporter: Paul Bakker Assignee: Pierre De Rop In the Dependency Mannager Annotations plugin for bnd a old version is used. This is a problem for usage in for example BndTools, where the latest bnd version is used. The most important change is that aQute.lib.osgi is renamed to aQute.bnd.service. Unfortunately there are also some real API changes. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
