youshallnotpass-dev / service Goto Github PK

There is no way to disable a specific rule. The best you can do is put an insanely high threshold.

Taking the following case:

final List<String> strings = new Arraylist<String>();
strings.stream().forEach(string -> processString(string));

allfinal will throw a warning of string.

I can't open https://iwillfailyou.com It seems like a domain has been changed to https://youshallnotpass.dev

Case 1

@Deprecated
public static void someMethod() {
 ... do something
}

The above code will print: filepath > @Deprecated, instead of the method definition public static void someMethod() {

Case 2

/**
* some javadoc
*/
public static void someMethod() {
 ... do something
}

The above code will print: filepath > /**, instead of the method definition public static void someMethod() {

With version 0.4.0 and the addition of the new inspections for setterfree and numultiplereturns, it seems that maven plugin might not have been correctly updated.

With running with the example config in readme: https://github.com/iwillfailyou/service#maven

mvn clean iwillfailyou:iwillfailyou

The following error is printed:

[ERROR] Failed to execute goal com.iwillfailyou:iwillfailyou-maven-plugin:0.4.0:iwillfailyou (default-cli) on project finapi-java-client: Unable to parse configuration of mojo com.iwillfailyou:iwillfailyou-maven-plugin:0.4.0:iwillfailyou for parameter setterfree: Cannot find 'setterfree' in class com.iwillfailyou.IwillfailyouMojo -> [Help 1]

If setterfree config is removed, then the same error appears for nomultiplereturn

[ERROR] Failed to execute goal com.iwillfailyou:iwillfailyou-maven-plugin:0.4.0:iwillfailyou (default-cli) on project finapi-java-client: Unable to parse configuration of mojo com.iwillfailyou:iwillfailyou-maven-plugin:0.4.0:iwillfailyou for parameter nomultiplereturn: Cannot find 'nomultiplereturn' in class com.iwillfailyou.IwillfailyouMojo -> [Help 1]

Have you considered the option to skip test code from the iwfy validation?

PMD also offers this feature: https://maven.apache.org/plugins/maven-pmd-plugin/pmd-mojo.html#includeTests

By default, test code should be included.
This feature won't really help with new projects, but it will make the "migration-phase" for older ones a little easier, as the devs can see just the issues in the prod code and not be blinded by issues in their test code.

This name has more fun :)

• github
• bintray
• maven central
• maven plugin name
• gradle plugin name

./gradlew youshallnotpass