You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Joe Bohn (JIRA)" <de...@geronimo.apache.org> on 2006/06/10 21:05:30 UTC

[jira] Updated: (GERONIMO-2106) Document the modules included in each assembly on our Wiki

     [ http://issues.apache.org/jira/browse/GERONIMO-2106?page=all ]

Joe Bohn updated GERONIMO-2106:
-------------------------------

    Attachment: Geronimo1.1-Config-20060512.ppt

I don't know why we need a JIRA for this activity ... but here is a powerpoint document that I had created earlier which not only shows the different configurations (what is in litte-G vs. big-G) ... but also shows the parent dependencies used to create the classloaders.

> Document the modules included in each assembly on our Wiki
> ----------------------------------------------------------
>
>          Key: GERONIMO-2106
>          URL: http://issues.apache.org/jira/browse/GERONIMO-2106
>      Project: Geronimo
>         Type: Task
>     Security: public(Regular issues) 
>   Components: documentation
>     Versions: 1.1
>     Reporter: Donald Woods
>     Assignee: Donald Woods
>     Priority: Trivial
>      Fix For: 1.1
>  Attachments: Geronimo1.1-Config-20060512.ppt
>
> Info needed inorder to enable upgrades from minimal-server to j2ee-server -
> If you get a chance, could you look at project.xml for the J2EE
> assemblies vs. the minimal assemblies and make a list of all the
> Geronimo modules in the two?  Such as:
> module  J2EE  minimal
> system  yes  yes
> unavailable-webservices-deployer  no  yes
> ...
> We can use a list like that to create the plugin metadata to upgrade
> minimal to full J2EE.
> Thanks,
>    Aaron 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira