[
https://issues.apache.org/jira/browse/FELIX-5568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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)
