Home » Eclipse Projects » Eclipse Platform » Plug-in Export wizard fails - Unable to find plugin
| Plug-in Export wizard fails - Unable to find plugin [message #320688] |
Wed, 26 September 2007 19:01  |
Eclipse User |
|
|
|
I have a plugin I'm developting that runs ok under the debugger and now I'm
trying to export it for the first time. I click on the "Export Wizard" link
found on the Overview page of the plugin.xml editor. It brings up the
wizard with my plugin checked (org.ibm.rational.apex (0.0.0)), I give it an
archive file name with a path pointing to my $HOME directory
(/people/geb/foo.zip), and under Options I tell it not to include source
code, package plugin-s as individual JAR archives, and not to save the Ant
script (those are the defaults). I don't use JAR Sigining. Then I click on
Finish.
It pops up an error dialog that says:
Problems during export
Reason:
Unable to find plug-in: com.ibm.rational.apex_0.0.0. Please check the
error log for more details.
I've looked in the PDE "Error Log" view and I've looked in my workspaces
..metadata/.log file. Neither of them have anything. (I try the export many
times and each time I look, those two logging areas are unchanged.) So what
error log should I be looking at?
The only occurrance of the string "apex_0.0.0" I can find in my workspace is
in my plugin's build.properties file. That file insists that I have a
source.* line and it insists that the bin.* line reference the file
com.ibm.rational.apex_0.0.0.jar. I have no desire to create any sort of
"source" jar but it insists. Is this the root of the export wizard's
problem? If so, how do I go about creating this jar file and what is its
purpose? I would also like to know why I have to create it if anyone knows.
When I change the buiild.properties file to use the name apexxxx.jar instead
of apex_0.0.0.jar (and save the change) I notice two things, (a) the Build
page of the plugin.xml editor does not change and (b) when I try the export
the wizard is again looking for com.ibm.rational.apex_0.0.0. So apparently
the apex_0.0.0 in the build.properties file has nothing to do with the
error.
If I close the plugin.xml editor and reopen it then the Build page is
updated. At this point I've eliminated the _0.0.0 from the jar's name,
saved the plugin.xml and build.properties files, and closed and reopened the
plugin.xml editor. The Build page now says com.ibm.rational.apex.jar.
However an export operation still gets the same error saying it is looking
for a com.ibm.rational.apex_0.0.0 plugin. My build.properties file now
looks like this:
bin.includes = plugin.xml,\
plugin.properties,\
about.ini,\
about.properties,\
bin/,\
icons/,\
doc.xml,\
doc.zip,\
com.ibm.rational.apex.jar
source.com.ibm.rational.apex.jar = src/,\
icons/,\
internal/The only other occurance of
"0.0.0" in my plugin is in the plugin.xml <plugin> version="0.0.0" setting.
If I change that to be "3.0.0" instead and run the export I still get the
error about com.ibm.rational.apex_0.0.0 no being found. Where else could
that 0.0.0 be coming from? Any why is the export wizard looking for the
very plugin I'm trying to create?
Up until I tried to Export my plugin everything has been very automatic.
Now suddenly I can't find any signposts to tell me what to do next.
Gary
|
|
| |
| Re: Plug-in Export wizard fails - Unable to find plugin [message #320717 is a reply to message #320688] |
Thu, 27 September 2007 13:18  |
| Eclipse User |
|
|
|
Gary,
I would not expect this error to be about the contents of the bundle itself.
For the export, a feature would have been generated that includes
com.ibm.rational.apex version 0.0.0 (0.0.0 is a wild card, and matches any
version). The missing plugin message means that there was no _resolved_ bundle
with that name, commonly this means the bundle did not resolve for some reason,
as opposed to actually not being there at all.
So, look for reasons your bundle would have failed to resolve. Missing
dependency, RequiredExecutionEnvironment, etc.
-Andrew
Gary Barnes wrote:
> I have a plugin I'm developting that runs ok under the debugger and now I'm
> trying to export it for the first time. I click on the "Export Wizard" link
> found on the Overview page of the plugin.xml editor. It brings up the
> wizard with my plugin checked (org.ibm.rational.apex (0.0.0)), I give it an
> archive file name with a path pointing to my $HOME directory
> (/people/geb/foo.zip), and under Options I tell it not to include source
> code, package plugin-s as individual JAR archives, and not to save the Ant
> script (those are the defaults). I don't use JAR Sigining. Then I click on
> Finish.
>
> It pops up an error dialog that says:
>
> Problems during export
> Reason:
> Unable to find plug-in: com.ibm.rational.apex_0.0.0. Please check the
> error log for more details.
>
> I've looked in the PDE "Error Log" view and I've looked in my workspaces
> .metadata/.log file. Neither of them have anything. (I try the export many
> times and each time I look, those two logging areas are unchanged.) So what
> error log should I be looking at?
>
> The only occurrance of the string "apex_0.0.0" I can find in my workspace is
> in my plugin's build.properties file. That file insists that I have a
> source.* line and it insists that the bin.* line reference the file
> com.ibm.rational.apex_0.0.0.jar. I have no desire to create any sort of
> "source" jar but it insists. Is this the root of the export wizard's
> problem? If so, how do I go about creating this jar file and what is its
> purpose? I would also like to know why I have to create it if anyone knows.
>
> When I change the buiild.properties file to use the name apexxxx.jar instead
> of apex_0.0.0.jar (and save the change) I notice two things, (a) the Build
> page of the plugin.xml editor does not change and (b) when I try the export
> the wizard is again looking for com.ibm.rational.apex_0.0.0. So apparently
> the apex_0.0.0 in the build.properties file has nothing to do with the
> error.
>
> If I close the plugin.xml editor and reopen it then the Build page is
> updated. At this point I've eliminated the _0.0.0 from the jar's name,
> saved the plugin.xml and build.properties files, and closed and reopened the
> plugin.xml editor. The Build page now says com.ibm.rational.apex.jar.
> However an export operation still gets the same error saying it is looking
> for a com.ibm.rational.apex_0.0.0 plugin. My build.properties file now
> looks like this:
> bin.includes = plugin.xml,\
> plugin.properties,\
> about.ini,\
> about.properties,\
> bin/,\
> icons/,\
> doc.xml,\
> doc.zip,\
> com.ibm.rational.apex.jar
> source.com.ibm.rational.apex.jar = src/,\
> icons/,\
> internal/The only other occurance of
> "0.0.0" in my plugin is in the plugin.xml <plugin> version="0.0.0" setting.
> If I change that to be "3.0.0" instead and run the export I still get the
> error about com.ibm.rational.apex_0.0.0 no being found. Where else could
> that 0.0.0 be coming from? Any why is the export wizard looking for the
> very plugin I'm trying to create?
>
> Up until I tried to Export my plugin everything has been very automatic.
> Now suddenly I can't find any signposts to tell me what to do next.
>
> Gary
>
>
|
|
| |
| Re: Plug-in Export wizard fails - Unable to find plugin [message #320722 is a reply to message #320717] |
Thu, 27 September 2007 20:36 |
| Eclipse User |
|
|
|
Sorry, I don't think understand what you're saying here. My plugin is
com.ibm.rational.apex. I'm trying to export it and it is complaining, in
some sense, that it can't find itself. The only dependencies it has are on
org.eclipse.* packages. Is the export trying to locate
com.ibm.rational.apex_0.0.0 somewhere in the running Eclipse instance (the
one I'm use to develop the plugin, which naturally doesn't have my plugin
installed)?
Gary
"Andrew Niefer" <aniefer@ca.ibm.com> wrote in message
news:fdgojv$e5b$1@build.eclipse.org...
> Gary,
> I would not expect this error to be about the contents of the bundle
> itself.
>
> For the export, a feature would have been generated that includes
> com.ibm.rational.apex version 0.0.0 (0.0.0 is a wild card, and matches any
> version). The missing plugin message means that there was no _resolved_
> bundle with that name, commonly this means the bundle did not resolve for
> some reason, as opposed to actually not being there at all.
>
> So, look for reasons your bundle would have failed to resolve. Missing
> dependency, RequiredExecutionEnvironment, etc.
>
> -Andrew
>
> Gary Barnes wrote:
>> I have a plugin I'm developting that runs ok under the debugger and now
>> I'm trying to export it for the first time. I click on the "Export
>> Wizard" link found on the Overview page of the plugin.xml editor. It
>> brings up the wizard with my plugin checked (org.ibm.rational.apex
>> (0.0.0)), I give it an archive file name with a path pointing to my $HOME
>> directory (/people/geb/foo.zip), and under Options I tell it not to
>> include source code, package plugin-s as individual JAR archives, and not
>> to save the Ant script (those are the defaults). I don't use JAR
>> Sigining. Then I click on Finish.
>>
>> It pops up an error dialog that says:
>>
>> Problems during export
>> Reason:
>> Unable to find plug-in: com.ibm.rational.apex_0.0.0. Please check
>> the error log for more details.
>>
>> I've looked in the PDE "Error Log" view and I've looked in my workspaces
>> .metadata/.log file. Neither of them have anything. (I try the export
>> many times and each time I look, those two logging areas are unchanged.)
>> So what error log should I be looking at?
>>
>> The only occurrance of the string "apex_0.0.0" I can find in my workspace
>> is in my plugin's build.properties file. That file insists that I have a
>> source.* line and it insists that the bin.* line reference the file
>> com.ibm.rational.apex_0.0.0.jar. I have no desire to create any sort of
>> "source" jar but it insists. Is this the root of the export wizard's
>> problem? If so, how do I go about creating this jar file and what is its
>> purpose? I would also like to know why I have to create it if anyone
>> knows.
>>
>> When I change the buiild.properties file to use the name apexxxx.jar
>> instead of apex_0.0.0.jar (and save the change) I notice two things, (a)
>> the Build page of the plugin.xml editor does not change and (b) when I
>> try the export the wizard is again looking for
>> com.ibm.rational.apex_0.0.0. So apparently the apex_0.0.0 in the
>> build.properties file has nothing to do with the error.
>>
>> If I close the plugin.xml editor and reopen it then the Build page is
>> updated. At this point I've eliminated the _0.0.0 from the jar's name,
>> saved the plugin.xml and build.properties files, and closed and reopened
>> the plugin.xml editor. The Build page now says
>> com.ibm.rational.apex.jar. However an export operation still gets the
>> same error saying it is looking for a com.ibm.rational.apex_0.0.0 plugin.
>> My build.properties file now looks like this:
>> bin.includes = plugin.xml,\
>> plugin.properties,\
>> about.ini,\
>> about.properties,\
>> bin/,\
>> icons/,\
>> doc.xml,\
>> doc.zip,\
>> com.ibm.rational.apex.jar
>> source.com.ibm.rational.apex.jar = src/,\
>> icons/,\
>> internal/The only other occurance of
>> "0.0.0" in my plugin is in the plugin.xml <plugin> version="0.0.0"
>> setting. If I change that to be "3.0.0" instead and run the export I
>> still get the error about com.ibm.rational.apex_0.0.0 no being found.
>> Where else could that 0.0.0 be coming from? Any why is the export wizard
>> looking for the very plugin I'm trying to create?
>>
>> Up until I tried to Export my plugin everything has been very automatic.
>> Now suddenly I can't find any signposts to tell me what to do next.
>>
>> Gary
>>
|
|
|
| Re: Plug-in Export wizard fails - Unable to find plugin [message #320740 is a reply to message #320722] |
Fri, 28 September 2007 11:23 |
| Eclipse User |
|
|
|
The export find things in the workspace and in the target platform.
Since your plug-in is in the workspace this means that the problem is not that
the plug-in is not found at all.
This means something is wrong with the plug-in that is stopping it from
resolving. (The build is looking for resolved plug-ins: that is plug-ins which
have all their dependencies and requirements satisfied.) This generally means a
problem with the manifest.mf.
You mentioned in your other post that you didn't have a manifest.mf. PDE.UI
should have a way to convert your old plugin.xml into a new manifest.mf. Try
right click on the old plugin.xml and look under PDE Tools, I think there is a
convert to manifest or something there. (I don't have an old plugin to actually
check this).
-Andrew
Gary Barnes wrote:
> Sorry, I don't think understand what you're saying here. My plugin is
> com.ibm.rational.apex. I'm trying to export it and it is complaining, in
> some sense, that it can't find itself. The only dependencies it has are on
> org.eclipse.* packages. Is the export trying to locate
> com.ibm.rational.apex_0.0.0 somewhere in the running Eclipse instance (the
> one I'm use to develop the plugin, which naturally doesn't have my plugin
> installed)?
>
> Gary
>
> "Andrew Niefer" <aniefer@ca.ibm.com> wrote in message
> news:fdgojv$e5b$1@build.eclipse.org...
>> Gary,
>> I would not expect this error to be about the contents of the bundle
>> itself.
>>
>> For the export, a feature would have been generated that includes
>> com.ibm.rational.apex version 0.0.0 (0.0.0 is a wild card, and matches any
>> version). The missing plugin message means that there was no _resolved_
>> bundle with that name, commonly this means the bundle did not resolve for
>> some reason, as opposed to actually not being there at all.
>>
>> So, look for reasons your bundle would have failed to resolve. Missing
>> dependency, RequiredExecutionEnvironment, etc.
>>
>> -Andrew
>>
>> Gary Barnes wrote:
>>> I have a plugin I'm developting that runs ok under the debugger and now
>>> I'm trying to export it for the first time. I click on the "Export
>>> Wizard" link found on the Overview page of the plugin.xml editor. It
>>> brings up the wizard with my plugin checked (org.ibm.rational.apex
>>> (0.0.0)), I give it an archive file name with a path pointing to my $HOME
>>> directory (/people/geb/foo.zip), and under Options I tell it not to
>>> include source code, package plugin-s as individual JAR archives, and not
>>> to save the Ant script (those are the defaults). I don't use JAR
>>> Sigining. Then I click on Finish.
>>>
>>> It pops up an error dialog that says:
>>>
>>> Problems during export
>>> Reason:
>>> Unable to find plug-in: com.ibm.rational.apex_0.0.0. Please check
>>> the error log for more details.
>>>
>>> I've looked in the PDE "Error Log" view and I've looked in my workspaces
>>> .metadata/.log file. Neither of them have anything. (I try the export
>>> many times and each time I look, those two logging areas are unchanged.)
>>> So what error log should I be looking at?
>>>
>>> The only occurrance of the string "apex_0.0.0" I can find in my workspace
>>> is in my plugin's build.properties file. That file insists that I have a
>>> source.* line and it insists that the bin.* line reference the file
>>> com.ibm.rational.apex_0.0.0.jar. I have no desire to create any sort of
>>> "source" jar but it insists. Is this the root of the export wizard's
>>> problem? If so, how do I go about creating this jar file and what is its
>>> purpose? I would also like to know why I have to create it if anyone
>>> knows.
>>>
>>> When I change the buiild.properties file to use the name apexxxx.jar
>>> instead of apex_0.0.0.jar (and save the change) I notice two things, (a)
>>> the Build page of the plugin.xml editor does not change and (b) when I
>>> try the export the wizard is again looking for
>>> com.ibm.rational.apex_0.0.0. So apparently the apex_0.0.0 in the
>>> build.properties file has nothing to do with the error.
>>>
>>> If I close the plugin.xml editor and reopen it then the Build page is
>>> updated. At this point I've eliminated the _0.0.0 from the jar's name,
>>> saved the plugin.xml and build.properties files, and closed and reopened
>>> the plugin.xml editor. The Build page now says
>>> com.ibm.rational.apex.jar. However an export operation still gets the
>>> same error saying it is looking for a com.ibm.rational.apex_0.0.0 plugin.
>>> My build.properties file now looks like this:
>>> bin.includes = plugin.xml,\
>>> plugin.properties,\
>>> about.ini,\
>>> about.properties,\
>>> bin/,\
>>> icons/,\
>>> doc.xml,\
>>> doc.zip,\
>>> com.ibm.rational.apex.jar
>>> source.com.ibm.rational.apex.jar = src/,\
>>> icons/,\
>>> internal/The only other occurance of
>>> "0.0.0" in my plugin is in the plugin.xml <plugin> version="0.0.0"
>>> setting. If I change that to be "3.0.0" instead and run the export I
>>> still get the error about com.ibm.rational.apex_0.0.0 no being found.
>>> Where else could that 0.0.0 be coming from? Any why is the export wizard
>>> looking for the very plugin I'm trying to create?
>>>
>>> Up until I tried to Export my plugin everything has been very automatic.
>>> Now suddenly I can't find any signposts to tell me what to do next.
>>>
>>> Gary
>>>
>
|
|
| | |
| Re: Plug-in Export wizard fails - Unable to find plugin [message #320756 is a reply to message #320752] |
Fri, 28 September 2007 16:02 |
| Eclipse User |
|
|
|
I created a new plugin and copied over the manifest and changed my
plugin.xml and build.properties files in a like fashion. Then my plugin
stopped working, the activation stopped working. But then I discovered by
trial and error that the new MANIFEST.MF's attribute named
Bundle-SymbolicName is equivalent to the old plugin.xml's <plugin id="...">
setting. Once I changed the symbolic name to be exactly
com.ibm.rational.apex my plugin was able to locate its bundle again and the
plugin seems to work ok again.
So now I have a MANIFEST.MF and in its Require-Bundle attribute it names
literally every plugin that comes with a 3.2 Eclipse as downloaded from
eclipse.org. It names every last plugin. There isn't a single one missing
(other than the *.compatibility plugins which I have removed).
So now I try to do the export and the export fails and says that it has
created a logs.zip in my home directory. I go look at that file and the
@dot.bin.log file in there has lots of messages of the form below. All of
these things are from packages that are listed in the Require-Bundle and
they also show up on the Dependencies page of the editor. What am I doing
wrong? The plugin finds them when it runs but the Export doesn't find them.
Gary
# 9/28/07 12:47:27 PM PDT
# Eclipse Java Compiler 0.671, 3.2.0 release, Copyright IBM Corp 2000, 2006.
All rights reserved.
----------
1. ERROR in
/people/geb/workspace.linux/Apex/src/com/ibm/rational/apex/A pexPlugin.java
(at line 43)
import org.eclipse.core.commands.ExecutionEvent;
^^^^^^^^^^^^^^^^^^^^^^^^^
The import org.eclipse.core.commands cannot be resolved
----------
5. ERROR in
/people/geb/workspace.linux/Apex/src/com/ibm/rational/apex/A pexPlugin.java
(at line 47)
import org.eclipse.core.resources.IWorkspace;
^^^^^^^^^^^^^^^^^^^^^^^^^^
The import org.eclipse.core.resources cannot be resolved
----------
12. ERROR in
/people/geb/workspace.linux/Apex/src/com/ibm/rational/apex/A pexPlugin.java
(at line 54)
import org.eclipse.jface.dialogs.ErrorDialog;
^^^^^^^^^^^^^^^^^
The import org.eclipse.jface cannot be resolved
----------
13. ERROR in
/people/geb/workspace.linux/Apex/src/com/ibm/rational/apex/A pexPlugin.java
(at line 55)
import org.eclipse.jface.preference.IPreferenceStore;
^^^^^^^^^^^^^^^^^
The import org.eclipse.jface cannot be resolved
----------
14. ERROR in
/people/geb/workspace.linux/Apex/src/com/ibm/rational/apex/A pexPlugin.java
(at line 56)
import org.eclipse.jface.resource.ColorRegistry;
^^^^^^^^^^^^^^^^^
The import org.eclipse.jface cannot be resolved
----------
19. ERROR in
/people/geb/workspace.linux/Apex/src/com/ibm/rational/apex/A pexPlugin.java
(at line 61)
import org.eclipse.swt.SWT;
^^^^^^^^^^^^^^^^^^^
The import org.eclipse.swt.SWT cannot be resolved
----------
20. ERROR in
/people/geb/workspace.linux/Apex/src/com/ibm/rational/apex/A pexPlugin.java
(at line 62)
import org.eclipse.swt.graphics.Color;
^^^^^^^^^^^^^^^^^^^^^^^^
The import org.eclipse.swt.graphics cannot be resolved
----------
"Alex Blewitt" <automatic@javalobby.org> wrote in message
news:826388963.63631191001780588.JavaMail.root@cp9.dzone.com...
> You can right-click on a pugin.xml and select 'create OSGi manifest' or by
> using the link for the same in the plugin.xml editor.
>
> You can also change the vesion with <?plugin version=".."?> or some such -
> create a new empty plugin to see what it does.
>
> Alex.
|
|
|
Goto Forum:
Current Time: Sun Nov 09 18:36:18 EST 2025
Powered by FUDForum. Page generated in 0.04290 seconds |
Home