maven-issues mailing list archives

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


ASF GitHub Bot commented on ARCHETYPE-491:

Github user michael-o commented on a diff in the pull request:
    --- Diff: maven-archetype-plugin/src/it/build-archetype-and-run-its-with-existing-parent/pom.xml
    @@ -0,0 +1,63 @@
    +<?xml version="1.0" encoding="UTF-8"?>
    +Licensed to the Apache Software Foundation (ASF) under one
    +or more contributor license agreements.  See the NOTICE file
    +distributed with this work for additional information
    +regarding copyright ownership.  The ASF licenses this file
    +to you under the Apache License, Version 2.0 (the
    +"License"); you may not use this file except in compliance
    +with the License.  You may obtain a copy of the License at
    +Unless required by applicable law or agreed to in writing,
    +software distributed under the License is distributed on an
    +KIND, either express or implied.  See the License for the
    +specific language governing permissions and limitations
    +under the License.
    +<project xmlns="" xmlns:xsi=""
    +  xsi:schemaLocation="">
    +  <modelVersion>4.0.0</modelVersion>
    +  <groupId>org.apache.maven.plugins.archetype.its</groupId>
    +  <artifactId>build-archetype-and-run-its-with-existing-parent</artifactId>
    +  <version>1.0-SNAPSHOT</version>
    +  <packaging>maven-archetype</packaging>
    +  <name>build-archetype-with-existing-parent</name>
    +  <description>packages an archetype then runs IT (archetype:integration-test)
within a Maven Project being created through another archetype</description>
    +  <build>
    +    <extensions>
    +      <extension>
    +        <groupId>org.apache.maven.archetype</groupId>
    +        <artifactId>archetype-packaging</artifactId>
    +        <version>@project.version@</version>
    +      </extension>
    +    </extensions>
    +    <pluginManagement>
    +      <plugins>
    +        <plugin>
    +          <artifactId>maven-archetype-plugin</artifactId>
    +          <version>@project.version@</version>
    +          <configuration>
    +            <settingsFile>${basedir}/test-settings.xml</settingsFile>
    +            <localRepositoryPath>${basedir}/target/local-repo</localRepositoryPath>
    --- End diff --
    Please use the appropriate property for `target` instead of `${basedir}/target`.

> Allow to run integration test with another archetype as parent project
> ----------------------------------------------------------------------
>                 Key: ARCHETYPE-491
>                 URL:
>             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

View raw message