Home » Eclipse Projects » Plugin Development Environment (PDE) » Eclipse stopped treating plug-in project as a plug-in project - again!
| Eclipse stopped treating plug-in project as a plug-in project - again! [message #479674] |
Tue, 11 August 2009 18:46  |
Eclipse User |
|
|
|
I posted this comment last month. Since then, I have encountered the
problem again.
I have an OSGi plug-in that I am using in Eclipse and testing in the
built-in equinox OSGi container. I'm using a bunch of other bundles with
it. At some point after closing an instance of the server, Eclipse just
decides that this isn't a bundle anymore. Other bundles that are
dependent on the exported packages say that these packages are no longer
available. The package no longer shows up in the run configuration
check-box list.
The PDE menu does not, however, give me the option of converting the
project to a plug-in project. It realizes the project already IS a
plug-in. It's the rest of the PDE that disagrees. I 've checked all of
the plugin, classpath files, etc. Is there some kind of external file,
perhaps the run-configuration file, that would contain config data
determining whether or not this project gets treated like a plug in?
It's frustrating - the only way I could fix the problem last time was make
a new plug in project under a different name and copy everything to it.
Note, this is an entirely different plug-in from the one I had problems
with in the past.
Thanks,
Mike
http://dev.eclipse.org/newslists/news.eclipse.platform.pde/m sg01980.html
|
|
|
| Re: Eclipse stopped treating plug-in project as a plug-in project - again! [message #479678 is a reply to message #479674] |
Tue, 11 August 2009 19:31  |
| Eclipse User |
|
|
|
Michael Sullivan wrote:
> I posted this comment last month. Since then, I have encountered the
> problem again.
>
> I have an OSGi plug-in that I am using in Eclipse and testing in the
> built-in equinox OSGi container. I'm using a bunch of other bundles
> with it. At some point after closing an instance of the server, Eclipse
> just decides that this isn't a bundle anymore. Other bundles that are
> dependent on the exported packages say that these packages are no longer
> available. The package no longer shows up in the run configuration
> check-box list.
>
> The PDE menu does not, however, give me the option of converting the
> project to a plug-in project. It realizes the project already IS a
> plug-in. It's the rest of the PDE that disagrees. I 've checked all of
> the plugin, classpath files, etc. Is there some kind of external file,
> perhaps the run-configuration file, that would contain config data
> determining whether or not this project gets treated like a plug in?
>
> It's frustrating - the only way I could fix the problem last time was
> make a new plug in project under a different name and copy everything to
> it.
>
> Note, this is an entirely different plug-in from the one I had problems
> with in the past.
What's your .classpath file? What's in the .project file?
Let's start there to see what the problem may be. Do you have something
external (like maven) that may touch project files?
In Eclipse 3.5, the Target Platform State view should show you PDE's
view on the world (OSGi state).
Cheers,
Chris Aniszczyk | EclipseSource Austin | +1 860 839 2465
http://twitter.com/eclipsesource | http://twitter.com/caniszczyk
|
|
| | | | | | | | | |
| Re: Eclipse stopped treating plug-in project as a plug-in project - again! [message #600568 is a reply to message #479674] |
Tue, 11 August 2009 19:31 |
| Eclipse User |
|
|
|
Michael Sullivan wrote:
> I posted this comment last month. Since then, I have encountered the
> problem again.
>
> I have an OSGi plug-in that I am using in Eclipse and testing in the
> built-in equinox OSGi container. I'm using a bunch of other bundles
> with it. At some point after closing an instance of the server, Eclipse
> just decides that this isn't a bundle anymore. Other bundles that are
> dependent on the exported packages say that these packages are no longer
> available. The package no longer shows up in the run configuration
> check-box list.
>
> The PDE menu does not, however, give me the option of converting the
> project to a plug-in project. It realizes the project already IS a
> plug-in. It's the rest of the PDE that disagrees. I 've checked all of
> the plugin, classpath files, etc. Is there some kind of external file,
> perhaps the run-configuration file, that would contain config data
> determining whether or not this project gets treated like a plug in?
>
> It's frustrating - the only way I could fix the problem last time was
> make a new plug in project under a different name and copy everything to
> it.
>
> Note, this is an entirely different plug-in from the one I had problems
> with in the past.
What's your .classpath file? What's in the .project file?
Let's start there to see what the problem may be. Do you have something
external (like maven) that may touch project files?
In Eclipse 3.5, the Target Platform State view should show you PDE's
view on the world (OSGi state).
Cheers,
Chris Aniszczyk | EclipseSource Austin | +1 860 839 2465
http://twitter.com/eclipsesource | http://twitter.com/caniszczyk
|
|
| | | | | | | | |
| Re: Problem (apparently) Solved [message #603145 is a reply to message #481082] |
Tue, 10 November 2009 08:31 |
| Eclipse User |
|
|
|
I've had the same problem here (and a collegue of mine had so, too).
Investigating the issue brought me to Manifest.MF and there I found the origin of this problem: There was a duplicate entry in "Import-Package".
1) This does not generate a warning!
2) Formatting the code removes the duplicate entry without further messages.
3) Only some internals of eclipse are affected by this problem, whereas other mechanisms are not prone to this issue. Those are affected:
Run/Debug configurations: The problematic bundle will not show up.
Dependant plugins: Yes, you can add the problematic bundle as required bundle, but it won't be found during build.
|
|
|
Goto Forum:
Current Time: Sun Jul 27 01:59:10 EDT 2025
Powered by FUDForum. Page generated in 0.09883 seconds |
Home