Github user markdingram closed the pull request at:
https://github.com/apache/maven-integration-testing/pull/9
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or
Github user markdingram closed the pull request at:
https://github.com/apache/maven-integration-testing/pull/10
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so
Github user markdingram closed the pull request at:
https://github.com/apache/maven-integration-testing/pull/8
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or
Github user markdingram commented on the pull request:
https://github.com/apache/maven/pull/23#issuecomment-49514275
already merged
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this
Github user markdingram closed the pull request at:
https://github.com/apache/maven/pull/23
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
GitHub user markdingram opened a pull request:
https://github.com/apache/maven-integration-testing/pull/10
Only ignore repo folder in root directory
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/markdingram/maven-integration
Github user markdingram closed the pull request at:
https://github.com/apache/maven-integration-testing/pull/4
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or
GitHub user markdingram opened a pull request:
https://github.com/apache/maven/pull/23
Fixes MNG-5663 - a regression introduced in 3.2.2 by MNG-5639 that preve...
...nts
nested import POMs from resolving their dependencies.
The cuplrit was the resetRepositories
GitHub user markdingram opened a pull request:
https://github.com/apache/maven-integration-testing/pull/8
Creation of an integration test for MNG-5663.
The test was for a regression introduced with Maven 3.2.2 that prevents
nested import scope POMs from being resolved.
You can
GitHub user markdingram opened a pull request:
https://github.com/apache/maven-integration-testing/pull/9
MNG-5639 test should run with v3.2.2
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/markdingram/maven-integration-testing
GitHub user markdingram opened a pull request:
https://github.com/apache/maven-integration-testing/pull/5
Added guidance for setting proxy if required
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/markdingram/maven-integration
GitHub user markdingram opened a pull request:
https://github.com/apache/maven-integration-testing/pull/4
MNG-5639 a test for resolving import scope POMs in DependencyManagement
The new feature is allowing the repository URL to contain a property.
You can merge this pull request
GitHub user markdingram opened a pull request:
https://github.com/apache/maven/pull/17
MNG-5639: Support resolution of Import Scope POMs from Repo that contain...
...s a ${parameter}
https://jira.codehaus.org/browse/MNG-5639
You can merge this pull request into a Git
13 matches
Mail list logo
