[jira] [Comment Edited] (MNG-4839) plugin dependencies not resolved form repositories

["Matt Parker (JIRA)" <ji...@apache.org>]

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

Matt Parker edited comment on MNG-4839 at 12/12/18 4:16 PM:
------------------------------------------------------------

Seems like how this works is too constrained. I'm having an issue with this right now. I'm using mycila's maven-license-plugin. As a feature, you can extend the plugin with custom property generators that can be used in license template or bundle your own license text in a third-party jar. Their plugin is deployed on a public maven server (central), and my plugin in deploy in our teams private repo. It cannot find the plugin since it doesn't live on central. If I list it as a repo in my pom file, the plugin should be able to use it. Is there another workaround other than downloading and rebranding their plugin and storing it in my private repo?

I got this to work by defining a pluginRepository pointing to my release repo, which is entirely redundant since the release repo is defined as a repository element. 


was (Author: parker20121):
Seems like how this works is too constrained. I'm having an issue with this right now. I'm using mycila's maven-license-plugin. As a feature, you can extend the plugin with custom property generators that can be used in license template or bundle your own license text in a third-party jar. Their plugin is deployed on a public maven server (central), and my plugin in deploy in our teams private repo. It cannot find the plugin since it doesn't live on central. If I list it as a repo in my pom file, the plugin should be able to use it. Is there another workaround other than downloading and rebranding their plugin and storing it in my private repo?

> plugin dependencies not resolved form repositories
> --------------------------------------------------
>
>                 Key: MNG-4839
>                 URL: https://issues.apache.org/jira/browse/MNG-4839
>             Project: Maven
>          Issue Type: Bug
>    Affects Versions: 3.0-beta-1, 3.0-beta-3
>         Environment: Apache Maven 3.0-RC3 (r1001464; 2010-09-26 18:14:28+0200)
> Java version: 1.6.0_21
> OS name: "windows 7" version: "6.1" arch: "amd64" Family: "windows"
>            Reporter: Michael Brackx
>            Assignee: Benjamin Bentmann
>            Priority: Major
>         Attachments: pom.xml
>
>
> plugin dependencies are not resolved from repositories in <repositories>
> regression from 2.2.1
> the [wiki|https://cwiki.apache.org/MAVEN/maven-3x-compatibility-notes.html#Maven3.xCompatibilityNotes-PluginRepositories] mentions
> "For clarity, this rule only applies to the resolution of the root artifact. In other words, while a plugin is only resolved from a <pluginRepository>, the dependencies of the plugin are resolved from the original <pluginRepository> and any <repositories> specified in the plugin's POM."
> example pom is attached
> error:
> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-antrun-plugin:1.3:run (process-classes) on project bug: Execution process-classes of goal org.apache.maven.plugins:maven-antrun-plugin:1.3:run failed: Plugin org.apache.maven.plugins:maven-antrun-plugin:1.3 or one of its dependencies could not be resolved: Could not find artifact org.hibernate:hibernate-tools:jar:3.2.4.GA in central (http://repo1.maven.org/maven2) -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please read the following articles:
> [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/PluginResolutionException



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