Eclipse Community Forums: Java Development Tools (JDT) » Packages not visible when plugin is deployed

Home » Language IDEs » Java Development Tools (JDT) » Packages not visible when plugin is deployed

Packages not visible when plugin is deployed [message #248456]

Sat, 06 October 2007 18:14

Eclipse User

Originally posted by: zinon.z.gmail.com

Hi all

This appears to be a recurring problem and despite hours of searching
have yet to get this to work.

I have a plugin in which I want one of the packages visible. I have
added it to the Export-Package: section of the manifest file and have
tried all the solutions I have managed to find on the web from other
people's efforts but still the package is not visible from a project
when deployed.

My manifest looks like:

Manifest-Version: 1.0
Bundle-ManifestVersion: 2
Bundle-Name: Project
Bundle-SymbolicName: org.project.Plugin;singleton:=true
Bundle-Version: 1.0.0.80
Bundle-Activator: org.project.plugin.Activator
Export-Package: org.project.plugin.annotationTypes;version="1.0.0.80"
Require-Bundle: org.eclipse.jdt.core,
org.eclipse.text,
org.eclipse.ui,
org.eclipse.core.runtime,
org.eclipse.core.resources,
org.eclipse.ui.ide
Eclipse-LazyStart: true
Bundle-ClassPath: owlapi-api.jar,
owlapi-apibinding.jar,
owlapi-debugging.jar,
owlapi-dig1_1.jar,
owlapi-functionalparser.jar,
owlapi-functionalrenderer.jar,
owlapi-impl.jar,
owlapi-krssparser.jar,
owlapi-oboparser.jar,
owlapi-owlxmlparser.jar,
owlapi-owlxmlrenderer.jar,
owlapi-rdfapi.jar,
owlapi-rdfxmlparser.jar,
owlapi-rdfxmlrenderer.jar,
owlapi-util.jar,
arq-extra.jar,
commons-logging-1.1.jar,
log4j-1.2.12.jar,
lucene-core-2.0.0.jar,
qname.jar,
axis.jar,
axis-ant.jar,
commons-discovery-0.2.jar,
jaxrpc.jar,
saaj.jar,
commons-validator-1.3.1.jar,
jakarta-oro-2.0.8.jar,
commons-lang-2.2.jar,
.

Any pointers/ideas on what it is I'm not doing right would be much
appreciated.

ZZ

Re: Packages not visible when plugin is deployed [message #248493 is a reply to message #248456]

Mon, 08 October 2007 15:57

Eclipse User

Originally posted by: wharley.bea.com

"ZZ" <zinon.z@gmail.com> wrote in message
news:fe919c$9o2$1@build.eclipse.org...
> Hi all
>
> This appears to be a recurring problem and despite hours of searching have
> yet to get this to work.
>
> I have a plugin in which I want one of the packages visible. I have added
> it to the Export-Package: section of the manifest file and have tried all
> the solutions I have managed to find on the web from other people's
> efforts but still the package is not visible from a project when deployed.
>
> My manifest looks like:
>
> Manifest-Version: 1.0
> Bundle-ManifestVersion: 2
> Bundle-Name: Project
> Bundle-SymbolicName: org.project.Plugin;singleton:=true
> Bundle-Version: 1.0.0.80
> Bundle-Activator: org.project.plugin.Activator
> Export-Package: org.project.plugin.annotationTypes;version="1.0.0.80"

When you say "visible", what exactly do you mean? How are you trying to use
them?

Also, whenever you're running into a "this works in a dev workspace but not
when deployed" problem, there are a few troubleshooting steps you should
always do: first, make sure to run Eclipse with the -clean command line
option, to ensure that your latest deployment is actually the code you're
executing; second, make sure that your bundle classpath actually contains
the code you're trying to export (including "." if you have any code in the
plug-in itself as opposed to just third-party jars).

Re: Packages not visible when plugin is deployed [message #248514 is a reply to message #248493]

Tue, 09 October 2007 12:36

Eclipse User

Originally posted by: zinon.z.gmail.com

Walter Harley wrote:
> "ZZ" <zinon.z@gmail.com> wrote in message
> news:fe919c$9o2$1@build.eclipse.org...
>> Hi all
>>
>> This appears to be a recurring problem and despite hours of searching have
>> yet to get this to work.
>>
>> I have a plugin in which I want one of the packages visible. I have added
>> it to the Export-Package: section of the manifest file and have tried all
>> the solutions I have managed to find on the web from other people's
>> efforts but still the package is not visible from a project when deployed.
>>
>> My manifest looks like:
>>
>> Manifest-Version: 1.0
>> Bundle-ManifestVersion: 2
>> Bundle-Name: Project
>> Bundle-SymbolicName: org.project.Plugin;singleton:=true
>> Bundle-Version: 1.0.0.80
>> Bundle-Activator: org.project.plugin.Activator
>> Export-Package: org.project.plugin.annotationTypes;version="1.0.0.80"
>
>
> When you say "visible", what exactly do you mean? How are you trying to use
> them?
>
> Also, whenever you're running into a "this works in a dev workspace but not
> when deployed" problem, there are a few troubleshooting steps you should
> always do: first, make sure to run Eclipse with the -clean command line
> option, to ensure that your latest deployment is actually the code you're
> executing; second, make sure that your bundle classpath actually contains
> the code you're trying to export (including "." if you have any code in the
> plug-in itself as opposed to just third-party jars).
>
>

Thanks for your reply Walter.

What I mean by 'visible' is that when the plugin is deployed in a clean
copy of Eclipse, and I create a new project, I cannot import any of the
packages in the plugin that I have explicitly added to the
Export-Package: section of the manifest file. (I get the message: The
import ... cannot be resolved).

I run Eclipse with the -clean command every time and "." is included in
the bundle classpath. Almost all the literature I have been able to find
on this merely mentions the Export-Package: section of the manifest file.

I'm at a loss...

Re: Packages not visible when plugin is deployed [message #248533 is a reply to message #248514]

Tue, 09 October 2007 15:42

Eclipse User

Originally posted by: wharley.bea.com

"ZZ" <zinon.z@gmail.com> wrote in message
news:fegaln$ahb$1@build.eclipse.org...
> Thanks for your reply Walter.
>
> What I mean by 'visible' is that when the plugin is deployed in a clean
> copy of Eclipse, and I create a new project, I cannot import any of the
> packages in the plugin that I have explicitly added to the Export-Package:
> section of the manifest file. (I get the message: The import ... cannot be
> resolved).
>
> I run Eclipse with the -clean command every time and "." is included in
> the bundle classpath. Almost all the literature I have been able to find
> on this merely mentions the Export-Package: section of the manifest file.

I assume the new project is itself a plug-in project, with your plug-in on
its dependency list?

If you open up the deployed plug-in jar, are your classes in there, in the
location you'd expect?

Are the classes in question contained within your source code or within a
third-party jar included in your plug-in? See
https://bugs.eclipse.org/bugs/show_bug.cgi?id=135012 for details on why
third-party jars can cause problems.

Re: Packages not visible when plugin is deployed [message #248571 is a reply to message #248533]

Wed, 10 October 2007 13:02

Eclipse User

Originally posted by: zinon.z.gmail.com

Walter Harley wrote:
> "ZZ" <zinon.z@gmail.com> wrote in message
> news:fegaln$ahb$1@build.eclipse.org...
>> Thanks for your reply Walter.
>>
>> What I mean by 'visible' is that when the plugin is deployed in a clean
>> copy of Eclipse, and I create a new project, I cannot import any of the
>> packages in the plugin that I have explicitly added to the Export-Package:
>> section of the manifest file. (I get the message: The import ... cannot be
>> resolved).
>>
>> I run Eclipse with the -clean command every time and "." is included in
>> the bundle classpath. Almost all the literature I have been able to find
>> on this merely mentions the Export-Package: section of the manifest file.
>
>
> I assume the new project is itself a plug-in project, with your plug-in on
> its dependency list?
>
> If you open up the deployed plug-in jar, are your classes in there, in the
> location you'd expect?
>
> Are the classes in question contained within your source code or within a
> third-party jar included in your plug-in? See
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=135012 for details on why
> third-party jars can cause problems.
>
>

I have no idea why/how this would happen, but when I downloaded a fresh
copy of eclipse the plug-in worked first time. Probably due to all my
poking around...

Many thanks however Walter for taking the time to reply.

Previous Topic:	Surrounding Closable objects with finally
Next Topic:	Reusing JDT's code

Goto Forum:

-=] Back to Top [=-

Current Time: Tue Jul 22 12:10:54 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter