geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Prasad Kashyap (JIRA)" <>
Subject [jira] Commented: (GERONIMO-2071) Move Geronimo build to M2 (new 1.2 trunk)
Date Tue, 06 Jun 2006 16:18:30 GMT
    [ ] 

Prasad Kashyap commented on GERONIMO-2071:

I cut my teeth on M2 migrating this plugin. It was also the first one to be migrated. So I
"migrated" the classes as is. But I don't believe we will have a need for that class. M2 provides
some form of resource filtering. So please prune this plugin and out it for vote. 

The site and test were stubs for future work. But let's remove that too for now. We should
revisit the sites for all plugins that we create  usage info and stuff.

> Move Geronimo build to M2 (new 1.2 trunk)
> -----------------------------------------
>          Key: GERONIMO-2071
>          URL:
>      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,, configs.log, configs.log, configs.patch,
configs.patch, deploy-tool.patch, deploy-tool.patch, deployment-plugin.patch, deployment-plugin.patch,
geronimo.patch, geronimo.patch, geronimo.patch, m2-plugins.patch, modules.patch, modules.patch,
mvn.log, openejb.log, openejb.patch, openejb.patch, openejb.patch, openejb.patch, openejb.patch,
openejb.patch, pom.xml, pom.xml
> A lot of work for moving Geronimo build to M2 was done under G-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:
For more information on JIRA, see:

View raw message