Read full article from UIMA PEAR packaging
The following two build plug-ins hooks into the build cycle of the PEAR project in order to make sure all dependencies end up being packaged into the final PEAR file.
The first uses the maven-dependency-plugin to resolve the runtime dependencies of the PEAR into the lib folder of the PEAR. They have to be there because the PEAR packaging plugin does not take care of packaging up the dependencies.
The second hooks into the clean phase of the build phase. It deletes the lib folder again.
Note: The lib folder is thus automatically filled and removed during the build process. Thus it should not go into the source control system and neither should you manually place any jars in there.
Read full article from UIMA PEAR packaging
The following two build plug-ins hooks into the build cycle of the PEAR project in order to make sure all dependencies end up being packaged into the final PEAR file.
The first uses the maven-dependency-plugin to resolve the runtime dependencies of the PEAR into the lib folder of the PEAR. They have to be there because the PEAR packaging plugin does not take care of packaging up the dependencies.
The second hooks into the clean phase of the build phase. It deletes the lib folder again.
Note: The lib folder is thus automatically filled and removed during the build process. Thus it should not go into the source control system and neither should you manually place any jars in there.
Read full article from UIMA PEAR packaging
No comments:
Post a Comment