[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [epp-dev] Code Recommenders: gathering information for potential package inclusions

Hi Markus, Steffen, Ian,

We are currently rewriting these parts and will probably be ready mid/end of January.

most of the critical rewrites are done or will be done until the end of the week. We've hudson builds for 3.x and 4.2 and will likely join the aggregation build by the end of the week. I'll get in contact with Java Package and RCP/RAP via Bugzilla to discuss next steps and requirements.

Ian, for JEE I need to discuss with the Foundation whether a usage data collector for community-driven model generation would be supported. It's challenging to find a sufficient amount of (open source) data to create a reasonable coverage for existing JEE libraries.

Best,
Marcel

On 05.12.2011, at 16:20, Marcel Bruch wrote:

Hi Markus, Steffen and Ian,

Java and RCP/RAP would be my favorite packages. RCP is a perfect fit since we already have lots of the data for it. Java is excellent since we can generate models for Java SDK quite easily and many tools work out-of-the-box. 

However, I'm a bit cautious at the moment. In the past months we received a lot feedback and learned that some of our concepts fall too short and need improvement. We are currently rewriting these parts and will probably be ready mid/end of January.

Would it be ok to test the package in January after the rewrite of the code analyzer and extdoc parts?


On 05.12.2011, at 15:57, Markus Knauer wrote:

I was a little bit selfish when I asked you to propose Code Recommenders for package inclusion. How about opening another bug against the RCP/RAP package? If it is not too large I would be willing to give it a try in the RCP/RAP package as well, but I will need some testing support.

Thanks,
Markus

On Mon, Dec 5, 2011 at 14:11, Ian Skerrett <ian.skerrett@xxxxxxxxxxx> wrote:
I also think the Java EE package would be a logical place for Code Recommenders.  You might open a bug for the package too.

Ian


On 12/5/2011 8:09 AM, Steffen Pingel wrote:
Hi Marcel,

great to hear that Code Recommenders will be part of the release train! 

Given the strong focus on Java development it sounds like the Java package may be a natural target. If you are interested in including Code Recommenders please feel free to file a bug and put me on the CC. Questions that we typically ask when considering a new component for the package are listed on this wiki page: http://wiki.eclipse.org/EPP/How_to_create_a_package#Adding_components_to_a_package

Steffen


On Mon, Dec 5, 2011 at 12:10 PM, Marcel Bruch <bruch@xxxxxxxxxxxxxxxxxx> wrote:
Hi EPP-Dev,

after short conversation with Technology PMC we decided to join the annual release train for Juno. Markus Knauer told me that with joining the annual release train we may also be join some EPP packages - if there is a package owner willing to add Code Recommenders to their package.

Can any package owner imagine to integrate Code Recommenders into his package? If so, what requirements should we met? If not, it would be great to learn why.

What does Code Recommenders offer for annual release? 
We have several components that can be packaged separately (more details on request):

* Intelligent Method Call Completion & Method Overrides Completion
* Call Chain Completion
* Snipmatch 
* Extdoc Platform 
* Subwords Completion
* Usage Sharing Client to build continuously growing knowledge bases for intelligent completion + extdoc
* (maybe) new code search client + engine for Eclipse

A (not self-learning) version of Call Chain and Subwords Completion may already be handed over to JDT 3.8 until Juno. All tools work for Java only.


A video showing the above tool suite in action is available here:

PMC conversation about joining the release train:

Code Recommenders source code repository:


Thanks,
Marcel