Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geronimo.apache.org
Message-ID: <19125615.1149217779784.JavaMail.jira@brutus>
Date: Fri, 2 Jun 2006 03:09:39 +0000 (GMT+00:00)
From: "Prasad Kashyap (JIRA)" <dev@geronimo.apache.org>
To: dev@geronimo.apache.org
Subject: [jira] Updated: (GERONIMO-2071) Move Geronimo build to M2 (new 1.2
 trunk)
In-Reply-To: <25328623.1149089494975.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

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

Prasad Kashyap updated GERONIMO-2071:
-------------------------------------

    Attachment: applications.patch.zip

The applications.patch does the following

1. in the geronimo/pom.xml, change dwrVersion to 1.1.1
2. consolidate all the individual application patches in the subtasks of http://issues.apache.org/jira/browse/GERONIMO-851.
3. consolidate and re-org console and magicGball apps.

The applications.patch does NOT do the following yet:
1. jsp precompile (http://jira.codehaus.org/browse/MJSPC-2)
2. jar classes dir to web-inf/lib/classes.jar (http://jira.codehaus.org/browse/MWAR-45)
3. migration of remote-deploy app. remote-deploy-lib app to be merged in 1.2


> Move Geronimo build to M2 (new 1.2 trunk)
> -----------------------------------------
>
>          Key: GERONIMO-2071
>          URL: http://issues.apache.org/jira/browse/GERONIMO-2071
>      Project: Geronimo
>         Type: New Feature
>     Security: public(Regular issues) 
>   Components: buildsystem
>     Versions: 1.2
>     Reporter: Prasad Kashyap
>     Assignee: Jacek Laskowski
>      Fix For: 1.2
>  Attachments: applications.patch.zip, deploy-tool.patch, geronimo.patch, geronimo.patch, geronimo.patch, openejb.patch, pom.xml
>
> A lot of work for moving Geronimo build to M2 was done under G-851. (http://issues.apache.org/jira/browse/GERONIMO-851) 
> The old trunk was renamed as dead-1.2. The new trunk was created from 1.1 and hence the migration work needs to be done here again. This JIRA will seek to consolidate the work that was done under G-851 and all it's subtasks. 
> The patch(es) here will be submitted under the RTC guidelines. Future patches for migration will have to be applied on top of this one. This patch will contain the parent pom, modules, openejb, configs, m2-plugins
> Any issues/concerns about migrating some pieces are well documented in G-851 with links to dev list archives.

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