geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Prasad Kashyap (JIRA)" <>
Subject [jira] Commented: (GERONIMO-1738) Plugin migration to Maven 2: geronimo-deployment-plugin
Date Fri, 10 Mar 2006 02:46:39 GMT
    [ ] 

Prasad Kashyap commented on GERONIMO-1738:

I believe that the m1 deployment plugin is only used by the itests in the openejb module.

The itests from Geronimo-1654 ( don't have
the openejb itests plugged into them yet. However, they use the new m2 deployment-plugin from
Geronimo-1650 (

Between the two below, what should the sequence of events be ?

1. If we don't worry about  existing openejb itests for now, then we can ditch the m1deployment
plugin all together. We can move to the m2 deployment-plugin in G-1650. We can move the itests
from the sandbox (G-1654) and write/migrate existing openejb itests to the new itests framework.

2. If we need to continue running existing openejb itests, then we should continue to support
the m1 deployment-plugin. Then the m2 deployment-plugin in G-1650 should be checked in a different

> Plugin migration to Maven 2: geronimo-deployment-plugin
> -------------------------------------------------------
>          Key: GERONIMO-1738
>          URL:
>      Project: Geronimo
>         Type: Sub-task
>   Components: buildsystem
>     Versions: 1.x
>     Reporter: Jacek Laskowski

> It's a task to keep track of the progress of the plugin build migration to Maven2

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