mvn clean install fabric8:run can result in docker build running twice
See original GitHub issueI’ve things like this do 2 builds (which can take a long time)
mvn clean install fabric8:run
I wonder if fabric8:build
should check if its been invoked already and not rerun itself?
Issue Analytics
- State:
- Created 7 years ago
- Comments:5 (4 by maintainers)
Top Results From Across the Web
docker build with maven - how to prevent re-downloading ...
Run stage (JDK or JRE image) : copy the jar from the previous stage. 1) No explicit cache for maven dependencies : straight...
Read more >Best practices for writing Dockerfiles - Docker Documentation
Hints, tips and guidelines for writing clean, reliable Dockerfiles. ... /go/src/project/ RUN go build -o /bin/project # This results in a single layer...
Read more >fabric8io/docker-maven-plugin
This is a Maven plugin for managing Docker images and containers. It focuses on two major aspects for a Docker build integration: ...
Read more >Faster Maven builds in Docker - A Java geek
2, Add required resources ... time DOCKER_BUILDKIT=0 docker build -t fast-maven:1.0 . (1) ... Here are the results of the five runs:.
Read more >Docker Maven Plugin - YouTube
In this video, users learn options for building images with Fabric8 Docker Maven plugins. The instructor then explains how to configure the ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I guess spring-boot:run just invokes the test-compile goal
I wonder if we should avoid the forking of Install - making folks have to type:
Was just wondering if we could make the forking of the install goal conditional on the install goal being already invoked or not to avoid the double-invoke issue
I don’t think this can be easily fixed and we are currently on the way to make goals independent and do not look up whether they are called together with other goals.
As I suppose that’s an intrinsic Maven issue, I’m going to close this.