[
https://issues.apache.org/jira/browse/ARCHETYPE-491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15369875#comment-15369875
]
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_r70186177
--- Diff:
maven-archetype-plugin/src/it/build-archetype-and-run-its-with-existing-parent/src/test/resources/projects/basic/verify.groovy
---
@@ -0,0 +1 @@
+System.out.println(" Yeah Baby it rocks!")
--- End diff --
Please add trailing line break and change to proper English: "Yeah baby, it
rocks!"
> 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)
