Github user asfgit closed the pull request at:
https://github.com/apache/maven/pull/51
---
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 enable
Github user jvanzyl commented on the pull request:
https://github.com/apache/maven/pull/51#issuecomment-138307685
Fair enough, I cannot remember that far back :-)
---
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 pr
Github user josephw commented on the pull request:
https://github.com/apache/maven/pull/51#issuecomment-138302328
Even if it wasn't the intended use, way back in Maven 2:
4
would give:
$ mvn2 validate
[INFO] Scanning for pro
Github user jvanzyl commented on the pull request:
https://github.com/apache/maven/pull/51#issuecomment-138297887
I'm reasonably sure it's never been used for build-time enforcement.
Anything to make it clear that the enforcer is for build-time and the
prerequisite element is for runt
Github user josephw commented on the pull request:
https://github.com/apache/maven/pull/51#issuecomment-138297080
@jvanzyl although the original change was unconditional deprecation, I
changed it after comments so the current language in the patch is intended to
reflect that distincti
Github user jvanzyl commented on the pull request:
https://github.com/apache/maven/pull/51#issuecomment-138295450
No. The enforcer plugin is for build-time enforcement. The
element is for runtime enforcement. We certainly don't want to have to inspect
the any plugin configuration ele
Github user josephw commented on the pull request:
https://github.com/apache/maven/pull/51#issuecomment-138286028
@kwin, @mosabua - is this current form acceptable as a fix?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well.
Github user josephw commented on the pull request:
https://github.com/apache/maven/pull/51#issuecomment-112843851
@kwin , @mosabua: thanks. I've rewritten it to reflect that distinction,
that it's only deprecated for compile-time enforcement.
---
If your project is set up for it, you
Github user mosabua commented on the pull request:
https://github.com/apache/maven/pull/51#issuecomment-112198560
Enforcer plugin is for build time enforcement. Prerequisite is build time
as well as plugin runtime requirement. As such it should not be deprecated.
Documentation update
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 user josephw opened a pull request:
https://github.com/apache/maven/pull/51
MNG-5297: Mark as deprecated.
MNG-4840 indicates that the Enforcer plugin should be
preferred to . Indicate that in the documentation.
You can merge this pull request into a Git repository by run
11 matches
Mail list logo
