Merlin studio migration?

Peter Neubauer peter at neubauer.se
Mon Apr 11 18:14:50 EDT 2005


Hi gang,
On Saturday 09 April 2005 02:25, Peter Neubauer wrote:
> Hi Broc,
>
> my first plan would be something like:
>
> 1)Everyone try to mount all the eclipse plugins:
> -org.apache.avalon.ide.eclipse.core
> -org.apache.avalon.ide.eclipse.launch
> -org.apache.avalon.ide.eclipse.ui
> -org.apache.avalon.ide.eclipse.repository
> -magic (working with new Magic)
>
> 2) examine what they do by starting eclipse in PDE-debug mode and start
> looking through the Merlin Wizards, perspectives, builders and whatnot
>
Got the stuff working, at least to the point where I can make a new component 
via the wizards. It looks really good I think. There are just some questions 
that come to mind:
- since metadata is out with Metro-Freighttrain and ContextIoC is in, should 
we support Merlin style javadoc stuff anymore?
- I feel that since everything moves into plain java and the heaven of 
typesafeness, we should concentrate on repository/transit stuff, building 
support/ant task completion and index/component definition manipulation
> 3) start a discussion on what of that we really need
>
see above
> 4) get the plugins to build with magic (will be a nice use of transit since
> we have some artifact naming challenges here)
>
Cameron and me are starting to think about that. Basically, we envision having 
a spell that converts a eclipse plugin.xml:
<?xml version="1.0" encoding="UTF-8"?>
<?eclipse version="3.0"?>
<plugin
   id="net.dpml.ide.eclipse.plugins.Magic"
   name="Eclipse Magic Plug-in"
   version="0.1.91"
   provider-name="DPML" 
   class="net.dpml.ide.eclipse.plugins.magic.MagicPlugin">
   <runtime>
      <library name="lib/dpml-transit-tools.jar">
         <export name="*"/>
      </library>
  </runtime>
   <requires>
      <import plugin="org.eclipse.ui"/>
   </requires>
</plugin>
Into a module.xml that lists the exported libraries as resources, and the 
dependencies as module imports. The concepts between module.xml and 
plugin.xml seem similar, so I think besides the naming conventions that could 
work. So if you want to use the eclipse plugin in magic you would do 
something in your index.xml like

<x:import artifact:plugin:eclipse/org.eclipse.core#3.1/>

and then you could use the exported libs by including a virtual resource that 
has dependecies to all of them, like

    <dependencies>
      <include key="org.eclipse.core"/>

We are not sure whether we will need special EclipseResolver but we will see 
as we go.

Btw, is it possible to define an artifact URI directly as a resource? I'm 
thinking of something like

<resource key=org.eclipse.core-test>
<uri>artifact:jar:eclipse/plugins/org.eclipse.core/test#3.1</uri>
</resource>
and that artifact uril would refer to
cache/eclipse/org.eclipse.core-3.1/test.jar via the EclipseResolver.

Any thoughts on that?

/peter



More information about the dev-dpml mailing list