You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Hervé Boutemy (JIRA)" <ji...@apache.org> on 2018/04/02 14:40:00 UTC

[jira] [Closed] (MARCHETYPES-51) add plugin testing harness to maven-archetype-plugin

     [ https://issues.apache.org/jira/browse/MARCHETYPES-51?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Hervé Boutemy closed MARCHETYPES-51.
------------------------------------
    Resolution: Fixed
      Assignee: Hervé Boutemy

ok, we'll see later for maven-compat dependency removal

> add plugin testing harness to maven-archetype-plugin
> ----------------------------------------------------
>
>                 Key: MARCHETYPES-51
>                 URL: https://issues.apache.org/jira/browse/MARCHETYPES-51
>             Project: Maven Archetype Bundles
>          Issue Type: Dependency upgrade
>          Components: Maven Plugin Archetype
>    Affects Versions: maven-archetype-plugin-1.3
>         Environment: macOS High Sierra
>            Reporter: Nick Lombard
>            Assignee: Hervé Boutemy
>            Priority: Major
>             Fix For: 1.3
>
>         Attachments: MARCHETYPES-51.patch
>
>
> I want to update the plugin archetype (for creating new plugins not to be confused with the archetype plugin) to also include a testing harness unit test example alongside the currently supplied integration test example.
> Once completed the documentation can then be updated to reflect the new starting point. The documentation currently under Plugin Developers Centre should also be merged with Cookbook: How To Use Maven Plugin Testing Harness? But lets start with updating the archetype and take it from there. 
> Please let me know if there you have any problem with me working on this or if there are any special requirements you would like to see addressed. 
> I am going with the assumption that http://svn.apache.org/viewvc/maven/archetypes is the correct repository to patch against because this repo has not been migrated to git as yet. Please correct me if I am wrong.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)