Accurate Maven Plugin Project

Accurate REST Maven Plugin

License	Apache 2
Categories	Maven Build Tools
GroupId	io.codearte.accurest
ArtifactId	accurest-maven-project
Last Version	0.3-51
Release Date	Apr 5, 2016
Type	pom
Description	Accurate Maven Plugin Project Accurate REST Maven Plugin
Project URL	https://github.com/Codearte/accurest-maven-plugin
Source Code Management	https://github.com/Codearte/accurest-maven-plugin

Download accurest-maven-project

Filename	Size
accurest-maven-project-0.3-51.pom	5 KB

How to add to project

Apache Maven

<!-- https://jarcasting.com/artifacts/io.codearte.accurest/accurest-maven-project/ -->
<dependency>
    <groupId>io.codearte.accurest</groupId>
    <artifactId>accurest-maven-project</artifactId>
    <version>0.3-51</version>
    <type>pom</type>
</dependency>

Gradle Groovy

// https://jarcasting.com/artifacts/io.codearte.accurest/accurest-maven-project/
implementation 'io.codearte.accurest:accurest-maven-project:0.3-51'

Gradle Kotlin

// https://jarcasting.com/artifacts/io.codearte.accurest/accurest-maven-project/
implementation ("io.codearte.accurest:accurest-maven-project:0.3-51")

Apache Buildr

'io.codearte.accurest:accurest-maven-project:pom:0.3-51'

Apache Ivy

<dependency org="io.codearte.accurest" name="accurest-maven-project" rev="0.3-51">
  <artifact name="accurest-maven-project" type="pom" />
</dependency>

Groovy Grape

@Grapes(
@Grab(group='io.codearte.accurest', module='accurest-maven-project', version='0.3-51')
)

Scala SBT

libraryDependencies += "io.codearte.accurest" % "accurest-maven-project" % "0.3-51"

Leiningen

[io.codearte.accurest/accurest-maven-project "0.3-51"]

Dependencies

There are no dependencies for this project. It is a standalone project that does not depend on any other jars.

Project Modules

• maven-plugin

Spring Cloud Contract Verifier Maven Plugin

Documentation

• Spring Cloud Contract Verifier Documentation

• Spring Cloud Contract Verifier Maven Plugin Documentation Site

Contributing

Spring Cloud is released under the non-restrictive Apache 2.0 license, and follows a very standard Github development process, using Github tracker for issues and merging pull requests into master. If you want to contribute even something trivial please do not hesitate, but follow the guidelines below.

Sign the Contributor License Agreement

Before we accept a non-trivial patch or pull request we will need you to sign the contributor’s agreement. Signing the contributor’s agreement does not grant anyone commit rights to the main repository, but it does mean that we can accept your contributions, and you will get an author credit if we do. Active contributors might be asked to join the core team, and given the ability to merge pull requests.

Code of Conduct

This project adheres to the Contributor Covenant code of conduct. By participating, you are expected to uphold this code. Please report unacceptable behavior to [email protected].

Code Conventions and Housekeeping

None of these is essential for a pull request, but they will all help. They can also be added after the original pull request but before a merge.

• Use the Spring Framework code format conventions. If you use Eclipse you can import formatter settings using the eclipse-code-formatter.xml file from the Spring Cloud Build project. If using IntelliJ, you can use the Eclipse Code Formatter Plugin to import the same file.

• Make sure all new .java files to have a simple Javadoc class comment with at least an @author tag identifying you, and preferably at least a paragraph on what the class is for.

• Add the ASF license header comment to all new .java files (copy from existing files in the project)

• Add yourself as an @author to the .java files that you modify substantially (more than cosmetic changes).

• Add some Javadocs and, if you change the namespace, some XSD doc elements.

• A few unit tests would help a lot as well — someone has to do it.

• If no-one else is using your branch, please rebase it against the current master (or other target branch in the main project).

• When writing a commit message please follow these conventions, if you are fixing an existing issue please add Fixes gh-XXXX at the end of the commit message (where XXXX is the issue number).

Versions

Version
0.3-51 Apr 5, 2016
0.3-50 Apr 5, 2016
0.3-48 Apr 5, 2016
0.3-47 Apr 5, 2016
0.3.45 Apr 4, 2016
0.3.43 Apr 4, 2016
0.3.41 Apr 3, 2016
0.3.40 Apr 3, 2016
0.3.39 Apr 3, 2016
0.2 Apr 3, 2016
0.1.2 Apr 2, 2016
0.1.1 Apr 2, 2016
0.1 Apr 2, 2016
0.1-beta Apr 2, 2016
0.1-alpha Mar 30, 2016