M

MavenAnalysisConf

Provides a Checkstyle and PMD configuration. The PMD configuration is meant to allow for future hierarchical levels to be defined, so that projects can choose which level to adhere. Checkstyle is not as flexible. I have provided a check that looks for a BSD 3 clause header in your project assuming that will be your default, especially in the https://github.com/salesforce/ repositories.
repositories allow have adhere hierarchical looks level levels especially future choose assuming https defined check your meant provides flexible header projects that project default which checkstyle will salesforce provided configuration github clause
Files download
File Operation
MavenAnalysisConf-2.0.1.jar download
MavenAnalysisConf-2.0.1.pom download
MavenAnalysisConf-2.0.1-sources.jar download
Apache Maven 
<dependency>
  <groupId>com.salesforce.maven</groupId>
  <artifactId>MavenAnalysisConf</artifactId>
  <version>2.0.1</version>
</dependency>
Gradle Groovy 
implementation 'com.salesforce.maven:MavenAnalysisConf:2.0.1'
Gradle Kotlin 
implementation("com.salesforce.maven:MavenAnalysisConf:2.0.1")
Scala SBT 
libraryDependencies += "com.salesforce.maven" % "MavenAnalysisConf" % "2.0.1"
Groovy Grape 
@Grapes(
  @Grab(group='com.salesforce.maven', module='MavenAnalysisConf', version='2.0.1')
)
Apache Ivy 
<dependency org="com.salesforce.maven" name="MavenAnalysisConf" rev="2.0.1" />
Leiningen 
[com.salesforce.maven/MavenAnalysisConf "2.0.1"]
Apache Buildr 
'com.salesforce.maven:MavenAnalysisConf:jar:2.0.1'
Dependencies 
<parent>
  <groupId>com.salesforce.maven</groupId>
  <artifactId>MavenBase</artifactId>
  <version>2.0.1</version>
</parent>
The project has no third-party dependencies