Developers and CTOs know: Frequently changing teams and the “liberal” use of the latest and greatest technologies makes your burndown charts and project cost estimations burst within just a few weeks.
To compensate for "brain drain" and to lower the entrance barrier, team leads plan a fair amount of their team's time for documenting software, doing reviews, and pair programming to evenly spread the knowledge about how to use APIs over the whole team - and to newcomers in particular.
If done right, this is the best a team lead can do to make the team effective in the long run. But Code Recommenders thinks that there is more a team lead can do...
How much can an IDE predict what you will write in the next seconds?
At first glance, you might answer: nothing. Indeed, the information needed to complete the source code is primarily in the developer's brain. However, API designers typically have some expectations about how developers should use their APIs, i.e., they expect their clients to call certain methods at certain points in time and in particular order. The challenge to all newcomers is thus to learn about these implicit expectations and API usage rules fast enough to be of help for the team they joined.
Eclipse Code Recommenders assists developers on learning how to use and extend new APIs by analyzing applications that successfully applied the framework before and re-integrating this knowledge back into your IDE as :
* Intelligent Call Completion,
* Intelligent Method Overrrides Completion, and even
* Simple Code Snippets, and
* additional API documentation.
Check http://eclipse.org/recommenders/documentation/usr.html for a feature overview.
Please use the following update sites to get the latest RC features for Eclipse Juno:
Reviews
does not work with e4
org.eclipse.e4.core.di.InjectionException: java.lang.LinkageError: loader constraint violation: when resolving method "org.eclipse.recommenders.utils.rcp.JdtUtils.createUnresolvedType(Lorg/eclipse/jdt/internal/compiler/lookup/TypeBinding;)Lcom/google/common/base/Optional;" the class loader (instance of org/eclipse/osgi/internal/baseadaptor/DefaultClassLoader) of the current class, org/eclipse/recommenders/internal/completion/rcp/BaseRecommendersCompletionContext, and the class loader (instance of org/eclipse/osgi/internal/baseadaptor/DefaultClassLoader) for resolved class, org/eclipse/recommenders/utils/rcp/JdtUtils, have different Class objects for the type com/google/common/base/Optional used in the signature
This is fixed in HEAD and
This is fixed in HEAD and will be rolled out today on Eclipse Marketplace.