Eclipse Foundation Executive Director Mike Milinkovich criticized Microsoft on Tuesday for not approaching Eclipse about interoperability between .Net and open source Eclipse technologies.
Speaking at the EclipseCon conference, Milinkovich also shined a spotlight on OSGi (Open Services Gateway initiative), which provides the basis of Eclipse's core plug-in model for software development.
Commenting on Microsoft, Milinkovich said Microsoft sends representatives to EclipseCon every year. Eclipse and Microsoft officials in attendance then agree that a meeting ought to be set up between the two sides. But afterward, "they never call," Milinkovich said.
"Ask your friends at Microsoft what they're doing to interoperate with Eclipse," Milinkovich said during a press conference.
Milinkovich said he expects Microsoft to someday join Eclipse and that there are enough points of interaction between these two development "universes" that interoperability is the right thing to do.
Currently, there are a few point solutions for interoperability, such as Teamprise providing an Eclipse plug-in enabling Eclipse-based developers to access Microsoft's Visual Studio 2005 Team Foundation Server product for application lifecycle management, Milinkovich said. (Teamprise announced on Tuesday that it has joined the Eclipse Foundation.)
But users would benefit from cooperation between the two camps to provide interoperability, Milinkovich said. A company with, for example, developers building in .Net and on the Eclipse Rich Client Platform might want to see resulting applications be easily interoperable, he said.
Microsoft, contacted for its response to Milinkovich's plea, declined to comment. But an industry analyst questioned whether Microsoft really needs to do anything about interoperating with Eclipse.
"I think there's a lot of people that make a very good living bridging the two [platforms] and SOA makes that less of an issue," said Dana Gardner, principal analyst at Interarbor Solutions. With SOA, the use of mashups and services boosts interoperability, according to Gardner.
Eclipse technologies based on OSGi could become the open source alternative to .Net for software development, Milinkovich said.
Eclipse began basing its technology on the OSGi component standard with the Eclipse 3.0 platform in 2004. "OSGi I believe is going to be one of those overnight successes that endures eight years or nine years in the making," Milinkovich said.
"It's a component model for Java and this is something that Java actually has been lacking since its inception," Milinkovich said. The OSGi community is participating in Java Specification Request 291, which would have OSGi become part of the Java component model, Milinkovich said.
"One of the great things about [OSGi] is it's supported by a number of vendors and open source communities. Eclipse is not the only implementation of OSGi," Milinkovich said.