Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [] The Opportunity

We do not rely on any metadata elements from Eclipse IDE. Che had to create a different set given the structure of the workspace is different.

We explored what would be involved with making it possible to import Eclipse projects directly into Che, and the conclusion is that we can probably handle 80% of the cases with 1% conversion.  And then other 20% of the cases would be impossible or require tremendous efforts.  Che workspace always require a runtime, so there would be a substantial matching exercise that would be needed to generate the right runtime to support a particular Eclipse project, and this would be error prone.

Best to assume that everything is different inside of Che - as everything had to be structured for packaging with a distributable, hosted workspace.

I didn't understand the point about serialization or resource model - mostly because I don't know what Eclipse does with those.

Tyler Jewell | CEO | tyler@​codenvy.​com | 9​78​.8​84​.53​55

On Wed, Mar 23, 2016 at 7:17 AM, Mickael Istria <mistria@xxxxxxxxxx> wrote:
On 03/23/2016 02:52 PM, Tyler Jewell wrote:
Someone asked about how SSH with file mounting works with Eclipse Che + Eclipse IDE.

Pretty cool. Thanks!
I noticed that this example project has a .project and a .classpath file. Does Che relies on those metadata files from Eclipse IDE and JDT? and what about preferences other project settings, does Che also use traditional location, serialization and API ? More generally: Does Che rely on the Eclipse resource model or does it have something else/more on that topic?
Mickael Istria
Eclipse developer at JBoss, by Red Hat
My blog - My Tweets

_______________________________________________ mailing list

IMPORTANT: Membership in this list is generated by processes internal to the Eclipse Foundation.  To be permanently removed from this list, you must contact emo@xxxxxxxxxxx to request removal.

Back to the top