[
https://issues.apache.org/jira/browse/ACE-101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13256482#comment-13256482
]
J.W. Janssen commented on ACE-101:
----------------------------------
Given the latest sources, this would now be possible. You can disable the
default discovery service by adding
"-Dorg.apache.ace.discovery.property=disabled" to the MA startup, and plug in
your own discovery service by adding the MA-option
"bundle=my.own.discovery.Activator" (given that the custom discovery bundle is
added to the class path). For example:
[localhost:~/]$ java -cp
org.apache.ace.launcher-0.8.1-SNAPSHOT.jar:my.own.discovery-0.0.1.jar
-Dorg.apache.ace.discovery.property=disabled bundle=my.own.discovery.Activator
identification=MyTarget
Does this cover this issue? If so, can it be closed?
> 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
