[
https://issues.apache.org/jira/browse/MINVOKER-123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17958336#comment-17958336
]
Olivier Lamy commented on MINVOKER-123:
---------------------------------------
This project has moved from Jira to GitHub Issues. This issue was migrated to
[apache/maven-invoker-plugin#393|https://github.com/apache/maven-invoker-plugin/issues/393].
> Use different Maven versions for running the current build and the
> integration tests
> ------------------------------------------------------------------------------------
>
> Key: MINVOKER-123
> URL: https://issues.apache.org/jira/browse/MINVOKER-123
> Project: Maven Invoker Plugin (Moved to GitHub Issues)
> Issue Type: New Feature
> Affects Versions: 1.5
> Environment: all
> Reporter: Karl Heinz Marbaise
> Priority: Major
>
> I'm currently faced with the problem that my build (appassembler-plugin) can
> be done via Maven 3.0.X and Maven 2.2.1 but not with Maven 2.0.11. But on the
> other hand the appassembler-plugin itself can be used in Maven 2.0.11 or be
> more accurate that i would like to test this via the integration tests.
> So currently i don't see a possibility to run my build of the plugin via
> Maven 3.0.3 and let the integration-tests run with a different Maven version
> (or may be oversight something?)...for example with Maven 2.2.1 or Maven
> 2.0.11.
> So it would be very handy to have the possibility to use a different Maven
> version for running inside the integration tests than for the build itself.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
