|
|
|
|
Re: Extending the palette with custom widgets [Eclipse 3.2, VE 1.2] [message #135808 is a reply to message #135786] |
Tue, 13 February 2007 14:24 |
Eclipse User |
|
|
|
Originally posted by: richkulp.us.NO_SPAM.ibm.com
If you open the schema document on the registrations extension point
you'll see the following comment on the runtime attribute:
the path to the jar relative to the plugin. This jar will be added to
the classpath. If relative to another plugin, then use the format
"/otherpluginid/myjar.jar".
--
Thanks,
Rich Kulp
|
|
|
|
Re: Extending the palette with custom widgets [Eclipse 3.2, VE 1.2] [message #135834 is a reply to message #135820] |
Tue, 13 February 2007 16:34 |
Eclipse User |
|
|
|
Originally posted by: richkulp.us.NO_SPAM.ibm.com
There is a problem in that during development time the runtime jar (in
your case widgets.jar) must be a true jar sitting in the
my.widgets.framework/lib directory in the project. You'll need to build
it and place it in the right place in your framework project, and if you
are using CVS I would put a .cvsignore file in that folder telling it to
ignore that jar and not put it out to cvs.
This is an annoying problem but it is a JDT problem that they won't fix
(they call it an enhancement that they won't do. :-)) But basically they
won't allow an external class folder to be in the classpath. Since the
widgets.jar during development time is not a jar but just classes within
a class bin folder, this folder cannot be added to the container in your
target workspace.
--
Thanks,
Rich Kulp
|
|
|
|
Re: Extending the palette with custom widgets [Eclipse 3.2, VE 1.2] [message #135860 is a reply to message #135847] |
Tue, 13 February 2007 19:11 |
Eclipse User |
|
|
|
Originally posted by: richkulp.us.NO_SPAM.ibm.com
No, it should not be in the plugin's classpath since you are not
executing that code in Eclipse.
Sébastien Alonzo wrote:
> Well in my case the jar is already built in my.widgets.framework/lib
> directory. But it's not in the classpath of my.widgets.framework plugin
> so maybe that's what is bothering the JDT.
>
> I'm going to try and add it to my plugin classpath to see if it works.
>
> Rich Kulp wrote:
>> There is a problem in that during development time the runtime jar (in
>> your case widgets.jar) must be a true jar sitting in the
>> my.widgets.framework/lib directory in the project. You'll need to
>> build it and place it in the right place in your framework project,
>> and if you are using CVS I would put a .cvsignore file in that folder
>> telling it to ignore that jar and not put it out to cvs.
>>
>> This is an annoying problem but it is a JDT problem that they won't
>> fix (they call it an enhancement that they won't do. :-)) But
>> basically they won't allow an external class folder to be in the
>> classpath. Since the widgets.jar during development time is not a jar
>> but just classes within a class bin folder, this folder cannot be
>> added to the container in your target workspace.
>>
>>
--
Thanks,
Rich Kulp
|
|
|
|
|
|
Re: Extending the palette with custom widgets [Eclipse 3.2, VE 1.2] [message #615065 is a reply to message #135786] |
Tue, 13 February 2007 14:24 |
Eclipse User |
|
|
|
Originally posted by: richkulp.us.NO_SPAM.ibm.com
If you open the schema document on the registrations extension point
you'll see the following comment on the runtime attribute:
the path to the jar relative to the plugin. This jar will be added to
the classpath. If relative to another plugin, then use the format
"/otherpluginid/myjar.jar".
--
Thanks,
Rich Kulp
|
|
|
|
Re: Extending the palette with custom widgets [Eclipse 3.2, VE 1.2] [message #615067 is a reply to message #135820] |
Tue, 13 February 2007 16:34 |
Eclipse User |
|
|
|
Originally posted by: richkulp.us.NO_SPAM.ibm.com
There is a problem in that during development time the runtime jar (in
your case widgets.jar) must be a true jar sitting in the
my.widgets.framework/lib directory in the project. You'll need to build
it and place it in the right place in your framework project, and if you
are using CVS I would put a .cvsignore file in that folder telling it to
ignore that jar and not put it out to cvs.
This is an annoying problem but it is a JDT problem that they won't fix
(they call it an enhancement that they won't do. :-)) But basically they
won't allow an external class folder to be in the classpath. Since the
widgets.jar during development time is not a jar but just classes within
a class bin folder, this folder cannot be added to the container in your
target workspace.
--
Thanks,
Rich Kulp
|
|
|
|
Re: Extending the palette with custom widgets [Eclipse 3.2, VE 1.2] [message #615069 is a reply to message #135847] |
Tue, 13 February 2007 19:11 |
Eclipse User |
|
|
|
Originally posted by: richkulp.us.NO_SPAM.ibm.com
No, it should not be in the plugin's classpath since you are not
executing that code in Eclipse.
Sébastien Alonzo wrote:
> Well in my case the jar is already built in my.widgets.framework/lib
> directory. But it's not in the classpath of my.widgets.framework plugin
> so maybe that's what is bothering the JDT.
>
> I'm going to try and add it to my plugin classpath to see if it works.
>
> Rich Kulp wrote:
>> There is a problem in that during development time the runtime jar (in
>> your case widgets.jar) must be a true jar sitting in the
>> my.widgets.framework/lib directory in the project. You'll need to
>> build it and place it in the right place in your framework project,
>> and if you are using CVS I would put a .cvsignore file in that folder
>> telling it to ignore that jar and not put it out to cvs.
>>
>> This is an annoying problem but it is a JDT problem that they won't
>> fix (they call it an enhancement that they won't do. :-)) But
>> basically they won't allow an external class folder to be in the
>> classpath. Since the widgets.jar during development time is not a jar
>> but just classes within a class bin folder, this folder cannot be
>> added to the container in your target workspace.
>>
>>
--
Thanks,
Rich Kulp
|
|
|
Powered by
FUDForum. Page generated in 0.04672 seconds