[
https://issues.apache.org/jira/browse/MSHARED-20?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sylwester Lachiewicz updated MSHARED-20:
----------------------------------------
Description: We are happily maintaining (at least) two code bases to fork
Maven: One in the maven-invoker ({{Invoker}} and {{DefaultInvoker}}) and one in
the _org.apache.maven.release:maven-release-manager_ ({{MavenExecutor}} and
{{ForkedMavenExecutor}}). Some far day in the future we might want to
consolidate this stuff into a single component. (was: We are happily
maintaining (at least) two code bases to fork Maven: One in the maven-invoker
({{Invoker}} and {{DefaultInvoker}}) and one in the maven-release-manager
({{MavenExecutor}} and {{ForkedMavenExecutor}}). Some far day in the future we
might want to consolidate this stuff into a single component.)
> Extend Invoker API to support the needs of the Release Plugin
> -------------------------------------------------------------
>
> Key: MSHARED-20
> URL: https://issues.apache.org/jira/browse/MSHARED-20
> Project: Maven Shared Components
> Issue Type: New Feature
> Components: maven-invoker
> Reporter: Benjamin Bentmann
> Priority: Major
>
> We are happily maintaining (at least) two code bases to fork Maven: One in
> the maven-invoker ({{Invoker}} and {{DefaultInvoker}}) and one in the
> _org.apache.maven.release:maven-release-manager_ ({{MavenExecutor}} and
> {{ForkedMavenExecutor}}). Some far day in the future we might want to
> consolidate this stuff into a single component.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
