Eclipse Community Forums: Plugin Development Environment (PDE) » Eclipse stopped treating plug-in project as a plug-in project - again!

Search

Help

Login

Home » Eclipse Projects » Plugin Development Environment (PDE) » Eclipse stopped treating plug-in project as a plug-in project - again!

Show: Today's Messages :: Show Polls :: Message Navigator

Switch to threaded view of this topic

Create a new topic

Submit Reply

Eclipse stopped treating plug-in project as a plug-in project - again! [message #479674]

Tue, 11 August 2009 22:46

Michael Sullivan is currently offline

Michael Sullivan

Friend

Messages: 37
Registered: July 2009

Member

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

Report message to a moderator

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 23:31

Chris Aniszczyk is currently offline

Chris Aniszczyk

Friend

Messages: 674
Registered: July 2009

Senior Member

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

Report message to a moderator

Re: Eclipse stopped treating plug-in project as a plug-in project - again! [message #479680 is a reply to message #479678]

Wed, 12 August 2009 00:12

Michael Sullivan is currently offline

Michael Sullivan

Friend

Messages: 37
Registered: July 2009

Member

Classpath:
<?xml version="1.0" encoding="UTF-8"?>
<classpath>
<classpathentry kind="con"
path=" org.eclipse.jdt.launching.JRE_CONTAINER/org.eclipse.jdt.inte rnal.debug.ui.launcher.StandardVMType/JavaSE-1.6 "/>
<classpathentry kind="con" path="org.eclipse.pde.core.requiredPlugins"/>
<classpathentry kind="src" path="src"/>
<classpathentry kind="output" path="bin"/>
</classpath>

project
<?xml version="1.0" encoding="UTF-8"?>
<projectDescription>
<name>mike.test.feature.manager</name>
<comment></comment>
<projects>
</projects>
<buildSpec>
<buildCommand>
<name>org.eclipse.jdt.core.javabuilder</name>
<arguments>
</arguments>
</buildCommand>
<buildCommand>
<name>org.eclipse.pde.ManifestBuilder</name>
<arguments>
</arguments>
</buildCommand>
<buildCommand>
<name>org.eclipse.pde.SchemaBuilder</name>
<arguments>
</arguments>
</buildCommand>
</buildSpec>
<natures>
<nature>org.eclipse.pde.PluginNature</nature>
<nature>org.eclipse.jdt.core.javanature</nature>
</natures>
</projectDescription>

I do have a maven plugin installed, but this project has no pom.xml and I
let the default compiler/build tools build and deploy it to OSGi.

I'm running Eclipse 3.4 but I'll try upgrading tonight to 3.5.

Thanks for the help,
Mike

Report message to a moderator

Re: Eclipse stopped treating plug-in project as a plug-in project - again! [message #479683 is a reply to message #479680]

Wed, 12 August 2009 00:24

Michael Sullivan is currently offline

Michael Sullivan

Friend

Messages: 37
Registered: July 2009

Member

Not sure if it helps, but my former-plug-in is lacking a .location file
under org.eclipse.core.resources/.projects/<former-plug-in> that many of
my other plugins have. Looks binaryish though.

Report message to a moderator

Re: Eclipse stopped treating plug-in project as a plug-in project - again! [message #480554 is a reply to message #479678]

Mon, 17 August 2009 15:33

Michael Sullivan is currently offline

Michael Sullivan

Friend

Messages: 37
Registered: July 2009

Member

OK, So i've upgraded to 3.5, and the same problem. Target Platform state
does not include my prodigal project. I recall from 3.4 there was a
target platform checkbox where you stated whether or not new projects
should become part of the target. Where is that data stored? Can I
manually edit a file to 'remind' Eclipse about this plugin?

Report message to a moderator

OK, Now I'm really confused. [message #480924 is a reply to message #479674]

Tue, 18 August 2009 23:56

Michael Sullivan is currently offline

Michael Sullivan

Friend

Messages: 37
Registered: July 2009

Member

As I mentioned above, I was able to solve this problem in the past by
creating a new project and copying the content of the old project to it.
Well, I created the new project and copied the content over. It didn't
show up in the Target Platform State, and the dependencies it provided
were not found by other projects.

But my copy itself built.

Despite not having any of the dependencies *IT* required provided through
the build path or the Plug-in Dependencies tool.

And there is no maven involved.

But of course, the built code is not available for the run configuration,
since Eclipse still doesn't think it's a plug-in.

*sigh*

Report message to a moderator

Re: OK, Now I'm really confused. [message #480927 is a reply to message #480924]

Wed, 19 August 2009 00:08

Michael Sullivan is currently offline

Michael Sullivan

Friend

Messages: 37
Registered: July 2009

Member

OK, rebuilt it. And now it can't find any of its dependencies. yay?

Report message to a moderator

Problem (apparently) Solved [message #480929 is a reply to message #479674]

Wed, 19 August 2009 00:26

Michael Sullivan is currently offline

Michael Sullivan

Friend

Messages: 37
Registered: July 2009

Member

I went back to my non-plug-in plug-in, deleted all of the imports and
exports, and opened each java file in the editor. I clicked on the
'suggested fix' icon for each import statement that wasn't being found,
selected "add to manifest", and as I added each one, the relevant
dependency showed up in Plug-in Dependencies.

Then I did the same with the project that was dependent on this one.

It looks like the pde might have cached some kind of failure in building
the project where it just never tried rebuilding it? I don't know, just
thrilled that I can get back to some domain related issues and leave the
IDE ones behind. (i hope?)

Report message to a moderator

Re: Problem (apparently) Solved [message #480958 is a reply to message #480929]

Wed, 19 August 2009 07:58

Chris Aniszczyk is currently offline

Chris Aniszczyk

Friend

Messages: 674
Registered: July 2009

Senior Member

Michael Sullivan wrote:
> I went back to my non-plug-in plug-in, deleted all of the imports and
> exports, and opened each java file in the editor. I clicked on the
> 'suggested fix' icon for each import statement that wasn't being found,
> selected "add to manifest", and as I added each one, the relevant
> dependency showed up in Plug-in Dependencies.
>
> Then I did the same with the project that was dependent on this one.
> It looks like the pde might have cached some kind of failure in building
> the project where it just never tried rebuilding it? I don't know, just
> thrilled that I can get back to some domain related issues and leave the
> IDE ones behind. (i hope?)

If you can give me a small reproducible test case, that would be great.
It's hard to address your problem when I can't reproduce it on my end.
Maybe a remote debugging session could be in order if that would work
for you.

Cheers,

Chris Aniszczyk | EclipseSource Austin | +1 860 839 2465
http://twitter.com/eclipsesource | http://twitter.com/caniszczyk

Report message to a moderator

Re: Problem (apparently) Solved [message #481082 is a reply to message #480958]

Wed, 19 August 2009 14:51

Michael Sullivan is currently offline

Michael Sullivan

Friend

Messages: 37
Registered: July 2009

Member

Thanks Chris, if it happens again, I'll try to get something for you.
Right now, I need to get caught up on my project. When I get some free
time, I'll see if I can force it to happen, but I'm really not sure what's
causing it.

Mike

Report message to a moderator

Re: Problem (apparently) Solved [message #496540 is a reply to message #481082]

Tue, 10 November 2009 13:31

Dr. Christian Betz is currently offline

Dr. Christian Betz

Friend

Messages: 2
Registered: July 2009

Junior Member

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.

Report message to a moderator

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 23:31

Chris Aniszczyk is currently offline

Chris Aniszczyk

Friend

Messages: 674
Registered: July 2009

Senior Member

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

Report message to a moderator

Re: Eclipse stopped treating plug-in project as a plug-in project - again! [message #600578 is a reply to message #479678]

Wed, 12 August 2009 00:12

Michael Sullivan is currently offline

Michael Sullivan

Friend

Messages: 37
Registered: July 2009

Member

Classpath:
<?xml version="1.0" encoding="UTF-8"?>
<classpath>
<classpathentry kind="con"
path=" org.eclipse.jdt.launching.JRE_CONTAINER/org.eclipse.jdt.inte rnal.debug.ui.launcher.StandardVMType/JavaSE-1.6 "/>
<classpathentry kind="con" path="org.eclipse.pde.core.requiredPlugins"/>
<classpathentry kind="src" path="src"/>
<classpathentry kind="output" path="bin"/>
</classpath>

project
<?xml version="1.0" encoding="UTF-8"?>
<projectDescription>
<name>mike.test.feature.manager</name>
<comment></comment>
<projects>
</projects>
<buildSpec>
<buildCommand>
<name>org.eclipse.jdt.core.javabuilder</name>
<arguments>
</arguments>
</buildCommand>
<buildCommand>
<name>org.eclipse.pde.ManifestBuilder</name>
<arguments>
</arguments>
</buildCommand>
<buildCommand>
<name>org.eclipse.pde.SchemaBuilder</name>
<arguments>
</arguments>
</buildCommand>
</buildSpec>
<natures>
<nature>org.eclipse.pde.PluginNature</nature>
<nature>org.eclipse.jdt.core.javanature</nature>
</natures>
</projectDescription>

I do have a maven plugin installed, but this project has no pom.xml and I
let the default compiler/build tools build and deploy it to OSGi.

I'm running Eclipse 3.4 but I'll try upgrading tonight to 3.5.

Thanks for the help,
Mike

Report message to a moderator

Re: Eclipse stopped treating plug-in project as a plug-in project - again! [message #600595 is a reply to message #479680]

Wed, 12 August 2009 00:24

Michael Sullivan is currently offline

Michael Sullivan

Friend

Messages: 37
Registered: July 2009

Member

Not sure if it helps, but my former-plug-in is lacking a .location file
under org.eclipse.core.resources/.projects/<former-plug-in> that many of
my other plugins have. Looks binaryish though.

Report message to a moderator

Re: Eclipse stopped treating plug-in project as a plug-in project - again! [message #600726 is a reply to message #479678]

Mon, 17 August 2009 15:33

Michael Sullivan is currently offline

Michael Sullivan

Friend

Messages: 37
Registered: July 2009

Member

OK, So i've upgraded to 3.5, and the same problem. Target Platform state
does not include my prodigal project. I recall from 3.4 there was a
target platform checkbox where you stated whether or not new projects
should become part of the target. Where is that data stored? Can I
manually edit a file to 'remind' Eclipse about this plugin?

Report message to a moderator

OK, Now I'm really confused. [message #600771 is a reply to message #479674]

Tue, 18 August 2009 23:56

Michael Sullivan is currently offline

Michael Sullivan

Friend

Messages: 37
Registered: July 2009

Member

As I mentioned above, I was able to solve this problem in the past by
creating a new project and copying the content of the old project to it.
Well, I created the new project and copied the content over. It didn't
show up in the Target Platform State, and the dependencies it provided
were not found by other projects.

But my copy itself built.

Despite not having any of the dependencies *IT* required provided through
the build path or the Plug-in Dependencies tool.

And there is no maven involved.

But of course, the built code is not available for the run configuration,
since Eclipse still doesn't think it's a plug-in.

*sigh*

Report message to a moderator

Re: OK, Now I'm really confused. [message #600787 is a reply to message #480924]

Wed, 19 August 2009 00:08

Michael Sullivan is currently offline

Michael Sullivan

Friend

Messages: 37
Registered: July 2009

Member

OK, rebuilt it. And now it can't find any of its dependencies. yay?

Report message to a moderator

Problem (apparently) Solved [message #600794 is a reply to message #479674]

Wed, 19 August 2009 00:26

Michael Sullivan is currently offline

Michael Sullivan

Friend

Messages: 37
Registered: July 2009

Member

I went back to my non-plug-in plug-in, deleted all of the imports and
exports, and opened each java file in the editor. I clicked on the
'suggested fix' icon for each import statement that wasn't being found,
selected "add to manifest", and as I added each one, the relevant
dependency showed up in Plug-in Dependencies.

Then I did the same with the project that was dependent on this one.

It looks like the pde might have cached some kind of failure in building
the project where it just never tried rebuilding it? I don't know, just
thrilled that I can get back to some domain related issues and leave the
IDE ones behind. (i hope?)

Report message to a moderator

Re: Problem (apparently) Solved [message #600805 is a reply to message #480929]

Wed, 19 August 2009 07:58

Chris Aniszczyk is currently offline

Chris Aniszczyk

Friend

Messages: 674
Registered: July 2009

Senior Member

Michael Sullivan wrote:
> I went back to my non-plug-in plug-in, deleted all of the imports and
> exports, and opened each java file in the editor. I clicked on the
> 'suggested fix' icon for each import statement that wasn't being found,
> selected "add to manifest", and as I added each one, the relevant
> dependency showed up in Plug-in Dependencies.
>
> Then I did the same with the project that was dependent on this one.
> It looks like the pde might have cached some kind of failure in building
> the project where it just never tried rebuilding it? I don't know, just
> thrilled that I can get back to some domain related issues and leave the
> IDE ones behind. (i hope?)

If you can give me a small reproducible test case, that would be great.
It's hard to address your problem when I can't reproduce it on my end.
Maybe a remote debugging session could be in order if that would work
for you.

Cheers,

Chris Aniszczyk | EclipseSource Austin | +1 860 839 2465
http://twitter.com/eclipsesource | http://twitter.com/caniszczyk

Report message to a moderator

Re: Problem (apparently) Solved [message #600822 is a reply to message #480958]

Wed, 19 August 2009 14:51

Michael Sullivan is currently offline

Michael Sullivan

Friend

Messages: 37
Registered: July 2009

Member

Thanks Chris, if it happens again, I'll try to get something for you.
Right now, I need to get caught up on my project. When I get some free
time, I'll see if I can force it to happen, but I'm really not sure what's
causing it.

Mike

Report message to a moderator

Re: Problem (apparently) Solved [message #603145 is a reply to message #481082]

Tue, 10 November 2009 13:31

Dr. Christian Betz is currently offline

Dr. Christian Betz

Friend

Messages: 2
Registered: July 2009

Junior Member

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.

Report message to a moderator

Switch to threaded view of this topic

Create a new topic

Submit Reply

Previous Topic:	problem triggering checkstyle jar
Next Topic:	Cleanest way to allow plugin version ranges

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Thu Apr 18 08:03:15 GMT 2024

Powered by FUDForum. Page generated in 0.02475 seconds

.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top