I did a similar thing for work here, but did not use Eclipse; a suite of applications hosted by a very light-weight platform that provides a single extension point for adding applications. The platform discovers applications (a la plugins) in the classpath and adds it to the platform.
I suppose you are trying to use eclipse's discovery mechanism and HiveMind's injection and interception features? Do you want to share components between plugins? That may be a problem. What is your motive in using eclipse? SWT? -Harish On Tue, 8 Mar 2005 12:33:21 +0100, Knut Wannheden <[EMAIL PROTECTED]> wrote: > Hi all, > > I don't know if this sounds a little bit odd, but I'd like to run a > HiveMind application inside Eclipse. As the application is split into > multiple modules, of which not always all will be used, I thought it > would be natural to map every module to an Eclipse plugin. > > Without thinking further about it I did just that. Of course I ran > into problems: HiveMind doesn't find the module descriptors as I think > the Eclipse plugins are all loaded by a separate class loaders. > > Before trying to implement a solution to this I was wondering if > anybody else had done something like this before. > > I think it should be quite easy to support HiveMind applications > inside Eclipse. I'd have to create a HiveMind plugin which exposes a > extension point for registering HiveMind modules in other plugins. > This should let HiveMind (using a custom ModuleDescriptorProvider) > construct the registry. Are there problems with this approach or can > someone think of a better idea? > > Cheers, > > --knut > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
