c

core

Common classes for embeded web servers. In 99% of cases, user applications should just refer to this module and then include one of the required integrations (jetty, grizzly etc) within their application assembly modules. This then allows the underlying webserver to be swapped out easily.
grizzly common assembly easily webserver jetty integrations swapped allows embeded refer servers underlying applications required just classes module application cases should include then within modules their user this
Files download
File Operation
core-10.5.jar download
core-10.5.pom download
core-10.5-sources.jar download
Apache Maven 
<dependency>
  <groupId>uk.org.retep.microkernel.web</groupId>
  <artifactId>core</artifactId>
  <version>10.5</version>
</dependency>
Gradle Groovy 
implementation 'uk.org.retep.microkernel.web:core:10.5'
Gradle Kotlin 
implementation("uk.org.retep.microkernel.web:core:10.5")
Scala SBT 
libraryDependencies += "uk.org.retep.microkernel.web" % "core" % "10.5"
Groovy Grape 
@Grapes(
  @Grab(group='uk.org.retep.microkernel.web', module='core', version='10.5')
)
Apache Ivy 
<dependency org="uk.org.retep.microkernel.web" name="core" rev="10.5" />
Leiningen 
[uk.org.retep.microkernel.web/core "10.5"]
Apache Buildr 
'uk.org.retep.microkernel.web:core:jar:10.5'
Dependencies 
<parent>
  <groupId>uk.org.retep.microkernel.web</groupId>
  <artifactId>web</artifactId>
  <version>10.5</version>
</parent>

compile

|-- uk.org.retep.tools:annotations

|-- uk.org.retep.tools:jaxb

provided

|-- uk.org.retep.microkernel:module:10.5