diff --git a/404.html b/404.html index 9d871579a7..8cf3abdda0 100644 --- a/404.html +++ b/404.html @@ -174,8 +174,8 @@
Internal API
@@ -2085,8 +2085,8 @@ be the API to report violations, and it can already be used as such in PMD 6.@InternalApi annotation. You’ll also get a deprecation warning.

@@ -2102,8 +2102,8 @@ and should not be overridden in own renderers.

Note that the message is set from the XML rule declaration, so this is only relevant if you instantiate rules manually.

-

RuleContext now requires setting the current rule before calling -apply. This is +

RuleContext now requires setting the current rule before calling +apply. This is done automatically by RuleSet#apply and such. Creating and configuring a RuleContext manually is strongly advised against, as the lifecycle of RuleContext will change drastically in PMD 7.

@@ -2271,9 +2271,9 @@ compared to other cli tools.

Experimental APIs
@@ -2307,10 +2307,10 @@ See also the examples on ASTClassOrInterfaceDeclaration#isSealed, -ASTClassOrInterfaceDeclaration#isNonSealed, -ASTClassOrInterfaceDeclaration#getPermittedSubclasses -
  • ASTPermitsList
    • +
  • ASTClassOrInterfaceDeclaration#isSealed, +ASTClassOrInterfaceDeclaration#isNonSealed, +ASTClassOrInterfaceDeclaration#getPermittedSubclasses
    • +
  • ASTPermitsList
    • @@ -2321,7 +2321,7 @@ See also the examples on @InternalApi     annotation. You’ll also get a deprecation warning.

     @@ -2334,13 +2334,13 @@ It will probably be moved away with PMD 7.
    Deprecated API
    @@ -2357,20 +2357,20 @@ are deprecated. This functionality will be replaced by another TBD mechanism in
    Experimental APIs
    @@ -2381,7 +2381,7 @@ in order to align the naming to the JLS. You can identify them with the @InternalApi annotation. You’ll also get a deprecation warning.

    @@ -2390,17 +2390,17 @@ are deprecated and considered to be internal API. They will be removed with PMD
    Deprecated API
    Experimental APIs
      -
    • The method GenericToken#getKind has been added as experimental. This +
    • The method GenericToken#getKind has been added as experimental. This unifies the token interface for both JavaCC and Antlr. The already existing method -AntlrToken#getKind is therefore experimental as well. The +AntlrToken#getKind is therefore experimental as well. The returned constant depends on the actual language and might change whenever the grammar of the language is changed.
    @@ -2412,30 +2412,30 @@ of the language is changed.
    Around RuleSet parsing
    Around the PMD class
    -

    Many classes around PMD’s entry point (PMD) have been deprecated as internal, including:

    +

    Many classes around PMD’s entry point (PMD) have been deprecated as internal, including:

    Miscellaneous
    @@ -2445,13 +2445,13 @@ refs #905 You can identify them with the @InternalApi annotation. You’ll also get a deprecation warning.

    6.29.0

    @@ -2465,23 +2465,23 @@ You can identify them with the For removal
  • pmd-java
  • pmd-apex
    • @@ -2855,25 +2855,25 @@ The following usages are now deprecated in the JSP AST (with ot
    • Manual instantiation of nodes. Constructors of node classes are deprecated and -marked InternalApi. Nodes should only be obtained from the parser, +marked InternalApi. Nodes should only be obtained from the parser, which for rules, means that they never need to instantiate node themselves. Those constructors will be made package private with 7.0.0.
    • Subclassing of abstract node classes, or usage of their type. The base classes are internal API and will be hidden in version 7.0.0. You should not couple your code to them.
        -
      • In the meantime you should use interfaces like JspNode or -Node, or the other published interfaces in this package, +
      • In the meantime you should use interfaces like JspNode or +Node, or the other published interfaces in this package, to refer to nodes generically.
      • Concrete node classes will be made final with 7.0.0.
    • Setters found in any node class or interface. Rules should consider the AST immutable. We will make those setters package private with 7.0.0.
      • -
    • The class JspParser is deprecated and should not be used directly. -Use LanguageVersionHandler#getParser instead.
      • +
    • The class JspParser is deprecated and should not be used directly. +Use LanguageVersionHandler#getParser instead.
    -

    Please look at net.sourceforge.pmd.lang.jsp.ast to find out the full list of deprecations.

    +

    Please look at net.sourceforge.pmd.lang.jsp.ast to find out the full list of deprecations.

    In ASTs (Velocity)
    @@ -2883,28 +2883,28 @@ The following usages are now deprecated in the VM AST (with oth
    • Manual instantiation of nodes. Constructors of node classes are deprecated and -marked InternalApi. Nodes should only be obtained from the parser, +marked InternalApi. Nodes should only be obtained from the parser, which for rules, means that they never need to instantiate node themselves. Those constructors will be made package private with 7.0.0.
    • Subclassing of abstract node classes, or usage of their type. The base classes are internal API and will be hidden in version 7.0.0. You should not couple your code to them.
        -
      • In the meantime you should use interfaces like VmNode or -Node, or the other published interfaces in this package, +
      • In the meantime you should use interfaces like VmNode or +Node, or the other published interfaces in this package, to refer to nodes generically.
      • Concrete node classes will be made final with 7.0.0.
    • Setters found in any node class or interface. Rules should consider the AST immutable. We will make those setters package private with 7.0.0.
      • -
    • The package net.sourceforge.pmd.lang.vm.directive as well as the classes -DirectiveMapper and LogUtil are deprecated +
    • The package net.sourceforge.pmd.lang.vm.directive as well as the classes +DirectiveMapper and LogUtil are deprecated for removal. They were only used internally during parsing.
      • -
    • The class VmParser is deprecated and should not be used directly. -Use LanguageVersionHandler#getParser instead.
      • +
    • The class VmParser is deprecated and should not be used directly. +Use LanguageVersionHandler#getParser instead.
    -

    Please look at net.sourceforge.pmd.lang.vm.ast to find out the full list of deprecations.

    +

    Please look at net.sourceforge.pmd.lang.vm.ast to find out the full list of deprecations.

    PLSQL AST
    @@ -2921,36 +2921,36 @@ parsed as ASTCursorSpecificat You can identify them with the @InternalApi annotation. You’ll also get a deprecation warning.

    @@ -2959,44 +2959,44 @@ by just that superclass.

    6.14.0

    @@ -3197,7 +3197,7 @@ or enable preview language features (e.g. CodeClimateRule is deprecated in 7.0.0 because it was unused for 2 years and +

    CodeClimateRule is deprecated in 7.0.0 because it was unused for 2 years and created an unwanted dependency. Properties “cc_categories”, “cc_remediation_points_multiplier”, “cc_block_highlighting” will also be removed. See #1702 for more.

    @@ -3215,13 +3215,13 @@ quickstart ruleset rulesets/a

    6.11.0

    6.10.0

    @@ -3236,59 +3236,59 @@ to remove them in 7.0.0. The proposed changes to the API are described net.sourceforge.pmd.properties.builders, -is being replaced by the simpler PropertyBuilder. Their APIs enjoy a high degree of source compatibility.

    +construction through builders. The builder hierarchy, currently found in the package net.sourceforge.pmd.properties.builders, +is being replaced by the simpler PropertyBuilder. Their APIs enjoy a high degree of source compatibility.

  • -

    Concrete property classes like IntegerProperty and StringMultiProperty will gradually -all be deprecated until 7.0.0. Their usages should be replaced by direct usage of the PropertyDescriptor +

    Concrete property classes like IntegerProperty and StringMultiProperty will gradually +all be deprecated until 7.0.0. Their usages should be replaced by direct usage of the PropertyDescriptor interface, e.g. PropertyDescriptor<Integer> or PropertyDescriptor<List<String>>.

  • -

    Instead of spreading properties across countless classes, the utility class PropertyFactory will become +

    Instead of spreading properties across countless classes, the utility class PropertyFactory will become from 7.0.0 on the only provider for property descriptor builders. Each current property type will be replaced by a corresponding method on PropertyFactory:

    @@ -3310,19 +3310,19 @@ are discontinued for lack of a use-case, and have no planned replacement in 7.0. @@ -3330,21 +3330,21 @@ accordingly.

    Changes to the PropertyDescriptor interface
      -
    • preferredRowCount is deprecated with no intended replacement. It was never implemented, and does not belong -in this interface. The methods uiOrder and compareTo(PropertyDescriptor) are deprecated for the +
    • preferredRowCount is deprecated with no intended replacement. It was never implemented, and does not belong +in this interface. The methods uiOrder and compareTo(PropertyDescriptor) are deprecated for the same reason. These methods mix presentation logic with business logic and are not necessary for PropertyDescriptors to work. PropertyDescriptor will not extend Comparable<PropertyDescriptor> anymore come 7.0.0.
      • -
    • The method propertyErrorFor is deprecated and will be removed with no intended +
    • The method propertyErrorFor is deprecated and will be removed with no intended replacement. It’s really just a shortcut for prop.errorFor(rule.getProperty(prop)).
      • -
    • T valueFrom(String) and String asDelimitedString(T) are deprecated and will be removed. These were +
    • T valueFrom(String) and String asDelimitedString(T) are deprecated and will be removed. These were used to serialize and deserialize properties to/from a string, but 7.0.0 will introduce a more flexible XML syntax which will make them obsolete.
      • -
    • isMultiValue and type are deprecated and won’t be replaced. The new XML syntax will remove the need +
    • isMultiValue and type are deprecated and won’t be replaced. The new XML syntax will remove the need for a divide between multi- and single-value properties, and will allow arbitrary types to be represented. Since arbitrary types may be represented, type will become obsolete as it can’t represent generic types, which will nevertheless be representable with the XML syntax. It was only used for documentation, but a new way to document these properties exhaustively will be added with 7.0.0.
      • -
    • errorFor is deprecated as its return type will be changed to Optional<String> with the shift to Java 8.
      • +
    • errorFor is deprecated as its return type will be changed to Optional<String> with the shift to Java 8.
    Deprecated APIs
    @@ -3353,27 +3353,27 @@ new way to document these properties exhaustively will be added with 7.0.0.
    • @@ -3381,21 +3381,21 @@ and will be moved into an internal package with 7.0.0. To implement your own met
  • @@ -3421,25 +3421,25 @@ are not fully supported by PMD, so having a language module does not make sense. not affected by this change. The following classes have been deprecated and will be removed with PMD 7.0.0:

  • @@ -3448,12 +3448,12 @@ in 7.0.0 to factorise common logic and make them extensible. Further explanation found on #1426. Consequently, the following APIs are deprecated for removal:

    • diff --git a/pmd_projectdocs_committers_infrastructure.html b/pmd_projectdocs_committers_infrastructure.html index 10289b53ff..ac905f84d0 100644 --- a/pmd_projectdocs_committers_infrastructure.html +++ b/pmd_projectdocs_committers_infrastructure.html @@ -174,8 +174,8 @@