Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Dependency Resolution Error #50

Open
rutherfordjw opened this issue Aug 7, 2014 · 4 comments
Open

Dependency Resolution Error #50

rutherfordjw opened this issue Aug 7, 2014 · 4 comments

Comments

@rutherfordjw
Copy link

Dependencies are being explicitly downloaded from Maven Central instead of specified maven repo. This is an issue for building on jenkins slaves without access to the external network.

This is using version 2.4.3

@gefilte
Copy link

gefilte commented Aug 26, 2014

I'm seeing this same behavior. The maven mirror settings are not being respected in selecting a repository to download plugin dependencies. The problem seems to have been introduced along with the introduction of Aether to this plugin. 2.4.0.RC2 works fine, but starting with 2.4.0 release this functionality is broken.

Incidentally, this problem does not occur if you attempt to build grails-maven on its own. It's only evident when including grails-maven as a plugin for another POM (i.e., a grails project POM.)

@bpt6576
Copy link

bpt6576 commented Oct 1, 2014

@gefilte You said, "Incidentally, this problem does not occur if you attempt to build grails-maven on its own."

Could you please explain what you mean by this? I'm running into this bug and I don't understand what you are suggesting to do as a workaround.

@gefilte
Copy link

gefilte commented Oct 1, 2014

@bpt6576 I wasn't suggesting a workaround, alas. This was just an observation that if you clone this repo directly and build it with maven it will respect the maven proxy settings. There's no workaround there because it isn't useful as a standalone build, it's only useful as a maven plugin.

@gefilte
Copy link

gefilte commented Dec 19, 2014

The no-mirror / no-proxy problem is still happening here, despite @YuryKovalev's commit. Dependencies of this plugin are downloaded from "repo.maven.apache.org" every time instead of from the designated mirror. (And proxy settings aren't being respected either, the downloads just fail for us.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants