Can we have the descriptor file generated in a different folder?

[mv93]

Hi,

I'm using this tool to convert my xml to open-api descriptor format and then exposing the same via swagger ui.

This is how im generating:

                    <execution>
                        <id>openapi</id>
                        <phase>generate-sources</phase>
                        <goals>
                            <goal>exec</goal>
                        </goals>
                        <configuration>
                            <workingDirectory>..</workingDirectory>
                            <executable>node</executable>
                            <arguments>
                               <argument>node_modules/odata-openapi/lib/cli.js</argument>
                                <argument>${project.basedir}/src/main/resources/edmx/RequisitionService.xml</argument>                                                  
                            </arguments>											
                        </configuration>
                    </execution>

So my open api file is getting generated in the same folder as the xml. But i want to move my open api file to a different folder and expose only that as a static resource. For this im using the maven resource plugin. But i wanted to know if there is a better way to move the generated file?
I saw a parameter called basePath. can we use this to specify the directory in which we need to generated file?

[ralfhandl]

Hi @mv93

You can use the -t parameter to specify the name and path of the output file. Or just move it where you want to have it. Not using maven myself, so can’t help there.

The --basePath parameter influences the server URL within the generated OpenAPI output.

[mv93]

Thank you, this worked for me.
This is how I used it in my pom.xml:

<arguments>
<argument>node_modules/odata-openapi/lib/cli.js</argument>
<argument>${project.basedir}/src/main/resources/edmx/RequisitionService.xml</argument>  
<argument>-t</argument>	
<argument>${project.basedir}\src\main\resources\static\RequisitionService.openapi3.json</argument>
</arguments>

[ralfhandl]

@mv93 Thanks for sharing the solution!