Eclipse Community Forums - RDF feed
https://www.eclipse.org/forums/
Eclipse Community ForumsWhy JDT does not see my plugins classes?
https://www.eclipse.org/forums/index.php/mv/msg/201338/643073/#msg_643073
Originally posted by: agranov.allmail.net
We have three plugins - studio,support and parser
Studio requires both support and parser (they listed as required in
studio manifest)
If you import all 3 projects into the workspace – everything builds fine
Now export support project to support.jar plugin and/or parser project
to parser.jar plugin
Drop these plugins into eclipse/plugins and remove projects support and
parser from workspace
Studio project will not build now – java compiler does not see classes
from support.jar and/or parser.jar dropped into eclipse/plugins (though
the packages are exported!)
It does not complain – required plugins not found as they are found –
eclipse compiler simply does not see the classes…
But studio uses eclipse API and this API is provided by plugins located
in eclipse/plugins
Why classes only from our plugins are not visible by eclipse java compiler?
I have compared manifests from eclipse API plugins and e.g. our
manifests - the only difference is that in their manifests all classes
are signed:
Thank you very much,
Gennnady]]>2010-12-03T22:16:33-00:00Re: Why JDT does not see my plugins classes?
https://www.eclipse.org/forums/index.php/mv/msg/201338/643102/#msg_643102
> We have three plugins - studio,support and parser
>
> Studio requires both support and parser (they listed as required in
> studio manifest)
>
> If you import all 3 projects into the workspace – everything builds fine
>
> Now export support project to support.jar plugin and/or parser project
> to parser.jar plugin
>
> Drop these plugins into eclipse/plugins and remove projects support and
> parser from workspace
A P2 issue I think. Did you try dropping these plugins into
eclipse/dropins instead? Or did you try the 'Install into host' option
in the Plugin export wizard?
> Studio project will not build now – java compiler does not see classes
> from support.jar and/or parser.jar dropped into eclipse/plugins (though
> the packages are exported!)
>
> It does not complain – required plugins not found as they are found –
> eclipse compiler simply does not see the classes…
>
> But studio uses eclipse API and this API is provided by plugins located
> in eclipse/plugins
>
> Why classes only from our plugins are not visible by eclipse java compiler?
>
> I have compared manifests from eclipse API plugins and e.g. our
> manifests - the only difference is that in their manifests all classes
> are signed:
>
> Example:
>
> Name: org/eclipse/jem/internal/beaninfo/ui/BeaninfoEntrySearchpath Dial
> og$4.class
> SHA1-Digest: jZ6KY96EDYqBrWkVN3exQlyuC+0=
>
> That’s it? That’s the reason?
>
> Thank you very much,
> Gennnady]]>Deepak Azad2010-12-04T11:22:32-00:00Re: Why JDT does not see my plugins classes?
https://www.eclipse.org/forums/index.php/mv/msg/201338/643418/#msg_643418
Originally posted by: agranov.allmail.net
Hi, Deepak!
I tried both options suggested by you and unfortunately they did not
help eclipse java compiler to see classes from plugins.
Thanks for trying to help!
Gennady
On 12/4/2010 6:22 AM, Deepak Azad wrote:
> On 12/4/2010 3:46 AM, Gennady Agranov wrote:
>> We have three plugins - studio,support and parser
>>
>> Studio requires both support and parser (they listed as required in
>> studio manifest)
>>
>> If you import all 3 projects into the workspace – everything builds fine
>>
>> Now export support project to support.jar plugin and/or parser project
>> to parser.jar plugin
>>
>> Drop these plugins into eclipse/plugins and remove projects support and
>> parser from workspace
> A P2 issue I think. Did you try dropping these plugins into
> eclipse/dropins instead? Or did you try the 'Install into host' option
> in the Plugin export wizard?
>
>> Studio project will not build now – java compiler does not see classes
>> from support.jar and/or parser.jar dropped into eclipse/plugins (though
>> the packages are exported!)
>>
>> It does not complain – required plugins not found as they are found –
>> eclipse compiler simply does not see the classes…
>>
>> But studio uses eclipse API and this API is provided by plugins located
>> in eclipse/plugins
>>
>> Why classes only from our plugins are not visible by eclipse java
>> compiler?
>>
>> I have compared manifests from eclipse API plugins and e.g. our
>> manifests - the only difference is that in their manifests all classes
>> are signed:
>>
>> Example:
>>
>> Name: org/eclipse/jem/internal/beaninfo/ui/BeaninfoEntrySearchpath Dial
>> og$4.class
>> SHA1-Digest: jZ6KY96EDYqBrWkVN3exQlyuC+0=
>>
>> That’s it? That’s the reason?
>>
>> Thank you very much,
>> Gennnady
>]]>2010-12-06T19:07:57-00:00Re: Why JDT does not see my plugins classes?
https://www.eclipse.org/forums/index.php/mv/msg/201338/643419/#msg_643419
Originally posted by: agranov.allmail.net
Hi, Deepak!
I tried both options suggested by you and unfortunately they did not
help eclipse java compiler to see classes from plugins.
Thanks for trying to help!
Gennady
On 12/4/2010 6:22 AM, Deepak Azad wrote:
> On 12/4/2010 3:46 AM, Gennady Agranov wrote:
>> We have three plugins - studio,support and parser
>>
>> Studio requires both support and parser (they listed as required in
>> studio manifest)
>>
>> If you import all 3 projects into the workspace – everything builds fine
>>
>> Now export support project to support.jar plugin and/or parser project
>> to parser.jar plugin
>>
>> Drop these plugins into eclipse/plugins and remove projects support and
>> parser from workspace
> A P2 issue I think. Did you try dropping these plugins into
> eclipse/dropins instead? Or did you try the 'Install into host' option
> in the Plugin export wizard?
>
>> Studio project will not build now – java compiler does not see classes
>> from support.jar and/or parser.jar dropped into eclipse/plugins (though
>> the packages are exported!)
>>
>> It does not complain – required plugins not found as they are found –
>> eclipse compiler simply does not see the classes…
>>
>> But studio uses eclipse API and this API is provided by plugins located
>> in eclipse/plugins
>>
>> Why classes only from our plugins are not visible by eclipse java
>> compiler?
>>
>> I have compared manifests from eclipse API plugins and e.g. our
>> manifests - the only difference is that in their manifests all classes
>> are signed:
>>
>> Example:
>>
>> Name: org/eclipse/jem/internal/beaninfo/ui/BeaninfoEntrySearchpath Dial
>> og$4.class
>> SHA1-Digest: jZ6KY96EDYqBrWkVN3exQlyuC+0=
>>
>> That’s it? That’s the reason?
>>
>> Thank you very much,
>> Gennnady
>]]>2010-12-06T19:08:45-00:00Re: Why JDT does not see my plugins classes?
https://www.eclipse.org/forums/index.php/mv/msg/201338/643431/#msg_643431
eclipse/plugins directory.
If you don't need these 2 plugins in your running development
environment, just your build env, you can create a target platform using
Preferences>Plug-in Development>Target Platform. Base your target
platform on your install. Then deploy the 2 plugins that you care about
using File>Export...>Deployable Plug-ins and Fragments. Go back and
edit your target platform to include the 2 plugins.
Other options include deploying the 2 plugins *into* your running
eclipse (which would make the part of the default running platform).
This option can muddy your running eclipse, though.