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 Mon, 11 Jul 2016 23:43:11 GMT

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

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

Github user michael-o commented on the issue:

    https://github.com/apache/maven-archetype/pull/8
  
    I have found the issue on the line ending. Will elaborate later.


> 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