| Why JDT does not see my plugins classes? [message #643073] |
Fri, 03 December 2010 22:16  |
Eclipse User |
|
|
|
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:
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
|
|
|
|
| Re: Why JDT does not see my plugins classes? [message #643418 is a reply to message #643102] |
Mon, 06 December 2010 19:07  |
| Eclipse User |
|
|
|
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
>
|
|
|
| Re: Why JDT does not see my plugins classes? [message #643419 is a reply to message #643102] |
Mon, 06 December 2010 19:08 |
| Eclipse User |
|
|
|
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
>
|
|
|
|
Powered by
FUDForum. Page generated in 0.03797 seconds
] 
Search
Help
Register
Login
Home
