Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 335430

Summary:	Errors after changing bundle version
Product:	[Eclipse Project] PDE	Reporter:	Dani Megert <daniel_megert>
Component:	API Tools	Assignee:	PDE API Tools Inbox <pde-apitools-inbox>
Status:	RESOLVED WORKSFORME	QA Contact:
Severity:	normal
Priority:	P3	CC:	pwebster
Version:	3.7
Target Milestone:	---
Hardware:	PC
OS:	Windows XP
Whiteboard:

Description Dani Megert

2011-01-26 05:01:00 EST

I20110124-1800.


I get this error from time to time (see e.g. bug 246957) and it happened again yesterday. I have the steps that cause it but I can't reproduce on a fresh workspace yet.

0. Have
   - lots of source projects from CVS
   - remaining required projects imported as binary plug-ins
1. In the dev workspace fix a bug and save the file
   ==> no new error/warning (OK)
2. Increase the service segment in the Bundle-Version of the MANIFEST.MF, save
==> error is reported on MANIFEST.MF that some breakage happened and that I need to increase the major segment.

- clean all + full build does not fix the problem
- restart does not fix the problem
- restart + clean all + full build does not fix the problem

==> I have to delete all folders except .api_profiles and .api_stubs from 
.metadata\.plugins\org.eclipse.pde.api.tools and then rebuild my workspace to get rid of the error.

This indicates to me that something in the cached data is not up-to-date. Maybe this is caused by the following workflow that I often follow:
- replace a binary plug-in with its version from CVS
- replace a CVS shared plug-in with the binary version

Maybe Clean (All) should also clear the API Tools cache?

Comment 1 Dani Megert

2011-01-26 05:05:44 EST

In the concrete case, the only thing I did was to change the bundle version of 'org.eclipse.ui.console' from "3.5.0.qualifier" to "3.5.100.qualifier".

>Maybe Clean (All) should also clear the API Tools cache?
See also bug 255104.

Comment 2 Eclipse Genie

2019-02-25 18:16:37 EST

This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.

Comment 3 Dani Megert

2019-02-26 10:41:51 EST

I've not seen this for years.