2014-11-20 16:29:10 -05:00
|
|
|
<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
|
|
|
|
<modelVersion>4.0.0</modelVersion>
|
|
|
|
|
|
|
|
<!--
|
|
|
|
HAPI projects use the Sonatype OSS parent project.
|
|
|
|
You do not need to use this <parent> in your own projects.
|
|
|
|
-->
|
|
|
|
<parent>
|
|
|
|
<groupId>org.sonatype.oss</groupId>
|
|
|
|
<artifactId>oss-parent</artifactId>
|
|
|
|
<version>7</version>
|
|
|
|
</parent>
|
|
|
|
|
|
|
|
|
|
|
|
<groupId>ca.uhn.hapi.example</groupId>
|
|
|
|
<artifactId>hapi-fhir-example-simple-server</artifactId>
|
2018-11-29 15:22:43 -05:00
|
|
|
<version>0.8</version>
|
2014-11-20 16:29:10 -05:00
|
|
|
<packaging>war</packaging>
|
|
|
|
|
|
|
|
<name>HAPI FHIR Example - Simple Server</name>
|
|
|
|
|
|
|
|
<repositories>
|
|
|
|
<repository>
|
|
|
|
<id>oss-snapshots</id>
|
|
|
|
<snapshots>
|
|
|
|
<enabled>true</enabled>
|
|
|
|
</snapshots>
|
|
|
|
<url>https://oss.sonatype.org/content/repositories/snapshots/</url>
|
|
|
|
</repository>
|
|
|
|
</repositories>
|
|
|
|
|
|
|
|
<dependencies>
|
|
|
|
|
|
|
|
<!-- This dependency includes the core HAPI-FHIR classes -->
|
|
|
|
<dependency>
|
|
|
|
<groupId>ca.uhn.hapi.fhir</groupId>
|
|
|
|
<artifactId>hapi-fhir-base</artifactId>
|
2018-11-29 15:22:43 -05:00
|
|
|
<version>1.6</version>
|
2014-11-20 16:29:10 -05:00
|
|
|
</dependency>
|
|
|
|
<dependency>
|
|
|
|
<groupId>ca.uhn.hapi.fhir</groupId>
|
|
|
|
<artifactId>hapi-fhir-structures-dstu</artifactId>
|
2018-11-29 15:22:43 -05:00
|
|
|
<version>1.6</version>
|
2014-11-20 16:29:10 -05:00
|
|
|
</dependency>
|
|
|
|
|
|
|
|
<!--
|
|
|
|
HAPI-FHIR uses Logback for logging support. The logback library is included
|
|
|
|
automatically by Maven as a part of the hapi-fhir-base dependency, but you
|
|
|
|
also need to include a logging library. Logback is used here, but log4j
|
|
|
|
would also be fine.
|
|
|
|
-->
|
|
|
|
<dependency>
|
|
|
|
<groupId>ch.qos.logback</groupId>
|
|
|
|
<artifactId>logback-classic</artifactId>
|
|
|
|
<version>1.1.2</version>
|
|
|
|
</dependency>
|
|
|
|
|
|
|
|
<!-- Needed for JEE/Servlet support -->
|
|
|
|
<dependency>
|
|
|
|
<groupId>javax.servlet</groupId>
|
|
|
|
<artifactId>javax.servlet-api</artifactId>
|
|
|
|
<version>3.0.1</version>
|
|
|
|
<scope>provided</scope>
|
|
|
|
</dependency>
|
|
|
|
|
|
|
|
</dependencies>
|
|
|
|
|
|
|
|
<build>
|
|
|
|
|
|
|
|
<!--
|
|
|
|
Tells Maven to name the generated WAR file as
|
|
|
|
restful-server-example.war
|
|
|
|
-->
|
|
|
|
<finalName>restful-server-example</finalName>
|
|
|
|
|
|
|
|
<!--
|
|
|
|
The following is not required for the application to build, but
|
|
|
|
allows you to test it by issuing "mvn jetty:run" from the command
|
|
|
|
line.
|
|
|
|
-->
|
|
|
|
<pluginManagement>
|
|
|
|
<plugins>
|
|
|
|
<plugin>
|
|
|
|
<groupId>org.eclipse.jetty</groupId>
|
|
|
|
<artifactId>jetty-maven-plugin</artifactId>
|
|
|
|
<version>9.1.1.v20140108</version>
|
|
|
|
</plugin>
|
|
|
|
</plugins>
|
|
|
|
</pluginManagement>
|
|
|
|
|
|
|
|
<plugins>
|
|
|
|
<!--
|
|
|
|
Tell Maven which Java source version you want to use
|
|
|
|
-->
|
|
|
|
<plugin>
|
|
|
|
<groupId>org.apache.maven.plugins</groupId>
|
|
|
|
<artifactId>maven-compiler-plugin</artifactId>
|
|
|
|
<version>3.1</version>
|
|
|
|
<configuration>
|
|
|
|
<source>1.6</source>
|
|
|
|
<target>1.6</target>
|
|
|
|
</configuration>
|
|
|
|
</plugin>
|
|
|
|
|
|
|
|
<!--
|
|
|
|
The deploy plugin is configured as a part of the HAPI
|
|
|
|
internal build process, you do not need to include
|
|
|
|
the <plugin> below in your own projects
|
|
|
|
-->
|
|
|
|
<plugin>
|
|
|
|
<groupId>org.apache.maven.plugins</groupId>
|
|
|
|
<artifactId>maven-deploy-plugin</artifactId>
|
|
|
|
<configuration>
|
|
|
|
<skip>false</skip>
|
|
|
|
</configuration>
|
|
|
|
</plugin>
|
|
|
|
|
|
|
|
</plugins>
|
|
|
|
</build>
|
|
|
|
|
|
|
|
</project>
|