Skip to content

Latest commit

 

History

History
75 lines (51 loc) · 1.96 KB

README.md

File metadata and controls

75 lines (51 loc) · 1.96 KB

jdata-unit-test

A framework for testing code over relational databases.

This framework is mainly inspired by DbUnit.

See https://jdut.gh.mikelue.guru/ for documentations.

Modules

Development

Deploy artifacts to OSSRH

mvn -P oss-deploy -DskipTests=true deploy

Reporting

Local building of sites:

# Quick building for AsciiDoctor
mvn -P site-author -pl ':parent' site

# With aggregation of javadoc/jxr
mvn -P site-author -pl ':parent,junit5' -Dskip.aggregate=false site

Deploy to gh-pages of GitHub

# 1. Execute site:stage after building every modules
mvn -P gh-pages clean site site:stage

# 2. Push to gh-pages branch of GitHub
mvn -P gh-pages -pl ":parent" scm-publish:publish-scm

Property scmpublish.dryRun can be used to dry run for scm-publish

-Dscmpublish.dryRun=true

Upgrade versions dependencies/plugins

Use org.codehaus.mojo:versions-maven-plugin to display/upgrade versions of dependencies/plugins:

mvn versions:display-dependency-updates
mvn versions:display-plugin-updates

The version-ruleset.xml file defines some ignorances of version number.

  • Skips -alpha versions
  • Skips -beta versions
  • Skips -RC versions
  • Skips -jre9/10/11/12/13/14/15 versions

Testing

You can use logging.level.jdut(default: warn) to assign logging level for all of the logging level under
package guru.mikelue.jdut.

mvn test -Dlogging.level.jdut=debug