|
| Re: eclipse plugins - external jars & environment variables - build problem [message #484709 is a reply to message #484336] |
Tue, 08 September 2009 20:13  |
|
Hi Mikael,
I workaround would be to translate the jars into plug-in projects.
See here for an example on how to create a plugin from a jar:
http://www.vogella.de/articles/EclipseJarToPlugin/article.ht ml
Best regards, Lars
--
http://www.vogella.de/ - Eclipse plugin and Eclipse RCP Tutorials
http://www.twitter.com/vogella - vogella on Twitter
Mikael wrote:
> Hi,
>
> I am working on adding new views to my eclipse perspective.
>
> I would like to use external jars, using environment variable to find them.
>
> Now, that works runtime using the external keywork in the MANIFEST file;
> for example:
>
> Bundle-Classpath: external:$EXTLIBS$/jdom-1.1/build/jdom.jar,
> .
>
> but it doesn't work at build time, I tried to change the build
> page/build.properties file in the plugin.xml editor and that doesn't work.
> When I hit the "export deployable plugin" button, it crashes saying that
> the jdom classes import couldn't be resolved.
>
>
> So, the temporary workaround I have got is to export the plugin with
> Eclipse / File / Export and then manually change things such as the
> manifest file that end up empty.
>
>
> In short, how to use jars at "plug-in build time" that are not part of
> any eclipse project and can only be found using an environment variable?
>
> Thanks in advance.
>
> Mikael
>
|
|
|
Powered by
FUDForum. Page generated in 0.02729 seconds
] 
Search
Help
Register
Login
Home
