Oberhuber, Martin wrote:
I believe the question was the
other way round:
Can we use Eclipse 3.5 (PDE)
tooling to safely develop software that should run on Eclipse 3.4.
Assuming that the "appInfo"
markup was being read case-insensitive by Eclipse 3.4, I believe that
we don't need to worry.
Yes. We know from our customers that they move slower to new versions
than we do. I am aware of customers that still use 3.3 and 3.4. I
wouldn´t say that appInfo is just a hint it is on the same level as
And if I am not mistaken, the
"appInfo" markup always just was a hint for tooling, and not relevant
for the runtime.... so even
if 3.4 was case sensitive, only
PDE Tooling / users of a 3.4 SDK would be affected but the runtime
Senior Member of Technical Staff, Wind
Management Project Lead, DSDP PMC Member
On Thu, Aug 6, 2009 at 1:57 AM, Stefan Liebig <Stefan.Liebig@xxxxxxxxxxxx>
I recently noticed that the Extension Point Schema Editor introduced a
change in the schema definition for extension points.
It changed the element from
- element/annotation/appinfo to element/annotation/appInfo
- attribute/annotation/appinfo to attribute/annotation/appInfo
(i.e. the 'i' in appinfo changed to 'I' in appInfo)
I am wondering whether this might cause problems for users of a pre 3.5
Eclipse IDE when using exsd's from a 3.5 Eclipse IDE.
If I understand what you're asking, Eclipse never aims to be forward compatible. In reality, this means you can't take something like Eclipse 3.4 and point it to a Eclipse 3.5 target. Eclipse aims to be backwards compatible.
Eclipse 3.5 should be able to deal with both of those formats.
A better forum for this discussion would be on the Eclipse PDE forums (or newsgroups)
Chris Aniszczyk | EclipseSource Austin | +1 860 839 2465