chore: make the npm script portable in Maven example (#1964)

asyncapi · Apr 25, 2024 · d891144 · d891144
1 parent 7e2b61d
commit d891144
Show file tree

Hide file tree

Showing 3 changed files with 13 additions and 4 deletions.
diff --git a/examples/integrate-with-maven/maven-project/pom.xml b/examples/integrate-with-maven/maven-project/pom.xml
@@ -96,6 +96,16 @@
               <nodeVersion>v18.15.0</nodeVersion>
             </configuration>
           </execution>
+          <execution>
+            <id>Dependencies</id>
+            <phase>generate-sources</phase>
+            <goals>
+              <goal>npm</goal>
+            </goals>
+            <configuration>
+              <arguments>install</arguments>
+            </configuration>
+          </execution>
           <execution>
             <id>Generate sources</id>
             <phase>generate-sources</phase>

diff --git a/examples/integrate-with-maven/maven-project/scripts/modelina/generate.ts b/examples/integrate-with-maven/maven-project/scripts/modelina/generate.ts
@@ -2,8 +2,8 @@ import { JAVA_JACKSON_PRESET, JavaFileGenerator } from '@asyncapi/modelina';
 import path from 'path';
 
 // Where should the models be placed relative to root maven project?
-const PACKAGE_NAME = 'java/com/mycompany/app';
-const MODEL_DIR = `src/main/${PACKAGE_NAME}`;
+const PACKAGE_NAME = 'com/mycompany/app';
+const MODEL_DIR = `src/main/java/${PACKAGE_NAME}`;
 
 const FINAL_OUTPUT_PATH = path.resolve(__dirname, '../../', MODEL_DIR);
 // Setup the generator and all it's configurations

diff --git a/examples/integrate-with-maven/maven-project/scripts/modelina/package.json b/examples/integrate-with-maven/maven-project/scripts/modelina/package.json
@@ -4,7 +4,6 @@
     "ts-node": "^10.3.0"
   },
   "scripts": {
-    "generate": "./node_modules/.bin/ts-node ./generate.ts",
-    "generate:windows": "..\\node_modules\\.bin\\ts-node .%\\generate.ts"
+    "generate": "ts-node ./generate.ts"
   }
 }