[news.eclipse.technology.kepler] Re: Proposed Kepler project plan on wik

[Thomas Hallgren <thomas@xxxxxxx>]

Hi Scott,

Scott Lewis wrote:
> Yes.  Kepler will absolutely not plan (or do) a rewrite of technology 
> already in Eclipse projects.  The draft doesn't state this and so 
> creates a wrong impression.
This is good to know. I think it would be beneficial if the draft did change its wording in 
some places in order to avoid misunderstandings. It's important to discuss how things are 
supposed to work, where functionality is best implemented and by who.

As an example, in Milestone 2 where it says that Headless Eclipse-Plugin and OSGi Builds are 
orchestrated by a Maven plugin from Codehaus it should mention other technologies too. The 
fact that existing Eclipse Technology Projects already covers the functionality is important 
and must not be omitted.

I think it would be great if we could increase the communication between Kepler and the 
technology projects that already do implement a lot of the functionality that the Kepler 
proposal is covering. Buckminster covers a lot of the build management functionality. Corona 
already have functional solutions for lot of the community issues, etc. We need to 
investigate the feasibility of using them and increase the knowledge transfer between the 
projects. In my opinion that should have priority.

That said, I'm not at all against using external technology if discussions around 
functionality leads us to believe that it would be beneficial. We just need to have those 
discussions first and perhaps do some research within Eclipse prior to making suggestions 
indicating what way to go.

Regards,
Thomas Hallgren