Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[MENFORCER-458] Move Build-in rules to new API #233

Merged
merged 1 commit into from
Jan 17, 2023

Conversation

slawekjaranowski
Copy link
Member

Moved rules:

  • banDependencyManagementScope
  • banDistributionManagement
  • banDuplicatePomDependencyVersions
  • banDynamicVersions
  • bannedPlugins
  • bannedRepositories
  • evaluateBeanshell
  • reactorModuleConvergence
  • requireActiveProfile
  • requireExplicitDependencyScope
  • requirePluginVersions
  • requirePrerequisite
  • requireProfileIdsExist
  • requireReleaseVersion
  • requireSameVersions
  • requireSnapshotVersion

Following this checklist to help us incorporate your
contribution quickly and easily:

  • Make sure there is a JIRA issue filed
    for the change (usually before you start working on it). Trivial changes like typos do not
    require a JIRA issue. Your pull request should address just this issue, without
    pulling in other changes.
  • Each commit in the pull request should have a meaningful subject line and body.
  • Format the pull request title like [MENFORCER-XXX] - Fixes bug in ApproximateQuantiles,
    where you replace MENFORCER-XXX with the appropriate JIRA issue. Best practice
    is to use the JIRA issue title in the pull request title and in the first line of the
    commit message.
  • Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
  • Run mvn clean verify to make sure basic checks pass. A more thorough check will
    be performed on your pull request automatically.
  • You have run the integration tests successfully (mvn -Prun-its clean verify).

If your pull request is about ~20 lines of code you don't need to sign an
Individual Contributor License Agreement if you are unsure
please ask on the developers list.

To make clear that you license your contribution under
the Apache License Version 2.0, January 2004
you have to acknowledge this by using the following check-box.

Moved rules:
 - banDependencyManagementScope
 - banDistributionManagement
 - banDuplicatePomDependencyVersions
 - banDynamicVersions
 - bannedPlugins
 - bannedRepositories
 - evaluateBeanshell
 - reactorModuleConvergence
 - requireActiveProfile
 - requireExplicitDependencyScope
 - requirePluginVersions
 - requirePrerequisite
 - requireProfileIdsExist
 - requireReleaseVersion
 - requireSameVersions
 - requireSnapshotVersion
@slawekjaranowski slawekjaranowski merged commit fba5896 into master Jan 17, 2023
@slawekjaranowski slawekjaranowski deleted the MENFORCER-458-part2 branch January 17, 2023 19:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant