koraktor/mavanagaiata

View on GitHub
src/main/java/com/github/koraktor/mavanagaiata/mojo/CommitMojo.java

Summary

Maintainability
A
1 hr
Test Coverage
A
100%

Method run has 30 lines of code (exceeds 25 allowed). Consider refactoring.
Open

    public void run(GitRepository repository) throws MavanagaiataMojoException {
        try {
            GitCommit commit = repository.getHeadCommit();
            String abbrevId  = repository.getAbbreviatedCommitId();
            String shaId     = commit.getId();
Severity: Minor
Found in src/main/java/com/github/koraktor/mavanagaiata/mojo/CommitMojo.java - About 1 hr to fix

    Prefer StringBuilder (non-synchronized) or StringBuffer (synchronized) over += for concatenating strings
    Open

                        abbrevId += dirtyFlag;

    UseStringBufferForStringAppends

    Since: PMD 3.1

    Priority: Medium

    Categories: Style

    Remediation Points: 50000

    The use of the '+=' operator for appending strings causes the JVM to create and use an internal StringBuffer. If a non-trivial number of these concatenations are being used then the explicit use of a StringBuilder or threadsafe StringBuffer is recommended to avoid this.

    Example:

    public class Foo {
     void bar() {
     String a;
     a = 'foo';
     a += ' bar';
     // better would be:
     // StringBuilder a = new StringBuilder('foo');
     // a.append(' bar');
     }
    }

    Prefer StringBuilder (non-synchronized) or StringBuffer (synchronized) over += for concatenating strings
    Open

                        shaId    += dirtyFlag;

    UseStringBufferForStringAppends

    Since: PMD 3.1

    Priority: Medium

    Categories: Style

    Remediation Points: 50000

    The use of the '+=' operator for appending strings causes the JVM to create and use an internal StringBuffer. If a non-trivial number of these concatenations are being used then the explicit use of a StringBuilder or threadsafe StringBuffer is recommended to avoid this.

    Example:

    public class Foo {
     void bar() {
     String a;
     a = 'foo';
     a += ' bar';
     // better would be:
     // StringBuilder a = new StringBuilder('foo');
     // a.append(' bar');
     }
    }

    When instantiating a SimpleDateFormat object, specify a Locale
    Open

                SimpleDateFormat dateFormat = new SimpleDateFormat(this.dateFormat);

    SimpleDateFormatNeedsLocale

    Since: PMD 2.0

    Priority: Medium

    Categories: Style

    Remediation Points: 50000

    Be sure to specify a Locale when creating SimpleDateFormat instances to ensure that locale-appropriate formatting is used.

    Example:

    public class Foo {
     // Should specify Locale.US (or whatever)
     private SimpleDateFormat sdf = new SimpleDateFormat('pattern');
    }

    There are no issues that match your filters.

    Category
    Status