[jira] Updated: (GERONIMO-2067) Configs migration to M2

["Anita Kulshreshtha (JIRA)" <de...@geronimo.apache.org>]

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

Anita Kulshreshtha updated GERONIMO-2067:
-----------------------------------------

    Attachment: applications.patch
                configs.patch
                configs.log

 --    Geronimo must use openejb 2.2. A new openejb trunk was created. As a result configs\client and client-deployer changed. This patch adds interceptor to the dependency list. see
       http://issues.apache.org/jira/browse/GERONIMO-2152
 --    As pointed out by David Jencks the axis configurations do not need openejb, removed dependency on openejb.
   Here is the list of patches to be applied - 
1. m2-plugins.patch (attached earlier)
2. configs.patch 
3. configs.log - results for rev. 418587
4. etc.patch - attached earlier 
5. applications.patch -  same as before, refreshed for rev 418587
Todo - The applications\console did not compile today. Hence did not build console-* configs. 


> Configs migration to M2
> -----------------------
>
>          Key: GERONIMO-2067
>          URL: http://issues.apache.org/jira/browse/GERONIMO-2067
>      Project: Geronimo
>         Type: Sub-task
>     Security: public(Regular issues) 
>   Components: buildsystem
>     Versions: 1.2
>  Environment: All
>     Reporter: Anita Kulshreshtha
>     Assignee: Anita Kulshreshtha
>      Fix For: 1.2
>  Attachments: applications.patch, applications.patch, configs.log, configs.log, configs.log, configs.log, configs.patch, configs.patch, configs.patch, configs.patch, configs.patch, configs.patch, configs.patch, etc.patch, m2-plugins.patch, modules.patch, modules.patch, modules.patch, newconfigs.patch, pom.patch, pom.patch, pom.patch
>
> To build these configurations use packaging plugin GERONIMO-1740. This patch builds non openejb and non jetty configurations. 
> This patch is for the new trunk, and has been edited using emcas to rempve ^M.

-- 
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