Home

About

After developing multiple eclipse plugins with a copy waste approach the maintenance effort became too much. So instead of having same and same code again inside de-jcup eclipse plugins, the plugins shall use a eclipse-commons library (which will NOT be exported by plugins).

Pro and contra for a commons library approach

Pro

• There will be only one code base for common parts
• code base will be versioned by jar
• Maintenance can be done on only one peace of code, usage must only use new library.
• Better implementation because of more generic approach

Contra

• As long as there is no correct maven/gradle build for de-jcup plugins there is a need to have the library checked in

But having only one single point for the development of common features is the most relevant part, so decided for library approach.