jira-importer

**[qxo](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=qxo)** commented ref PR: https://github.com/apache/maven-archetype/pull/130

**[Peter De Maeyer](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=peterdm)** commented It's on my to-do list to fix this, but if someone wants to beat me to it, knock yourself out.

**[Hervé Boutemy](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=hboutemy)** commented nice catch: looks like this IT should be defined as a setup IT = the normal way to show its special role setting relativePath is a good...

**[Peter De Maeyer](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=peterdm)** commented > this IT should be defined as a setup IT I don't know how to do that, I'm not so familiar with the `maven-invoker-plugin`. I'll need...

**[Robert Scholte](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=rfscholte)** commented This is a general issue with the maven-invoker-plugin. We should fix it there so other plugins can benefit from it as well.

**[Hervé Boutemy](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=hboutemy)** commented what do you want to fix "here so other plugins can benefit from it as well"? There is a default value for setup ITs https://maven.apache.org/plugins/maven-invoker-plugin/integration-test-mojo.html#setupIncludes , it...

**[Hervé Boutemy](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=hboutemy)** commented after writing, I just saw that the convention is followed and works when ITs are not run in isolation (and I'm happy about setup jobs display enhancement...

**[Mark Struberg](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=struberg)** commented I've documented the proper usage over at MASSEMBLY-919. You just have to add that other setup IT as well. e.g. ``` mvn verify -Dinvoker.test=it-project-parent,projects/bugs/massembly-919 -Prun-its ```

**[Peter De Maeyer](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=peterdm)** commented That feels like a workaround and no real solution to me. The downside of that is that you require everyone who wants to run an IT...

**[Hervé Boutemy](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=hboutemy)** commented > needs to "know" about a parent project that the IT project itself has no relation with notice that by convention, these setup jobs are named "setup*",...