You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "Robert Scholte (JIRA)" <ji...@apache.org> on 2018/04/04 16:44:00 UTC

[jira] [Commented] (MNG-6389) Move the toolchains model to a separate artifactId

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

Robert Scholte commented on MNG-6389:
-------------------------------------

There used to be a separate [maven-toolchain|http://search.maven.org/#search%7Cgav%7C1%7Cg%3A%22org.apache.maven%22%20AND%20a%3A%22maven-toolchain%22] artifact, don't know why it was dropped. I agree that it makes sense to have a separate artifact for the toolchain model.

> Move the toolchains model to a separate artifactId
> --------------------------------------------------
>
>                 Key: MNG-6389
>                 URL: https://issues.apache.org/jira/browse/MNG-6389
>             Project: Maven
>          Issue Type: Improvement
>          Components: Toolchains
>    Affects Versions: 3.5.3
>            Reporter: George Gastaldi
>            Priority: Major
>
> Just as maven-model and maven-settings, it would be nice to have a maven-toolchains artifactId containing only the model. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)