logo HAPI Tinder Plugin

HAPI FHIR - Java API for HL7 FHIR Clients and Servers

homepage:
fresh index:
last release: 7 months ago, first release: 5 years ago
packaging: maven-plugin
get this artifact from: central
see this artifact on: search.maven.org




This chart shows how much is this artifact used as a dependency in other Maven artifacts in Central repository and GitHub:


select version:

Add this snippet into pom.xml inside tag <project><build><plugins>:




Switch to artifact.
goals:
hapi-tinder:generate-jparest-server (phase: generate-sources)
hapi-tinder:generate-multi-files (phase: generate-sources)

Generate files from FHIR resource/composite metadata using Velocity templates. Generates either source or resource files for each selected resource or composite data type. One file is generated for each selected entity. The files are generated using a Velocity template that can be taken from inside the hapi-timder-plugin project or can be located in other projects The following Maven plug-in configuration properties are used with this plug-in Attribute Description Required version The FHIR version whose resource metadata is to be used to generate the files Valid values: dstu | dstu2 | dstu3 Yes baseDir The Maven project's base directory. This is used to possibly locate other assets within the project used in file generation. No. Defaults to: ${project.build.directory}/.. generateResources Should files be generated from FHIR resource metadata? Valid values: true | false One of these four options must be specified generateDataTypes Should files be generated from FHIR composite data type metadata? Valid values: true | false generateValueSets Should files be generated from FHIR value set metadata? Valid values: true | false generateProfiles Should files be generated from FHIR profile metadata? Valid values: true | false Java source files can be generated for FHIR resources or composite data types. There is one file generated for each selected entity. The following configuration properties control the naming of the generated source files:     <targetSourceDirectory>/<targetPackage>/<filenamePrefix>element-name<filenameSuffix> where: element-name is the "title-case" name of the selected resource or composite data type. Note that all dots in the targetPackage will be replaced by the path separator character when building the actual source file location. Also note that .java will be added to the filenameSuffix if it is not already included. targetSourceDirectory The Maven source directory to contain the generated files. Yes when Java source files are to be generated targetPackage The Java package that will contain the generated classes. This package is generated in the <targetSourceDirectory> if needed. Yes when targetSourceDirectory is specified filenamePrefix The prefix string that is to be added onto the beginning of the resource or composite data type name to become the Java class name or resource file name. No filenameSuffix Suffix that will be added onto the end of the resource or composite data type name to become the Java class name or resource file name. No. Maven resource files can also be generated for FHIR resources or composite data types. The following configuration properties control the naming of the generated resource files:     <targetResourceDirectory>/<targetFolder>/<filenamePrefix>element-name<filenameSuffix> where: element-name is the "title-case" name of the selected resource or composite data type. targetResourceDirectory The Maven resource directory to contain the generated files. Yes when resource files are to be generated targetFolder The folder within the targetResourceDirectory where the generated files will be placed. This folder is generated in the <targetResourceDirectory> if needed. No template The path of one of the Velocity templates contained within the hapi-tinder-plugin Maven plug-in classpath that will be used to generate the files. One of these two options must be configured templateFile The full path to the Velocity template that is to be used to generate the files. velocityPath When using the templateFile option, this property can be used to specify where Velocity macros and other resources are located. No. Defaults to same directory as the template file. velocityProperties Specifies the full path to a java properties file containing Velocity configuration properties No. includeResources A list of the names of the resources or composite data types that should be used in the file generation No. Defaults to all defined resources except for DSTU2, the Binary resource is excluded and for DSTU3, the Conformance resource is excluded. excludeResources A list of the names of the resources or composite data types that should excluded from the file generation No. valueSetFiles A list of files containing value-set resource definitions to be used. No. Defaults to all defined value-sets that are referenced from the selected resources. profileFiles A list of files containing profile definitions to be used. No. Defaults to the default profile for each selected resource

hapi-tinder:generate-single-file (phase: generate-sources)

Generate a single file based on resource or composite type metadata. Generates either a source or resource file containing all selected resources or composite data types. The file is generated using a Velocity template that can be taken from inside the hapi-timder-plugin project or can be located in other projects The following Maven plug-in configuration properties are used with this plug-in Attribute Description Required version The FHIR version whose resource metadata is to be used to generate the files Valid values: dstu | dstu2 | dstu3 Yes baseDir The Maven project's base directory. This is used to possibly locate other assets within the project used in file generation. No. Defaults to: ${project.build.directory}/.. generateResources Should files be generated from FHIR resource metadata? Valid values: true | false One of these two options must be specified generateDataTypes Should files be generated from FHIR composite data type metadata? Valid values: true | false Java source files can be generated for FHIR resources or composite data types. There is one file generated for each selected entity. The following configuration properties control the naming of the generated source files:     <targetSourceDirectory>/<targetPackage>/<targetFile> Note that all dots in the targetPackage will be replaced by the path separator character when building the actual source file location. Also note that .java will be added to the targetFile if it is not already included. targetSourceDirectory The Maven source directory to contain the generated file. Yes when a Java source file is to be generated targetPackage The Java package that will contain the generated classes. This package is generated in the <targetSourceDirectory> if needed. Yes when targetSourceDirectory is specified packageBase The base Java package for related classes. This property can be used to reference class in other places in a folder structure. No targetFile The name of the file to be generated Yes Maven resource files can also be generated for FHIR resources or composite data types. The following configuration properties control the naming of the generated resource files:     <targetResourceDirectory>/<targetFolder>/<targetFile> targetResourceDirectory The Maven resource directory to contain the generated file. Yes when a resource file is to be generated targetFolder The folder within the targetResourceDirectory where the generated file will be placed. This folder is generated in the <targetResourceDirectory> if needed. No template The path of one of the Velocity templates contained within the hapi-tinder-plugin Maven plug-in classpath that will be used to generate the files. One of these two options must be configured templateFile The full path to the Velocity template that is to be used to generate the files. velocityPath When using the templateFile option, this property can be used to specify where Velocity macros and other resources are located. No. Defaults to same directory as the template file. velocityProperties Specifies the full path to a java properties file containing Velocity configuration properties No. includeResources A list of the names of the resources or composite data types that should be used in the file generation No. Defaults to all defined resources except for DSTU2, the Binary resource is excluded and for DSTU3, the Conformance resource is excluded. excludeResources A list of the names of the resources or composite data types that should excluded from the file generation No. valueSetFiles A list of files containing value-set resource definitions to be used. No. Defaults to all defined value-sets that are referenced from the selected resources. profileFiles A list of files containing profile definitions to be used. No. Defaults to the default profile for each selected resource

hapi-tinder:generate-structures (phase: generate-sources)
hapi-tinder:minimize-resources (phase: generate-sources)

© Jiri Pinkas 2015 - 2018. All rights reserved. Admin login To submit bugs / feature requests please use this github page
related: JavaVids | Top Java Blogs | Java školení | 4npm - npm search | monitored using: sitemonitoring
Apache and Apache Maven are trademarks of the Apache Software Foundation. The Central Repository is a service mark of Sonatype, Inc.