| External jars - plugin [message #179679] |
Mon, 27 September 2004 21:08  |
Eclipse User |
|
|
|
Originally posted by: arthur.deltacore.com.br
Hello,
I'm making a class-generator plugin, and the classes generated by the
plugin depend on a external jar (DOM4J). I've included it in the build
output (the generated classes are in the org.foo package, and the jar is
at org/foo/lib). However, when the classes are generated, they simply
don´t recognize the dom4j import; I have to manually import the external
jar into the project build path. Is there a way to automatically do this
when the plugin generate the classes?
Regards,
Arthur Casals
|
|
|
|
| Re: External jars - plugin [message #179846 is a reply to message #179747] |
Tue, 28 September 2004 11:09  |
| Eclipse User |
|
|
|
Originally posted by: arthur.deltacore.com.br
Markus Keller wrote:
> Arthur Casals wrote:
>
>> Hello,
>>
>> I'm making a class-generator plugin, and the classes generated by the
>> plugin depend on a external jar (DOM4J). I've included it in the build
>> output (the generated classes are in the org.foo package, and the jar
>> is at org/foo/lib). However, when the classes are generated, they
>> simply don´t recognize the dom4j import; I have to manually import the
>> external jar into the project build path. Is there a way to
>> automatically do this when the plugin generate the classes?
>
>
> Use IJavaProject#getRawClasspath() and #setRawClasspath(..) to modify a
> project's classpath. You can create new classpath entries with
> JavaCore.newLibraryEntry(..).
>
> HTH
> Markus
Great, problem solved. Thanks a lot.
Arthur Casals
|
|
|
Powered by
FUDForum. Page generated in 0.06135 seconds
Home