[
https://issues.apache.org/jira/browse/FELIX-5685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16171336#comment-16171336
]
Carsten Ziegeler commented on FELIX-5685:
-----------------------------------------
[~fhoelting] I've created FELIX-5693 with a different proposal which is more
user friendly as it will not break most of the config admin users. But it
should give you the same result
> Splitting configadmin into configadmin and file persistance bundle
> ------------------------------------------------------------------
>
> Key: FELIX-5685
> URL: https://issues.apache.org/jira/browse/FELIX-5685
> Project: Felix
> Issue Type: Improvement
> Components: Configuration Admin
> Affects Versions: configadmin-1.8.16
> Reporter: Frank Hölting
> Labels: patch
> Attachments:
> Splitting-configadmin-into-configadmin-and-file-pers.patch
>
>
> It allows you to start alternative PersistenceManager without using
> Service Ranking and OSGi Start Level. The dependency definition of the
> declarative services is the only one that decides when which
> service/bundle is to be started.
> Unfortunately, the tests do not work before refactoring. Class not found
> exception by org. osgi.* Classes. This seems to be due to the maven pom
> configuration. And thus a fundamental test error of the bundle?
> Where can I find the CI system. At https://builds.apache.org/ you can find
> some felix subprojects. But not the Felix root project or even the
> configadmin subproject. It would be helpful to know how to run the tests if
> it doesn't work with mvn clean install.
> TODO:
> - Execute all tests
> - use code Formatter
> In the documentary SVN is documented as SCM. However, there is also a Felix
> github project. I have attached a git patch. I also like to create a pull
> request of the fork https://github.com/jcommand/felix/commits/trunk. Here are
> the two new commits.
> 716043a - The suggestion for improvement - patch and fork
> 1e7beab - same fixes of the build, see comment and code - only fork
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)