You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "Geoffrey (JIRA)" <ji...@codehaus.org> on 2005/12/22 09:31:11 UTC

[jira] Created: (MNG-1887) Guide to transforming a maven.xml goal into a plugin

Guide to transforming a maven.xml goal into a plugin
----------------------------------------------------

         Key: MNG-1887
         URL: http://jira.codehaus.org/browse/MNG-1887
     Project: Maven 2
        Type: New Feature

  Components: documentation - guides  
    Versions: 2.0.1    
    Reporter: Geoffrey


Many users coming from maven 1 have large maven.xml files and don't really know how to start migrating those.
Usually these maven.xml do simple things like copy some files or run an ant task.

3 use cases should be shown:
1) old custom assembly script can now be done by the assembly plugin
2) some ant task can be done with the antrun plugin
3) some custom script can be turned into a plugin
You probably don't like solution 2) and it's indeed not the best solution,
like use maven.xml in maven 1 was also not the best solution,
despite that people are doing it to do things quick & dirty or as proofs of concepts,
so they should be guided (and also be told that 3) is better)

This could become a part of "Guide to Moving from Maven 1.x to Maven 2.x":
http://maven.apache.org/guides/mini/guide-m1-m2.html
But seeing the length of that one, some sort of index would be usefull (like in FAQ's).

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org


[jira] Updated: (MNG-1887) Guide to transforming a maven.xml goal into a plugin

Posted by "John Casey (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MNG-1887?page=all ]

John Casey updated MNG-1887:
----------------------------

    Fix Version: documentation

> Guide to transforming a maven.xml goal into a plugin
> ----------------------------------------------------
>
>          Key: MNG-1887
>          URL: http://jira.codehaus.org/browse/MNG-1887
>      Project: Maven 2
>         Type: New Feature

>   Components: documentation - guides
>     Versions: 2.0.1
>     Reporter: Geoffrey De Smet
>      Fix For: documentation

>
>
> Many users coming from maven 1 have large maven.xml files and don't really know how to start migrating those.
> Usually these maven.xml do simple things like copy some files or run an ant task.
> 3 use cases should be shown:
> 1) old custom assembly script can now be done by the assembly plugin
> 2) some ant task can be done with the antrun plugin
> 3) some custom script can be turned into a plugin
> You probably don't like solution 2) and it's indeed not the best solution,
> like use maven.xml in maven 1 was also not the best solution,
> despite that people are doing it to do things quick & dirty or as proofs of concepts,
> so they should be guided (and also be told that 3) is better)
> This could become a part of "Guide to Moving from Maven 1.x to Maven 2.x":
> http://maven.apache.org/guides/mini/guide-m1-m2.html
> But seeing the length of that one, some sort of index would be usefull (like in FAQ's).

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org