[
https://issues.apache.org/jira/browse/ACE-101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13257514#comment-13257514
]
Marcel Offermans commented on ACE-101:
--------------------------------------
I think it covers this issue if you use the mechanism described above to
disable the discovery mechanism that is included in the launcher and either:
a) provide an activator that is part of the system bundle (by adding your
"bundle" to the system classpath when you start the launcher, or,
b) provide a discovery mechanism as a real bundle (but in this case, who
installs this bundle? You might have a bootstrap issue if you don't resolve
this).
> Allow the discovery service to be pluggable
> -------------------------------------------
>
> Key: ACE-101
> URL: https://issues.apache.org/jira/browse/ACE-101
> Project: ACE
> Issue Type: Sub-task
> Reporter: Angelo van der Sijpt
>
> The launcher has to be as self-contained as possible; yet, we want to be able
> to drop in a Discovery service, which will then take precedence over the
> system property.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
