[
https://issues.apache.org/jira/browse/FELIX-5568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15933286#comment-15933286
]
David Jencks commented on FELIX-5568:
-------------------------------------
I've never worked with the profiles and don't have a setup where I can
plausibly experiment. The jmx class use is very confined and AFAICT (from code
inspection) if the classes are missing nothing bad happens. Is
java.util.concurrent.Callable a proflle1 class?
What actually happens when you run current felix SCR in your profile1
environment?
Since no one expects to run into a deadlock, and they are generally difficult
to reproduce, I don't think that requiring a fragment to be installed to get
the data needed to diagnose the problem is a good idea.
> 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)
