You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Hudson (Jira)" <ji...@apache.org> on 2022/06/18 15:20:00 UTC

[jira] [Commented] (MPLUGINTESTING-70) maven-compat requirement

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

Hudson commented on MPLUGINTESTING-70:
--------------------------------------

Build succeeded in Jenkins: Maven » Maven TLP » maven-plugin-testing » master #13

See https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-plugin-testing/job/master/13/

> maven-compat requirement
> ------------------------
>
>                 Key: MPLUGINTESTING-70
>                 URL: https://issues.apache.org/jira/browse/MPLUGINTESTING-70
>             Project: Maven Plugin Testing
>          Issue Type: Dependency upgrade
>            Reporter: Elliotte Rusty Harold
>            Assignee: Sylwester Lachiewicz
>            Priority: Major
>             Fix For: 3.4.0
>
>         Attachments: bug.tar.gz
>
>
> I'm attaching a sample project based on work by Ian Lavallee. Briefly it demos that one can only use AbstractMojoTestCase if the pom.xml also adds a dependency on org.apache.maven:maven-compat and org.apache.maven:maven-plugin-api. The former at least seems like it should not be required.
> Furthermore if either of these are required they should probably be at least runtime dependencies of maven-plugin-testing rather than requiring client projects to ad these dependencies explicitly. 
> Both of these are only required to run tests, not to compile the project. 



--
This message was sent by Atlassian Jira
(v8.20.7#820007)