You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Michael Osipov (Jira)" <ji...@apache.org> on 2022/05/17 09:11:00 UTC
[jira] [Commented] (MSHARED-1074) Improvement performance of getMavenVersion in ForkedLauncher
[ https://issues.apache.org/jira/browse/MSHARED-1074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17538050#comment-17538050 ]
Michael Osipov commented on MSHARED-1074:
-----------------------------------------
The IT suite writes the Maven version to the console, this should be cached and reused.
> Improvement performance of getMavenVersion in ForkedLauncher
> ------------------------------------------------------------
>
> Key: MSHARED-1074
> URL: https://issues.apache.org/jira/browse/MSHARED-1074
> Project: Maven Shared Components
> Issue Type: Bug
> Components: maven-verifier
> Reporter: Slawomir Jaranowski
> Priority: Major
> Fix For: maven-verifier-next-release
>
>
> In method {{getMavenVersion}} in ForkedLauncher new Maven process is forked every time.
> We can cache output by Maven home or try to read from properties files in Maven home.
> There is also possibility to use Maven wrapper for executing - in this case we can read version form maven-wrapper.properties
--
This message was sent by Atlassian Jira
(v8.20.7#820007)