views:

76

answers:

1

I have been having a real hard time getting API Tooling to work in Eclipse 3.4.2. It keeps telling me:

The minor version should be incremented in version 3.4.0.qualifier, since new APIs have been added since version 3.4.0.40001

That being said, I have generated the plugins that are used for the baseline from the exact same code that it is being analyzed against. The API Tools docs say that it compares the current code against the baseline to see if there are any differences. I can't see how there could be differences if the built version is built from the current code.

The way that I tested it:

  1. Create a new eclipse workspace
  2. Create a new Plug-in Project with API Analysis turned on
  3. Add a simple class to that plugin and export the package with that class in it
  4. Build/Export that plugin to some location on your hard drive
  5. Set the workspace baseline to that location and do a full build

You get an error for the project in your problems view.

Thanks,

-One very perplexed user

A: 

Looks like this is something that got fixed in 3.5. Too bad my company doesn't want us using 3.5 in case there are any incompatibility issues. (there were 3.3 to 3.4)

My recommendation to anyone who wants to do Eclipse API Analysis is to use 3.5.

GreenKiwi
We recently migrated our product from 3.2 base platform to 3.5 and even at such a great leap, the problems we encountered were minor and with some minor exceptions the basic transition wqas quite smooth...Before we migrated, we had a analysis of the changes to the platform and we analyzed if it would make sense to migrate to 3.5 or 3.4 base platform.As a result we found that API wise the most major changes fell between 3.2 and 3.4 bases and the actual amount of potentially incompatible changes between 3.4 -> 3.5 were just too small to outweigh the potential gains of a newer release...
Roland Tepp
Thanks. We are just making the transition ourselves. I'll update with how the API analysis goes.
GreenKiwi