Closed jabrena closed 1 year ago
This issue is the continuation of: https://twitter.com/juanantoniobm/status/1603300943604469762?s=20&t=OV-piqV4qYd-vfd4sFVsig
The tool works fine if the plugin spring-boot-maven-plugin is located in the root of pom.xml but it will fail if the plugin definition is located in a maven profile.
Example:
<profiles> <profile> <id>jvm</id> <activation> <activeByDefault>true</activeByDefault> </activation> <build> <plugins> <plugin> <groupId>org.springframework.boot</groupId> <artifactId>spring-boot-maven-plugin</artifactId> <configuration> <imageName>ghcr.io/jabrena/usecase1-a:buildpacks-jvm.0.0.1-SNAPSHOT</imageName> <image> <buildpacks> <!-- EMPTY --> </buildpacks> </image> </configuration> </plugin> </plugins> </build> </profile> <profile> <id>native</id> <build> <plugins> <plugin> <groupId>org.springframework.boot</groupId> <artifactId>spring-boot-maven-plugin</artifactId> <configuration> <image> <builder>dashaun/builder:tiny</builder> <env> <BP_NATIVE_IMAGE>true</BP_NATIVE_IMAGE> <BP_JVM_VERSION>17</BP_JVM_VERSION> <BP_NATIVE_IMAGE_BUILD_ARGUMENTS>-J-Xmx6000m</BP_NATIVE_IMAGE_BUILD_ARGUMENTS> <pullPolicy>IF_NOT_PRESENT</pullPolicy> </env> </image> </configuration> </plugin> </plugins> </build> </profile> </profiles>
Project to reproduce the scenario: https://github.com/jabrena/101-docker/blob/main/usecase1/usecase1_rest_comms_a/pom.xml
Juan Antonio
This issue is the continuation of: https://twitter.com/juanantoniobm/status/1603300943604469762?s=20&t=OV-piqV4qYd-vfd4sFVsig
The tool works fine if the plugin spring-boot-maven-plugin is located in the root of pom.xml but it will fail if the plugin definition is located in a maven profile.
Example:
Project to reproduce the scenario: https://github.com/jabrena/101-docker/blob/main/usecase1/usecase1_rest_comms_a/pom.xml
Juan Antonio