From 3b2c1e51a4b82dde42cb1cb2bf9735cadf0daf79 Mon Sep 17 00:00:00 2001
From: Vaadin Bot <vaadin-bot@users.noreply.github.com>
Date: Thu, 21 Nov 2024 12:03:41 +0100
Subject: [PATCH] chore: make hybrid dev module a provided dependency (#6918)
 (#7023)

vaadin-dev-bundle requires vaadin-hybrid-dev-bundle only to extract the hybrid
package-lock.json file. It necessary to have the hybrid bundle module as a
project dependency, to make sure modules are executed in the correct order by
maven reactor. However, the scope of the hybrid dependency must be provided
to prevent the flow maven plugin to find its stats.json in classpath and
then refusing to create a new dev bundle.

Co-authored-by: Marco Collovati <marco@vaadin.com>
Co-authored-by: Zhe Sun <31067185+ZheSun88@users.noreply.github.com>
---
 scripts/generator/templates/template-dev-bundle-pom.xml | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/scripts/generator/templates/template-dev-bundle-pom.xml b/scripts/generator/templates/template-dev-bundle-pom.xml
index 349ce3727..19de6b2dc 100644
--- a/scripts/generator/templates/template-dev-bundle-pom.xml
+++ b/scripts/generator/templates/template-dev-bundle-pom.xml
@@ -25,10 +25,17 @@
     </properties>
 
     <dependencies>
+        <!--
+            vaadin-hybrid-dev-bundle must be a project dependency otherwise it will be built
+            after vaadin-dev-bundle because of modules configuration in root pom.
+            Configuring the dependency with provided scope will prevent it to be scanned by
+            flow-dev-bundle-plugin.
+        -->
         <dependency>
             <groupId>${project.groupId}</groupId>
             <artifactId>vaadin-hybrid-dev-bundle</artifactId>
             <version>${project.version}</version>
+            <scope>provided</scope>
             <optional>true</optional>
         </dependency>
         <dependency>