[
https://issues.apache.org/jira/browse/FELIX-5568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15936247#comment-15936247
]
Guillaume Nodet commented on FELIX-5568:
----------------------------------------
Imho, I don't think the problem is about documentation, it's about making sure
the code can run on compact1 profile, which is what the change I suggested
above does. There are tools to check which profile a jar requires, but in this
case, it will report compact3 because of the JMX access. The pom change at
least ensures that all the remaining code is compact1 compliant and gives the
user some confidence.
> 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)
