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

Posted to issues@maven.apache.org by "Jason van Zyl (JIRA)" <ji...@codehaus.org> on 2007/01/09 19:51:21 UTC

[jira] Created: (MNG-2750) Remove the notion of pluginRepositories

Remove the notion of pluginRepositories
---------------------------------------

                 Key: MNG-2750
                 URL: http://jira.codehaus.org/browse/MNG-2750
             Project: Maven 2
          Issue Type: New Feature
          Components: Artifacts and Repositories
    Affects Versions: 2.0.4
            Reporter: Jason van Zyl
             Fix For: 2.1


I really don't think we need separate repositories for plugins. With the current behavior where dependencies are specified in plugins, they can only come from a plugin repository which is sort of useless. I think most people in practice just point their repository and pluginRepository settings at the same URL.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Commented: (MNG-2750) Remove the notion of pluginRepositories

Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.

    [ http://jira.codehaus.org/browse/MNG-2750?page=comments#action_84563 ] 
            
Brett Porter commented on MNG-2750:
-----------------------------------

This would be dependent on other features. It is currently quite useful for only grabbing snapshots of dependencies and not plugins. Greater control of how a repository is used would be needed first (and greater control over the versions of plugins you get).

I also think it might be better to go through a deprecation cycle. Deprecated in 2.1, removed in 2.2, etc.

Perhaps the best thing to do is retain the old functionality for POMs v4.0.0, and it will just not be available if you change your POM version to 4.1.0 to get Maven 2.1 features.

> Remove the notion of pluginRepositories
> ---------------------------------------
>
>                 Key: MNG-2750
>                 URL: http://jira.codehaus.org/browse/MNG-2750
>             Project: Maven 2
>          Issue Type: New Feature
>          Components: Artifacts and Repositories
>    Affects Versions: 2.0.4
>            Reporter: Jason van Zyl
>         Assigned To: Jason van Zyl
>             Fix For: 2.1
>
>
> I really don't think we need separate repositories for plugins. With the current behavior where dependencies are specified in plugins, they can only come from a plugin repository which is sort of useless. I think most people in practice just point their repository and pluginRepository settings at the same URL.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Updated: (MNG-2750) Remove the notion of pluginRepositories

Posted by "Jason van Zyl (JIRA)" <ji...@codehaus.org>.

     [ http://jira.codehaus.org/browse/MNG-2750?page=all ]

Jason van Zyl updated MNG-2750:
-------------------------------

    Fix Version/s: 2.1

> Remove the notion of pluginRepositories
> ---------------------------------------
>
>                 Key: MNG-2750
>                 URL: http://jira.codehaus.org/browse/MNG-2750
>             Project: Maven 2
>          Issue Type: New Feature
>          Components: Artifacts and Repositories
>    Affects Versions: 2.0.4
>            Reporter: Jason van Zyl
>         Assigned To: Jason van Zyl
>             Fix For: 2.1
>
>
> I really don't think we need separate repositories for plugins. With the current behavior where dependencies are specified in plugins, they can only come from a plugin repository which is sort of useless. I think most people in practice just point their repository and pluginRepository settings at the same URL.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Closed: (MNG-2750) Remove the notion of pluginRepositories

Posted by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org>.

     [ http://jira.codehaus.org/browse/MNG-2750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Benjamin Bentmann closed MNG-2750.
----------------------------------

       Resolution: Won't Fix
    Fix Version/s:     (was: 3.x)

> Remove the notion of pluginRepositories
> ---------------------------------------
>
>                 Key: MNG-2750
>                 URL: http://jira.codehaus.org/browse/MNG-2750
>             Project: Maven 2
>          Issue Type: New Feature
>          Components: Artifacts and Repositories
>    Affects Versions: 2.0.4
>            Reporter: Jason van Zyl
>            Assignee: Jason van Zyl
>
> I really don't think we need separate repositories for plugins. With the current behavior where dependencies are specified in plugins, they can only come from a plugin repository which is sort of useless. I think most people in practice just point their repository and pluginRepository settings at the same URL.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira