GitHub user clarkperkins opened a pull request:
https://github.com/apache/maven/pull/159
Bugfix/mng 4347 recursive imports
â¦resolved using profile modifications from settings.xml
o Updated the 'DefaultModelResolver' to handle replacing repositories the
sa
Github user clarkperkins commented on the issue:
https://github.com/apache/maven/pull/158
Looks like there's a better solution out there for this, I'm going to close
this.
---
-
To unsubscribe, e-mail: de
Github user clarkperkins closed the pull request at:
https://github.com/apache/maven/pull/158
---
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
Github user clarkperkins commented on the issue:
https://github.com/apache/maven/pull/158
I just found this issue in jira - looks like it's closed as a won't-fix...
so sounds like there's a reason this hasn'
GitHub user clarkperkins opened a pull request:
https://github.com/apache/maven/pull/158
Set the profiles on reecursive dependencyManagement imports
When a set of default repositories are specified via a profile in the
global settings.xml, recursive dependencyManagement imports