[
https://issues.apache.org/jira/browse/ARCHETYPE-491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed ARCHETYPE-491.
------------------------------------
Resolution: Fixed
Fixed with
[50ec46b58af6084429622bc3bf645d5963f84634|https://git-wip-us.apache.org/repos/asf?p=maven-archetype.git;a=commit;h=50ec46b58af6084429622bc3bf645d5963f84634].
> 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)
