You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "Milos Kleint (JIRA)" <ji...@codehaus.org> on 2005/03/12 10:41:31 UTC

[jira] Created: (MAVEN-1578) if plugin has dependencies, the plugin props should be consulted for remote repositories to check.

if plugin has dependencies, the plugin props should be consulted for remote repositories to check.
--------------------------------------------------------------------------------------------------

         Key: MAVEN-1578
         URL: http://jira.codehaus.org/browse/MAVEN-1578
     Project: maven
        Type: Bug
  Components: plugin manager  
    Versions: 1.0.2    
 Environment: maven 1.0.2, mandrake linux 10.1
    Reporter: Milos Kleint


I have a plugin for creating Netbeans module artifacts (http://mevenide.codehaus.org/maven-nbm-plugin), the plugin is uploaded to ibiblio.
However, internally it uses Netbeans.org custom ant tasks to create the artifacts. I don't want to upload that to the central repository (it's not my jar, I just use it - in the case they come after me or release it on their own to ibiblio, it's easy to get rid of)
So I've put the artifact in my custom remote repository http://mevenide.codehaus.org/repository
The idea was that when specifying the maven.repo.remote in the plugin's project properties, it would download it from the correct place. However that's not happening, and one has to define that custom remote repository in every project that wants to use the plugin. That's unfortunate.

-- 
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
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org


[jira] Commented: (MNG-400) if plugin has dependencies, the plugin props should be consulted for remote repositories to check.

Posted by "Milos Kleint (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/MNG-400?page=comments#action_42786 ] 

Milos Kleint commented on MNG-400:
----------------------------------

for m1: would it be possible to use the user's defined repositories + then the one defined in plugin (only in case it's not already downloaded)


> if plugin has dependencies, the plugin props should be consulted for remote repositories to check.
> --------------------------------------------------------------------------------------------------
>
>          Key: MNG-400
>          URL: http://jira.codehaus.org/browse/MNG-400
>      Project: Maven 2
>         Type: Improvement
>   Components: maven-core
>  Environment: maven 1.0.2, mandrake linux 10.1
>     Reporter: Milos Kleint

>
>
> I have a plugin for creating Netbeans module artifacts (http://mevenide.codehaus.org/maven-nbm-plugin), the plugin is uploaded to ibiblio.
> However, internally it uses Netbeans.org custom ant tasks to create the artifacts. I don't want to upload that to the central repository (it's not my jar, I just use it - in the case they come after me or release it on their own to ibiblio, it's easy to get rid of)
> So I've put the artifact in my custom remote repository http://mevenide.codehaus.org/repository
> The idea was that when specifying the maven.repo.remote in the plugin's project properties, it would download it from the correct place. However that's not happening, and one has to define that custom remote repository in every project that wants to use the plugin. That's unfortunate.

-- 
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


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org


[jira] Commented: (MNG-400) if plugin has dependencies, the plugin props should be consulted for remote repositories to check.

Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MNG-400?page=comments#action_39118 ]
     
Brett Porter commented on MNG-400:
----------------------------------

this would have nasty side effects in m1 of never allowing you to override the repository correctly, I believe.

Possible in m2, but we need to add the repositories to the plugin descriptor.

> if plugin has dependencies, the plugin props should be consulted for remote repositories to check.
> --------------------------------------------------------------------------------------------------
>
>          Key: MNG-400
>          URL: http://jira.codehaus.org/browse/MNG-400
>      Project: m2
>         Type: Improvement
>   Components: maven-core
>  Environment: maven 1.0.2, mandrake linux 10.1
>     Reporter: Milos Kleint
>      Fix For: 2.0-beta-1

>
>
> I have a plugin for creating Netbeans module artifacts (http://mevenide.codehaus.org/maven-nbm-plugin), the plugin is uploaded to ibiblio.
> However, internally it uses Netbeans.org custom ant tasks to create the artifacts. I don't want to upload that to the central repository (it's not my jar, I just use it - in the case they come after me or release it on their own to ibiblio, it's easy to get rid of)
> So I've put the artifact in my custom remote repository http://mevenide.codehaus.org/repository
> The idea was that when specifying the maven.repo.remote in the plugin's project properties, it would download it from the correct place. However that's not happening, and one has to define that custom remote repository in every project that wants to use the plugin. That's unfortunate.

-- 
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


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org


[jira] Closed: (MNG-400) if plugin has dependencies, the plugin props should be consulted for remote repositories to check.

Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MNG-400?page=all ]
     
Brett Porter closed MNG-400:
----------------------------

     Resolution: Won't Fix
    Fix Version:     (was: 2.0-beta-1)

plugins should already do this

> if plugin has dependencies, the plugin props should be consulted for remote repositories to check.
> --------------------------------------------------------------------------------------------------
>
>          Key: MNG-400
>          URL: http://jira.codehaus.org/browse/MNG-400
>      Project: Maven 2
>         Type: Improvement
>   Components: maven-core
>  Environment: maven 1.0.2, mandrake linux 10.1
>     Reporter: Milos Kleint

>
>
> I have a plugin for creating Netbeans module artifacts (http://mevenide.codehaus.org/maven-nbm-plugin), the plugin is uploaded to ibiblio.
> However, internally it uses Netbeans.org custom ant tasks to create the artifacts. I don't want to upload that to the central repository (it's not my jar, I just use it - in the case they come after me or release it on their own to ibiblio, it's easy to get rid of)
> So I've put the artifact in my custom remote repository http://mevenide.codehaus.org/repository
> The idea was that when specifying the maven.repo.remote in the plugin's project properties, it would download it from the correct place. However that's not happening, and one has to define that custom remote repository in every project that wants to use the plugin. That's unfortunate.

-- 
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


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org