[GitHub] olamy commented on issue #19: Fix for MRELEASE-835: Automatically resolve snapshot dependencies in release:prepare

olamy commented on issue #19: Fix for MRELEASE-835: Automatically resolve snapshot dependencies in release:prepare URL: https://github.com/apache/maven-release/pull/19#issuecomment-339855892 @theit I'm happy with those changes. Except the lack of test. Is there anything you can do? A

[GitHub] olamy commented on issue #19: Fix for MRELEASE-835: Automatically resolve snapshot dependencies in release:prepare

olamy commented on issue #19: Fix for MRELEASE-835: Automatically resolve snapshot dependencies in release:prepare URL: https://github.com/apache/maven-release/pull/19#issuecomment-339855892 @theit I'm happy with this changes. Except the lack of test. Is there anything you can do? A

[GitHub] ctubbsii commented on issue #4: [MRELEASE-798] Commit additional files with release plugin

ctubbsii commented on issue #4: [MRELEASE-798] Commit additional files with release plugin URL: https://github.com/apache/maven-release/pull/4#issuecomment-339842030 +1 to this feature request I'm trying to update an OSGi manifest with the version derived from the version in the

Re: main-class + module-version

Hi, I've just implemented support for adding module version and main class. There is pull request[1] and comments and suggestions are more than welcome. The following excerpt from the test showcase how you can add module version and main class to a modular JAR fie: JarArchiver archiver = new

Re: maven-plugin-plugin due any time soon?

On 2017-10-26T14:05:01 + Mark Raynsford wrote: > > I'm running into what I think is MPLUGIN-304 [0] when upgrading > several of my Maven plugins to JDK 9. The issue has been fixed, but I > don't think that fix has made it into any release yet. Sorry for the

maven-plugin-plugin due any time soon?

Hello. I'm running into what I think is MPLUGIN-304 [0] when upgrading several of my Maven plugins to JDK 9. The issue has been fixed, but I don't think that fix has made it into any release yet. Is there a release of maven-plugin-plugin due any time soon? Apologies if this information is online

[GitHub] maven-surefire pull request #168: SUREFIRE-1424 javax.transaction.Transactio...

GitHub user eolivelli opened a pull request: https://github.com/apache/maven-surefire/pull/168 SUREFIRE-1424 javax.transaction.TransactionManager not visible with Java9 Contents of the patch: - drop --add-modules=java.ee.se - add a testcase on

[GitHub] asfbot commented on issue #6: add a IT case for bannedDependencies in a multi module project

asfbot commented on issue #6: add a IT case for bannedDependencies in a multi module project URL: https://github.com/apache/maven-enforcer/pull/6#issuecomment-339636554 Stephen Connolly on dev@maven.apache.org replies: could we get these sent to commits@m.a.o rather than dev@m.a.o

Re: [GitHub] asfgit closed pull request #6: add a IT case for bannedDependencies in a multi module project

could we get these sent to commits@m.a.o rather than dev@m.a.o On 26 October 2017 at 00:40, GitBox wrote: > asfgit closed pull request #6: add a IT case for bannedDependencies in a > multi module project > URL: https://github.com/apache/maven-enforcer/pull/6 >

[GitHub] theit opened a new pull request #19: Fix for MRELEASE-835: Automatically resolve snapshot dependencies in release:prepare

theit opened a new pull request #19: Fix for MRELEASE-835: Automatically resolve snapshot dependencies in release:prepare URL: https://github.com/apache/maven-release/pull/19 This pull requests adds support to release:prepare to let it automatically resolve snapshot dependencies without

[GitHub] maven pull request #135: [MNG-6296] Parse properties before configuring the ...

GitHub user coder-hugo opened a pull request: https://github.com/apache/maven/pull/135 [MNG-6296] Parse properties before configuring the logging settings You can merge this pull request into a Git repository by running: $ git pull https://github.com/coder-hugo/maven

[GitHub] asfgit closed pull request #7: MPLUGIN-294 - 'report' mojo should use 'extractors' configuration parameter

asfgit closed pull request #7: MPLUGIN-294 - 'report' mojo should use 'extractors' configuration parameter URL: https://github.com/apache/maven-plugin-tools/pull/7 This is a PR merged from a forked repository. As GitHub hides the original diff on merge, it is displayed below for the sake

[GitHub] asfgit closed pull request #6: For Groovy/Scala Mojos: Allow Mojo documentation in annotations, too.

asfgit closed pull request #6: For Groovy/Scala Mojos: Allow Mojo documentation in annotations, too. URL: https://github.com/apache/maven-plugin-tools/pull/6 This is a PR merged from a forked repository. As GitHub hides the original diff on merge, it is displayed below for the sake of

[GitHub] asfgit closed pull request #5: Preserving the annotations at runtime is very useful for testing

asfgit closed pull request #5: Preserving the annotations at runtime is very useful for testing URL: https://github.com/apache/maven-plugin-tools/pull/5 This is a PR merged from a forked repository. As GitHub hides the original diff on merge, it is displayed below for the sake of

[GitHub] asfgit closed pull request #4: Update to ASM5 opscode.

asfgit closed pull request #4: Update to ASM5 opscode. URL: https://github.com/apache/maven-plugin-tools/pull/4 This is a PR merged from a forked repository. As GitHub hides the original diff on merge, it is displayed below for the sake of provenance: As this is a foreign pull request

[GitHub] asfgit closed pull request #27: Fixed wrong page title for Dependency Convergence

asfgit closed pull request #27: Fixed wrong page title for Dependency Convergence URL: https://github.com/apache/maven-enforcer/pull/27 This is a PR merged from a forked repository. As GitHub hides the original diff on merge, it is displayed below for the sake of provenance: As this is

[GitHub] asfgit closed pull request #21: Add rule: banProfiles

asfgit closed pull request #21: Add rule: banProfiles URL: https://github.com/apache/maven-enforcer/pull/21 This is a PR merged from a forked repository. As GitHub hides the original diff on merge, it is displayed below for the sake of provenance: As this is a foreign pull request (from

[GitHub] asfgit closed pull request #20: MENFORCER-195 - use DependencyGraphBuilder API instead of DependencyTreeBuilder

asfgit closed pull request #20: MENFORCER-195 - use DependencyGraphBuilder API instead of DependencyTreeBuilder URL: https://github.com/apache/maven-enforcer/pull/20 This is a PR merged from a forked repository. As GitHub hides the original diff on merge, it is displayed below for the

[GitHub] asfgit closed pull request #26: Add Unit tests for RequireUpperBoundDeps

asfgit closed pull request #26: Add Unit tests for RequireUpperBoundDeps URL: https://github.com/apache/maven-enforcer/pull/26 This is a PR merged from a forked repository. As GitHub hides the original diff on merge, it is displayed below for the sake of provenance: As this is a foreign

[GitHub] asfgit closed pull request #16: MENFORCER-241 allow ignoring minor and patch level mismatches

asfgit closed pull request #16: MENFORCER-241 allow ignoring minor and patch level mismatches URL: https://github.com/apache/maven-enforcer/pull/16 This is a PR merged from a forked repository. As GitHub hides the original diff on merge, it is displayed below for the sake of provenance:

[GitHub] asfgit closed pull request #17: Added support for reading banned exclusions from a URL

asfgit closed pull request #17: Added support for reading banned exclusions from a URL URL: https://github.com/apache/maven-enforcer/pull/17 This is a PR merged from a forked repository. As GitHub hides the original diff on merge, it is displayed below for the sake of provenance: As

[GitHub] asfgit closed pull request #6: add a IT case for bannedDependencies in a multi module project

asfgit closed pull request #6: add a IT case for bannedDependencies in a multi module project URL: https://github.com/apache/maven-enforcer/pull/6 This is a PR merged from a forked repository. As GitHub hides the original diff on merge, it is displayed below for the sake of provenance:

[GitHub] asfgit closed pull request #28: [MENFORCER-281] added IT to show the issue.

asfgit closed pull request #28: [MENFORCER-281] added IT to show the issue. URL: https://github.com/apache/maven-enforcer/pull/28 This is a PR merged from a forked repository. As GitHub hides the original diff on merge, it is displayed below for the sake of provenance: As this is a

Re: next candidates for Git migration

on the git modules idea, Apache Sling is currently migrating from 1 svn repo to 200 git repos [1]: looks like they are beating us :) on the mass clone and pull question, they've just implemented [2] an aggregator repo using the "repo" command from Android [3] looks interesting: does anybody