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.
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
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):