You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Michael Osipov (JIRA)" <ji...@apache.org> on 2016/07/10 18:11:11 UTC

[jira] [Assigned] (ARCHETYPE-491) Allow to run integration test with another archetype as parent project

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

Michael Osipov reassigned ARCHETYPE-491:
----------------------------------------

    Assignee: Michael Osipov

> 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)