maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James Z.M. Gao (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MNG-6327) Add ability to easily retrieve core extensions from alternative pluginRepository
Date Thu, 12 Apr 2018 08:29:00 GMT

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

James Z.M. Gao commented on MNG-6327:
-------------------------------------

[~zebbedi], MNG-6392 should be a solution for this issue, put the pluginRepository in a
profile in the new project settings and check in the git source.

> Add ability to easily retrieve core extensions from alternative pluginRepository
> --------------------------------------------------------------------------------
>
>                 Key: MNG-6327
>                 URL: https://issues.apache.org/jira/browse/MNG-6327
>             Project: Maven
>          Issue Type: Improvement
>          Components: Bootstrap &amp; Build
>    Affects Versions: 3.5.2
>            Reporter: Matt Biggs
>            Priority: Critical
>
> If you define an extension in *.mvn/extensions.xml* it is automatically retrieved and
installed when you first build but ONLY if it is present in maven central. 
> I understand it's obviously a little 'chicken and egg' scenario but it would be really
useful for making a seamless out of the box experience if it could either a) read the pom
and use the pluginRepositories from there, or b) if you could perhaps specify the repository
inside the extensions.xml file?
> The only work around I can currently find is to ask the user to add an active profile
to their settings.xml which obviously isn't as nice. 



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

Mime
View raw message