Skip to content

Configure Compiler Warnings and Errors #8

Open

Description

@Horcrux7

There should be the option to customize the error or warning behavior of the compiler.

Possible problem description
native Methode There is a reference to a native method without replacement. This can result in a break or an unreachable code exception. Then only if the method is called an runtime error occur.
missing class/method There is a reference to a library that is not ship.
exclude classes There are classes in a library that should not be included to reduce the compile size.
Possible scopes description
all Problems in all classes should be ignored
library Problem classes from library and Java runtime should be ignored
java Problem classes from Java runtime should be ignored
none Any problem should be break the compiler run
pattern Problems in classes that match a pattern like java.lang.* should be ignored. The pattern should follow the calling script like Gradle.

Samples:

  • ignoreNative=all
  • ignoreMissing=library
  • excludeClasses=java.net.*

Are there more possible problems and scopes? Is the syntax understandable? Suggestions are welcome.

Activity

  1. Horcrux7 commented on Apr 27, 2019

    @Horcrux7
    MemberAuthor

    @Alexeuka A "package" is a only a special case of a "pattern". I think on the matching pattern from Gradle.

    For example java/util/*Set to handle all the Sets in the package.

    But yes, the most use patter will be: foo/bar/**
    to handle a package and its sub packages. The other use case will be handle some special files.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions