This repository has been archived by the owner on Mar 21, 2022. It is now read-only.
Changed build mojo to enable renaming files added to container #301
Conversation
This file contains 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
…s (renaming) - if the resource selection names a single file. That way it is possible to use the build output where the name is of significance in the container - e.g. WAR name copied to Tomcat webapps directory defines the context path of the deployed app.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Enabled using the name provided in resource's literally, so that the new name can be given to a file.
The trigger for this behavious is the resource definition naming a single file (similar to the below), and the target path not ending with trailing slash (which would make DOCKER treat is as directory name).
<configuration> <baseImage>dordoka/tomcat</baseImage> <imageName>${docker-image-name}</imageName> <resources> <resource> <targetPath>${webapps-dir-path}/ROOT.war</targetPath> <directory>${project.build.directory}</directory> <include>${project.build.finalName}.war</include> </resource> </resources> </configuration>