# First Class Eclipse Support

DevFeed: [First Class Eclipse Support](<https://devfeed.tech/articles/first-class-eclipse-support-19303.md>)

Original publisher: [Read original article](<https://www.codenameone.com/blog/first-class-eclipse-support/>)

Author: Shai Almog

Published: 2017-01-09T00:00:00Z

Content type: release

Language: en

Sources: [CodeName One](<https://devfeed.tech/sources/codename-one.md>)

Topics: [ide](<https://devfeed.tech/topics/ide.md>), [Code](<https://devfeed.tech/topics/code.md>)

Tags: [eclipse](<https://devfeed.tech/tags/eclipse.md>), [ide](<https://devfeed.tech/tags/ide.md>), [improvements](<https://devfeed.tech/tags/improvements.md>), [mac](<https://devfeed.tech/tags/mac.md>), [os](<https://devfeed.tech/tags/os.md>), [plugin](<https://devfeed.tech/tags/plugin.md>), [regression](<https://devfeed.tech/tags/regression.md>), [release](<https://devfeed.tech/tags/release.md>), [update](<https://devfeed.tech/tags/update.md>), [windows](<https://devfeed.tech/tags/windows.md>)

## AI overview

Codename One reports improved Eclipse IDE support, integrating the Eclipse plugin into the standard release process so it can be released alongside the other plugins. Version 3.6.0 includes newer demos, while cn1lib creation support remains unavailable.

## Source excerpt

Our eclipse IDE support has been around for quite a while now but has never stood up to the quality and update pace of NetBeans. Recently even our IntelliJ/IDEA support has surpassed the quality of our eclipse plugin and the blame should be on us. One of the problems is that our team doesn't use eclipse and uses a diverse set of OS's (Macs/Windows) which is problematic when sharing workspaces. Integrating the eclipse plugin build into our standard release process proved really hard and it ended up eventually as something we need to do but never got around to do it...