[
https://issues.apache.org/jira/browse/SUREFIRE-1957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17443490#comment-17443490
]
Tibor Digana edited comment on SUREFIRE-1957 at 11/14/21, 11:34 PM:
--------------------------------------------------------------------
[~slawekjaranowski]
So it would be worth to use API 3.1 with *sisu-maven-plugin*, then [your
PR|https://github.com/apache/maven-surefire/pull/393], and then j8.
This would avoid changing the metadata twice.
We are using 3.1 already as the recommended version for the user in the
documentation.
Finally, it would be great to use lambdas because we use one-method interfaces,
as in _ForkClient.java_. I think there's a plugin which helps migrating the
code to j8 automatically but still the developer has to check it. The
conditions with opt j8 can be avoided in our ITs.
was (Author: tibor17):
[~slawekjaranowski]
So it would be worth to use API 3.1 with *sisu-maven-plugin*, then [your
PR|https://github.com/apache/maven-surefire/pull/393], and then j8.
This would avoid changing the metadata twice.
We are using 3.1 already as the recommended version for the user in the
documentation.
Finally, it would be great to use lambdas because we use one-method interfaces,
as in _ForkClient.java_. I think there's a plugin which helps migrating the
code to j8 automatically but still the developer has to check it.
> Get rid of maven-artifact-transfer
> ----------------------------------
>
> Key: SUREFIRE-1957
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1957
> Project: Maven Surefire
> Issue Type: Improvement
> Reporter: Slawomir Jaranowski
> Assignee: Tibor Digana
> Priority: Major
> Fix For: 3.0.0-M6
>
>
> It looks like is used only in
> {{org.apache.maven.plugin.surefire.SurefireDependencyResolver}}
>
> Allows migration to Maven 3.1+
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
