[stellation-res] A complete plugin setup?

[Ringo De Smet <ringods@xxxxxxxxxxx>]

Hello guys,

At the moment, the command line version and the Eclipse plugin version
are quite different to setup. The cli version uses batch files to set
the class path etc. I've been thinking if it wouldn't be possible to
create a complete Eclipse plugin setup for client, server daemon and
Eclipse Team integration. I think it is!

The client would be comprised of the Eclipse launcher and the following
plugins:
- org.eclipse.core.boot
- org.eclipse.core.runtime
- org.eclipse.core.resources (?)
- org.apache.xerces
- org.apache.log4j
- org.jdom
- org.eclipse.stellation.core
- org.eclipse.stellation.client (to be created)

The server daemon would be the following set of plugins:
- org.eclipse.core.boot
- org.eclipse.core.runtime
- org.eclipse.core.resources (?)
- org.apache.xerces
- org.apache.log4j
- org.jdom
- org.eclipse.stellation.core
- org.eclipse.stellation.server (to be created)

The full Team integration would add the following plugins to the
Eclipse distribution:
- org.eclipse.stellation.core
- org.eclipse.stellation.scm.model
- org.eclispe.stellation.scm.ui

In the above cases, the new client and server plugins will contain the
main Eclipse application to launch (implements IPlatformRunnable).
There already exists a launcher on every platform Eclipse exists for,
so we could get rid of the unix shell scrips. In the three scenario's I
was thinking of adding the RDBMS connection management plugins from the
ECLDBTool project(1).

Another benefit is that we only have to support one programming model:
the plugin model!

Comments?

Ringo

(1) http://sourceforge.net/projects/ecldbtool/


__________________________________________________
Do You Yahoo!?
Everything you'll ever need on one web page
from News and Sport to Email and Music Charts
http://uk.my.yahoo.com