geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Prasad Kashyap (JIRA)" <...@geronimo.apache.org>
Subject [jira] Commented: (GERONIMO-1738) Plugin migration to Maven 2: geronimo-deployment-plugin
Date Fri, 10 Mar 2006 15:17:40 GMT
    [ http://issues.apache.org/jira/browse/GERONIMO-1738?page=comments#action_12369871 ] 

Prasad Kashyap commented on GERONIMO-1738:
------------------------------------------

OK. So, if you like the 2nd option better, then we can use the deployment-plugin.zip submittted
in G-1650 here. It has all the goals of the m1 deployment-plugin except for the "unpackServer".
 That functionality is now provided by 2 maven plugins - maven-assembly-plugin and dependency-maven-plugin.


The deployment-plugin.zip submitted in G-1650 is the migration to m2 piece of the m1 plugin.


Here's an idea. We check in the m2-deployment-plugin from G-1650 in the same dir as the current
deployment-plugin. Since the groupIds are different anyway, (geronimo in m1 and org.apache.geronimo
in m2), they will be different locations in the repo anyway. 

We just have to ensure the the following -
1. the right source files gets built depending on m1 or m2 build.
2. jars that gets packaged have a unique name.

The current m1 directory structure is src.java.org.apache.geronimo.deployment.mavenplugin
The new m2 directory structure is      src.main.java.org.apache.geronimo.plugins.deployment

This is what I had wanted to talk to you about   :-) Handling the itests and deployment-plugin
.

> Plugin migration to Maven 2: geronimo-deployment-plugin
> -------------------------------------------------------
>
>          Key: GERONIMO-1738
>          URL: http://issues.apache.org/jira/browse/GERONIMO-1738
>      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:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message