[ 
https://issues.apache.org/jira/browse/FELIX-136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Koszegi updated FELIX-136:
---------------------------------

    Attachment: felix-launcher.zip

Here is the plug-in. Please read the dev-notes and readme files. Source is 
provided as Eclipse projects.
The plugin is tested under Eclipse 3.4.1 (It won't work with 3.5M5). 

Any comment and critiques are welcomed.

Regards,
Robert

> Add property to modify development-time bundle class path for Eclipse PDE
> -------------------------------------------------------------------------
>
>                 Key: FELIX-136
>                 URL: https://issues.apache.org/jira/browse/FELIX-136
>             Project: Felix
>          Issue Type: New Feature
>          Components: Framework
>            Reporter: Richard S. Hall
>            Assignee: Richard S. Hall
>            Priority: Minor
>         Attachments: felix-launcher.zip, osgi-frameworks.JPG, 
> run-configurations.JPG, target-platform.JPG
>
>
> Eclipse PDE uses "framework launchers" for lauching arbitrary OSGi 
> frameworks. Felix in combination with its "reference:" protocol is 
> successfully able to be launched by Eclipse PDE, but it is not ideal since it 
> requires that the project be structured with everything in the root 
> directory. Since projects are typically organized around bin/ and classes/ 
> directories, this is less than perfect.
> Equinox supports a special property to modify the bundle's class path at 
> development time to alleviate this situation. Such a property could also be 
> added to Felix to improve integration with Eclipse PDE.
> For example, DirectoryRevision could be modified to search for a 
> configuration property named ${bundle-symbolic-name}.classpath and could 
> prepend this value to the existing manifest header. To my understanding, this 
> is similar to the approach used by Equinox.
> If we implement this, then we should probably add another property to 
> enable/disable development-time features, so that people cannot use this 
> property unless the framework is being used in development mode.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to