Lubos, I completely agree that
the dev list should be used to ease porting and you should always feel free to
ask questions of this sort and expect them to be answered. This will help
us refine the Porting Guide. The idea is that for any changes that cannot
be fixed by organizing imports you should be able to hit Ctrl+F on the Porting
Guide to figure out what to do. The changes for the 2.0 APIs are going to
be substantial, largely because we are trying to make it easier to create
connectors. We want to make sure that we make porting as straightforward
as possible.
I've updated the Porting Guide
to ensure that each of your questions is answered more clearly. To
summarize:
· AbstractRepositoryTask.getElapsedTime()
was removed - where do I get elapsed time info?
This method was on Task and was
not used. Use TaskListManager.getElapsedTime(ITask) instead, but note
that it might move to a new TaskActivityManager class (see Pending Changes
section)
· AbstractRepositoryTask.getIdentifyingLabel
() was removed - how do I set the task list label?
Set it in the constructor or
use setDescription().
· AbstractRepositoryQuery.setMaxHits() was
removed - is max hits still supported and if so where should it be set?
Max hits turned out to be a bad
idea, use QueryHitCollector.MAX_HITS if you want to constrain hits, see the
following bug for details:
176297: [api] get rid of query
max setting
https://bugs.eclipse.org/bugs/show_bug.cgi?id=176297
Let us know if you have any
other questions and please feel free to elaborate on the entries in the porting
guide if anything is unclear.
Mik
Nathan,
I do not think that porting guide is very useful answering my questions.
It does not explain where to get "elapsed time", and it does not
explain if there is any replacement
for maxHits or if maxHits are now hardcoded.
It is not easy to develop Mylar connector. It should be at least reasonably
easy to port it to next Mylar version 8-).
And help from dev list is critical for the connector developers.
Lubos Pochman