[
https://issues.apache.org/jira/browse/FELIX-1462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12742032#action_12742032
]
Richard S. Hall edited comment on FELIX-1462 at 8/11/09 12:42 PM:
------------------------------------------------------------------
FYI: I pre-pended Equinox to the class path and the launcher correctly
instantiated it, so that works. However, Felix defaults to creating its cache
in the current directory while Equinox defaults to creating it where its JAR
resides, so this can be confusing. If you specify a cache location, then it
works the same.
was (Author: rickhall):
FYI: I pre-pended Equinox to the class path and the launcher correctly
instantiated it, so that works.
> Felix framework launcher should only use standard launching API
> ---------------------------------------------------------------
>
> Key: FELIX-1462
> URL: https://issues.apache.org/jira/browse/FELIX-1462
> Project: Felix
> Issue Type: Improvement
> Components: Main
> Affects Versions: felix-1.8.1
> Reporter: Richard S. Hall
> Assignee: Richard S. Hall
> Priority: Minor
> Fix For: felix-2.0.0
>
>
> Currently, the Felix framework launcher uses Felix-specific mechanisms to
> launch the framework. Specifically, it uses Felix' custom system bundle
> activator mechanism to handle processing of the auto properties for
> installing/starting bundles. We would need to restructure the launcher to do
> this processing externally, which would be fairly straightforward, then the
> launcher could be used with any R4.2 framework. Whether or not this is
> ultimately useful is debatable, but it would serve as a good example of how
> to create a generic launcher.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
