Skip to content

Core support architecture for json-schema-validator and other processors

License

Notifications You must be signed in to change notification settings

rushirajchavan/json-schema-core

This branch is 119 commits behind java-json-tools/json-schema-core:master.

Folders and files

NameName
Last commit message
Last commit date

Latest commit

Apr 17, 2014
bc0df54 · Apr 17, 2014
Apr 13, 2014
Apr 13, 2014
Feb 9, 2014
Apr 4, 2014
Jun 30, 2013
Feb 18, 2014
Apr 4, 2014
Apr 13, 2014
Apr 17, 2014
Apr 14, 2014
Apr 13, 2014
Jun 30, 2013
Jun 24, 2013
Jun 24, 2013
Apr 14, 2014
Apr 13, 2014

Repository files navigation

Read me first

The license of this project is dual licensed LGPLv3 or later/ASL 2.0. See file LICENSE for more details. The full text of both licensed is included in the package.

Version 1.2.x is out. See here for the major changes.

What this is

This package contains the core mechanics of json-schema-validator library. It also provides a comprehensive infrastructure to build processing chains for anything you can think of, really. To this effect, this package can be used, for instance, to perform the following, provided you use the appropriate software packages:

  • generate a JSON Schema from a POJO, and then validate instances against that schema;
  • transform different, related schema formats into JSON Schema, or the reverse (for instance Avro);
  • conditional patching/deserialization;
  • etc etc.

You can see sample usages of this library in a separate project which is demonstrated online. More details on this library can be found here.

Versions

The current stable verson is 1.2.1 (ChangeLog, Javadoc).

The old verson is 1.0.4 (ChangeLog, Javadoc).

Using this project with gradle/maven

For gradle, use:

dependencies {
    compile(group: "com.github.fge", name: "json-shema-core", version: "your.version");
}

For maven:

<dependency>
    <groupId>com.github.fge</groupId>
    <artifactId>json-schema-core</artifactId>
    <version>your-version</version>
</dependency>

You can also get the jars from Bintray.

Versioning scheme policy

The versioning scheme is defined by the middle digit of the version number:

  • if this number is even, then this is the stable version; no new features will be added to such versions, and the user API will not change (save for some additions if requested).
  • if this number is odd, then this is the development version; new features will be added to those versions only, and the user API may change.

About

Core support architecture for json-schema-validator and other processors

Resources

License

Stars

Watchers

Forks

Packages

No packages published