Bug 512533 - PDE misses extension point in plug-in manifest
Summary: PDE misses extension point in plug-in manifest
Status: NEW
Alias: None
Product: PDE
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 4.7   Edit
Hardware: PC Windows 7
: P3 normal with 5 votes (vote)
Target Milestone: ---   Edit
Assignee: Vikas Chandra CLA
QA Contact:
URL:
Whiteboard:
Keywords: investigate
Depends on:
Blocks:
 
Reported: 2017-02-21 15:16 EST by Markus Keller CLA
Modified: 2024-03-18 06:11 EDT (History)
10 users (show)

See Also:


Attachments
Unable to recreate (182.48 KB, image/jpeg)
2017-02-23 01:50 EST, Vikas Chandra CLA
no flags Details
Problem (253.08 KB, image/gif)
2018-02-09 13:35 EST, Wim Jongman CLA
no flags Details
Eclipse does not recognize org.eclipse.chemclipse extension points (313.50 KB, image/png)
2021-12-02 07:35 EST, Matthias Mailänder CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Markus Keller CLA 2017-02-21 15:16:33 EST
Steps from bug 512424 comment 3:

I20170220-2000

- import bundles/org.eclipse.equinox.registry from master of git://git.eclipse.org/gitroot/equinox/rt.equinox.bundles.git

=> There's a wrong compiler warning on the plugin.xml:
"A plug-in manifest must contain at least one extension or extension point"

The plugin.xml contains an extension-point "org.eclipse.core.runtime.adapters".
Comment 1 Vikas Chandra CLA 2017-02-23 01:50:25 EST
Created attachment 266957 [details]
Unable to recreate

See img attached. Can you provide more details? Does it happen in a fresh workspace with just this plugin or there are other factors too?
Comment 2 Markus Keller CLA 2017-03-22 12:23:41 EDT
Happened in my main workspace, but I could also reproduce in a fresh workspace, and I can still reproduce in a clean runtime workspace.

To reproduce, you have to reset the equinox repo to d071f6db6f8663fe86b9a372def46efc5b0bfeb8 (master at the time this bug was filed).

The problem could be related to the classpath problems mentioned in bug 512424 comment 3.
Comment 3 Vikas Chandra CLA 2017-04-26 06:33:01 EDT
I am able to recreate this today.
Comment 4 Wim Jongman CLA 2018-02-09 13:35:09 EST
I noticed the same thing. See animated gif attachment.

The project was also installed in the IDE and I was maintaining a newer version in the workspace.

After I installed the same version as I have in the workspace, and a restart, the problem went away.
Comment 5 Wim Jongman CLA 2018-02-09 13:35:40 EST
Created attachment 272617 [details]
Problem
Comment 6 Wim Jongman CLA 2018-02-09 13:36:12 EST
Eclipse IDE for Eclipse Committers
Version: Oxygen.2 Release (4.7.2)
Build id: 20171218-0600
OS: Windows 10, v.10.0, x86_64 / win32
Comment 7 Dave Dresser CLA 2018-10-19 10:42:10 EDT
I work on a team developing an RCP application. We currently use Oxygen SR3.  We also have this problem. For us the problem is intermittent. Sometimes I've had it and at other times I don't (same with other team members).  This morning I had the problem and I was discussing it with another team member and he mentioned that if you switch your target platform to the Running Platform the warning goes away.  So I switched my target to the Running Platform and after it resolved, I immediately switched it back.  The warning went away and did not reappear after switching back.  When I've had the problem it seems to be persistent across shutdown and startup.
Comment 8 Eike Stepper CLA 2020-04-02 03:36:23 EDT
I'm still seeing this in:

Eclipse IDE for Eclipse Committers
Version: 2020-03 (4.15.0)
Build id: 20200313-1211

Are there chances that someone looks at this for the next release?
Comment 9 Julian Honnen CLA 2020-04-02 05:28:20 EDT
Can you share a self-contained project to reproduce the issue? I don't see that warning in equinox.registry.
Comment 10 Eike Stepper CLA 2020-04-02 07:15:09 EDT
Who?

Unfortunately I can not. All people who reported this problem say it's a flaky phenomenon. It comes and goes and to me it does not seem to be related to any particular condition in a specific project.
Comment 11 Matthias Mailänder CLA 2021-12-02 07:35:53 EST
Created attachment 287609 [details]
Eclipse does not recognize org.eclipse.chemclipse extension points

Screenshot made in Version: 2018-09 (4.9) sorry, it is what SUSE ships at the moment. Not really a minimal example, but https://github.com/eclipse/chemclipse has quite a few of those issues. I believe those warnings are displayed pretty constantly.
Comment 12 Matthias Mailänder CLA 2021-12-02 07:37:16 EST
Is this a reverse duplicate of bug 564927?
Comment 13 Wim Jongman CLA 2021-12-02 07:57:51 EST
(In reply to Matthias Mailänder from comment #11)
> Created attachment 287609 [details]
> Eclipse does not recognize org.eclipse.chemclipse extension points
> 
> Screenshot made in Version: 2018-09 (4.9) sorry, it is what SUSE ships at
> the moment. Not really a minimal example, but
> https://github.com/eclipse/chemclipse has quite a few of those issues. I
> believe those warnings are displayed pretty constantly.

It would be nice if you could upgrade to 4.21/22 and confirm it is still an issue.
Comment 14 Matthias Mailänder CLA 2022-01-18 08:31:46 EST
This seems to be resolved in

Version: 2021-12 (4.22.0)
Build id: 20211202-1639
Comment 15 Dennis Hendriks CLA 2023-09-07 04:40:21 EDT
I still get this in Eclipse 2023-03. Problem is thus not solved.
Comment 16 Dennis Hendriks CLA 2023-09-07 04:44:37 EDT
This issue seems related to, or maybe even identical, to bug 564927.
Comment 17 Matthias Mailänder CLA 2024-03-18 06:11:24 EDT
I updated build.properties files, which then spawned many incorrect warnings in version 2024-03 (4.31.0) where the extension point is defined in the same plugin.