Very cool example of what can be done with plugins.... :-)

Can we use G2099 to start creating a new subproject space for ASL 2.0 based Samples and Plugins in SVN? Something that fits into the normal Maven model of -
  /geronimo
    /samples
      /trunk
        /modules - dir would contain sample app dirs like magicgball
/plugins - dir would contain config/plugin dirs for samples and other external ASL apps like DirectoryServer and JetSpeed2

Maybe we can start by creating the structure in Sandbox and then vote to move it over when everything is building?


-Donald


Aaron Mulder (JIRA) wrote:
     [ http://issues.apache.org/jira/browse/GERONIMO-2099?page=all ]

Aaron Mulder updated GERONIMO-2099:
-----------------------------------

Description: Here's the "code" used to create the console TranQL/Oracle XA plugin. I'm not sure where it should go, perhaps we should create geronimo/plugins/(category)/(plugin)/trunk... in SVN

It's a little cheesy in that it uses a couple class files from the console, but 
it seems like we need to move those classes out of the console WAR in order to 
refer to them from a child module classpath.

  was:Here's the code used to create the console TranQL/Oracle XA plugin.  I'm 
not sure where it should go, perhaps we should create geronimo/plugins/...



Source for Console Oracle XA plugin
-----------------------------------

        Key: GERONIMO-2099
        URL: http://issues.apache.org/jira/browse/GERONIMO-2099
    Project: Geronimo
       Type: New Feature
Security: public(Regular issues) Components: Plugins
   Versions: 1.1
   Reporter: Aaron Mulder
Attachments: console-tranql-oracle-xa-plugin.zip

Here's the "code" used to create the console TranQL/Oracle XA plugin.  I'm not 
sure where it should go, perhaps we should create 
geronimo/plugins/(category)/(plugin)/trunk... in SVN
It's a little cheesy in that it uses a couple class files from the console, but 
it seems like we need to move those classes out of the console WAR in order to 
refer to them from a child module classpath.


Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

Reply via email to