[GitHub] maven-archetype pull request #8: ARCHETYPE-491

2016-07-15 Thread kwin
Github user kwin closed the pull request at: https://github.com/apache/maven-archetype/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 if the feature

[GitHub] maven-archetype issue #8: ARCHETYPE-491

2016-07-15 Thread kwin
Github user kwin commented on the issue: https://github.com/apache/maven-archetype/pull/8 This has been 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 feature enabled and

[GitHub] maven-archetype pull request #8: ARCHETYPE-491

2016-07-10 Thread kwin
Github user kwin commented on a diff in the pull request: https://github.com/apache/maven-archetype/pull/8#discussion_r70208080 --- Diff: maven-archetype-plugin/src/it/build-archetype-and-run-its-with-existing-parent/src/test/resources/projects/basic/reference/pom.xml --- @@ -0,0

[GitHub] maven-archetype issue #8: ARCHETYPE-491

2016-07-10 Thread kwin
Github user kwin commented on the issue: https://github.com/apache/maven-archetype/pull/8 Done --- 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

[GitHub] maven-archetype issue #8: ARCHETYPE-491

2016-06-30 Thread kwin
Github user kwin commented on the issue: https://github.com/apache/maven-archetype/pull/8 Is there anything more missing from this PR to get this merged before the next release? --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as

[GitHub] maven-archetype issue #8: ARCHETYPE-491

2016-06-09 Thread kwin
Github user kwin commented on the issue: https://github.com/apache/maven-archetype/pull/8 I would need to have closer look at the already existing ITs. But that won't happen too soon I fear. Only an IT would make sense for this change. --- If your project is set up for it, yo

[GitHub] maven-archetype pull request: ARCHETYPE-491

2015-11-06 Thread kwin
Github user kwin commented on the pull request: https://github.com/apache/maven-archetype/pull/8#issuecomment-154440343 Could someone give me some feedback on this PR? --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If

[GitHub] maven-archetype pull request: ARCHETYPE-491

2015-10-03 Thread kwin
GitHub user kwin opened a pull request: https://github.com/apache/maven-archetype/pull/8 ARCHETYPE-491 allow to run integration test with another archetype as parent project You can merge this pull request into a Git repository by running: $ git pull https://github.com/kwin

[GitHub] maven pull request: MNG-5297: Mark as deprecated.

2015-06-15 Thread kwin
Github user kwin commented on a diff in the pull request: https://github.com/apache/maven/pull/51#discussion_r32460741 --- Diff: maven-model/src/main/mdo/maven.mdo --- @@ -3459,6 +3459,7 @@ String 2.0

[GitHub] maven-enforcer pull request: MENFORCER-220 pass real MojoExecution...

2015-01-05 Thread kwin
Github user kwin closed the pull request at: https://github.com/apache/maven-enforcer/pull/14 --- 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

[GitHub] maven-enforcer pull request: MENFORCER-220 pass real MojoExecution...

2014-12-19 Thread kwin
GitHub user kwin opened a pull request: https://github.com/apache/maven-enforcer/pull/14 MENFORCER-220 pass real MojoExecution into the EnforcerExpressionEvaluator You can merge this pull request into a Git repository by running: $ git pull https://github.com/kwin/maven