Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

final fat jar is not updated in docker build directory #386

Closed
hlavki opened this issue Sep 17, 2020 · 0 comments · Fixed by #420
Closed

final fat jar is not updated in docker build directory #386

hlavki opened this issue Sep 17, 2020 · 0 comments · Fixed by #420
Assignees
Labels
bug Something isn't working
Projects
Milestone

Comments

@hlavki
Copy link

hlavki commented Sep 17, 2020

Description

docker image in multi module spring boot project didn't change after mvn install. Workaround is to call mvn clean install

Info

  • Eclipse JKube version : 1.0.0
  • Maven version (mvn -v) :
Apache Maven 3.6.3 (cecedd343002696d0abb50b32b541b8a6ba2883f)
Maven home: /opt/apache/apache-maven
Java version: 14.0.2, vendor: N/A, runtime: /usr/lib64/jvm/java-14-openjdk-14
Default locale: sk_SK, platform encoding: UTF-8
OS name: "linux", version: "5.8.7-1-default", arch: "amd64", family: "unix"

Scenario:

  1. Build project mvn install. New artifacts are built (fatJar, docker image, etc)
  2. Change something in jkube-boot-multimodule-domain source code e.g. in HelloService.java change return string.
  3. Do another build mvn install

Now docker image contains artifact from first build. From unknown reason, the artifact assembly/target/docker/jkube/test/1.0-SNAPSHOT/build/maven/jkube-boot-multimodule-assembly-1.0-SNAPSHOT.jar didn't change, but assembly/target/jkube-boot-multimodule-assembly-1.0-SNAPSHOT.jar is correct.

@hlavki hlavki changed the title final fat jar is not updated when main jar does not changes final fat jar is not updated in docker build directory Sep 17, 2020
@manusa manusa added the bug Something isn't working label Sep 18, 2020
@manusa manusa added this to the 1.0.1 milestone Sep 18, 2020
@manusa manusa added this to Backlog in Sprint #190 Sep 29, 2020
@rohanKanojia rohanKanojia moved this from Backlog to In progress in Sprint #190 Sep 30, 2020
@rohanKanojia rohanKanojia self-assigned this Sep 30, 2020
rohanKanojia added a commit to rohanKanojia/jkube that referenced this issue Oct 1, 2020
…irectory

Updated code in JKubeBuildTarArchiver to allow copying files when already existing.
rohanKanojia added a commit to rohanKanojia/jkube that referenced this issue Oct 1, 2020
…irectory

Updated code in JKubeBuildTarArchiver to allow copying files when already existing.
rohanKanojia added a commit to rohanKanojia/jkube that referenced this issue Oct 1, 2020
…irectory

Updated code in JKubeBuildTarArchiver to allow copying files when already existing.
rohanKanojia added a commit to rohanKanojia/jkube that referenced this issue Oct 1, 2020
…irectory

Updated code in JKubeBuildTarArchiver to allow copying files when already existing.
rohanKanojia added a commit to rohanKanojia/jkube that referenced this issue Oct 5, 2020
…irectory

Updated code in JKubeBuildTarArchiver to allow copying files when already existing.
Sprint #190 automation moved this from In progress to Done Oct 5, 2020
manusa pushed a commit that referenced this issue Oct 5, 2020
Updated code in JKubeBuildTarArchiver to allow copying files when already existing.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
No open projects
Sprint #190
  
Done
Development

Successfully merging a pull request may close this issue.

3 participants