Correct target folder for mounting JAR dependencies in teamengine-web#649
Open
Brook-B-Nigatu wants to merge 1 commit intoopengeospatial:masterfrom
Open
Correct target folder for mounting JAR dependencies in teamengine-web#649Brook-B-Nigatu wants to merge 1 commit intoopengeospatial:masterfrom
Brook-B-Nigatu wants to merge 1 commit intoopengeospatial:masterfrom
Conversation
…ooks for jar files in WEB-INF/lib)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This small change corrects the target folder for mounting JAR files in the web version of teamengine.
Tomcat expects JAR dependencies in WEB-INF/lib and unpacked .class files in WEB-INF/classes.
While the current version would work if ${TE_BASE}/resources/lib contains unpacked .class files instead of JAR files, teamengine usage instructions suggest putting dependencies as JAR files in ${TE_BASE}/resources/lib. The default build output from the template generated from the ETS maven archetype also packages dependencies as JAR files.
This change thus avoids the need to copy JAR files directly into the WEB-INF/lib folder during development or change the build output in the ETS code.