maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ARCHETYPE-491) Allow to run integration test with another archetype as parent project
Date Sun, 10 Jul 2016 18:20:11 GMT

    [ https://issues.apache.org/jira/browse/ARCHETYPE-491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15369883#comment-15369883
] 

ASF GitHub Bot commented on ARCHETYPE-491:
------------------------------------------

Github user michael-o commented on a diff in the pull request:

    https://github.com/apache/maven-archetype/pull/8#discussion_r70186237
  
    --- Diff: maven-archetype-plugin/src/main/java/org/apache/maven/archetype/mojos/IntegrationTestMojo.java
---
    @@ -84,6 +90,43 @@
      * the IT.</li>
      * </ul>
      * <p/>
    + * To let the IT create a Maven module below some other Maven project (being generated
from another archetype)
    + * one can additionally specify an optional <code>archetype.pom.properties</code>
file in the parent directory,
    + * specifying the archetype's <code>groupId</code>, <code>artifactId</code>
and <code>version</code> along with its 
    + * <code>archetype.properties</code> file, containing properties for project
generation. Both files are leveraged
    + * to create the parent project for this IT. Parent projects can be nested.
    + * An example structure for such an integration test looks like this
    + * <table>
    + * <tr>
    + * <th>File/Folder</code></td>
    + * <th>Description</td>
    + * </tr>
    + * <tr>
    + * <td><code>src/test/resources/projects/it1</code></td>
    + * <td>Folder for integration test 1</td>
    + * </tr>
    + * <tr>
    + * <td><code>src/test/resources/projects/it1/archetype.pom.properties</code></td>
    + * <td>GAV for the archetype from which to generate the parent</td>
    + * </tr>
    + * <tr>
    + * <td><code>src/test/resources/projects/it1/archetype.properties</code></td>
    + * <td>All required properties for the archetype being specified by <code>archetype.pom.properties</code>
on this level</td>
    + * </tr>
    + * <tr>
    + * <td><code>src/test/resources/projects/it1/child</code></td>
    + * <td>Folder for maven module within integration test 1 (this folder's name is
not relevant)</td>
    --- End diff --
    
    ditto


> Allow to run integration test with another archetype as parent project
> ----------------------------------------------------------------------
>
>                 Key: ARCHETYPE-491
>                 URL: https://issues.apache.org/jira/browse/ARCHETYPE-491
>             Project: Maven Archetype
>          Issue Type: Improvement
>          Components: Plugin
>    Affects Versions: 2.4
>            Reporter: Konrad Windszus
>            Assignee: Michael Osipov
>             Fix For: 2.5
>
>
> Archetypes can be either used as module archetypes (below existing Maven projects, then
the parent will be automatically set) or as regular project archetypes (i.e. will run standalone,
because they need no parent or have a parent hardcoded in their pom). Currently only the latter
is properly supported for the goal {{integration-test}}.
> To also support the former it would be good to allow the setup of arbitrary parent structures
(from other archetypes) below which the actual IT should be executed.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message