New structure of oasp4j and oasp4j-sample

gistfile1.asciidoc

We want to merge the oasp4j and oasp4j-sample repository with the following new structure:

• oasp4j

  • pom.xml (internal dev only with central build and deployment management aspects and modules, flatten)

  • oasp4j-module

    • pom.xml (internal dev only with modules, imports opas4j-dependencies as BOM)

    • oasp4j-beanmapping (will be released/deployed)

    • oasp4j-configuration (will be released/deployed)

    • …​

    • oasp4j-web (will be released/deployed)

  • oasp4j-dependencies (will be released/deployed)

    • pom.xml (inherits from spring-boot and NOT from oasp4j, BOM)

  • oasp4j-sample

    • pom.xml (internal dev only with modules, imports opas4j-dependencies as BOM)

    • oasp4j-sample-boot (depends on app-core, spring-boot starter, etc.)

    • oasp4j-sample-classic (depends on app-core, spring-classic stuff with web.xml, etc.)

    • oasp4j-sample-core (jar with the actual code)

    • oasp4j-sample-integration (module with integration tests, starts and stops WAR in tomcat via castor)

  • oasp4j-app-template (will be released/deployed)

    • pom.xml (generates maven archtype from oasp4j-sample)

we should use oasp4j-sample-server (or oasp4j-sample-backend) to allow a Java client (e.g. with JavaFx, Dragome, or whatever) in the future.
Further we do not want to have boot and classic in parallel. We should go for oasp4j-sample-server-web for classic approach and have the boot option in oasp-forge in a separate repository.