EMC: Please Update the Eclipse used in Composer

The absolute newest version of Composer available is built on top of a 3 year old ganyemede version of Eclipse (3.4, 2008). This is unacceptable. I would like very much to have modern plugin functionality such as eGit for managing my Documentum projects but i cannot install it because the version of eclipse that is used by Composer is so very old. In fact, it would be preferable if you would distribute Composer as plugins that could be installed into the most recent eclipse version and then we could avoid this problem entirely. I'll also sumbit this as a feature request in PowerLink.

Find more posts tagged with

Comments

ukdavo

I would add that it would be very useful to developers if the Composer plugins were not tightly coupled to Eclipse.

For example, have a core API for compiling/deploying DARs then add a thin Eclipse plugin wrapper. This is so that we can construct a DAR without bootstrapping Eclipse in order to run an Ant build. I mean - that's just mental. Surely we should be able to just run some Ant tasks.. which would then allow us to hook this into Maven, Jenkins, etc.

Also, why not make the source code available for Composer. The tooling is useless without Content Server anyway. I'm sure that developers would pick up loads from the source code.

aflowers001

Paul Warren's blog has some ways to install Composer 'extras' into a standard Eclipse.

Julien.Fontaine

You can only install the plugin on the newest version of Eclipse. Have a look to the Paul Warren's blog.

Alvaro_de_Andres

As already said, you can install the composer plugin in the newest version of eclipse, and then install whatever plugin you need, however this is not a supported composer.

I don'tk we'll be seeing a composer build over a newer eclipse until D7, when they plan to unify all the aplications into eclipse. (I've seen the xCP 2.0 preview and I am quite sure it wasn't ganymedes eclipse the one they were using...)