droolsjbpm-integration [windows_codegenpath] test output path on windows

Testing source output on windows

Jun 14 '21 12:06 gitgabrio

Jenkins retest this

Jun 14 '21 13:06 gitgabrio

@gitgabrio I'm afraid we have the same issue we had in the past

2021-06-15T07:31:40.1651042Z Caused by: java.io.IOException: Cannot run program "C:\hostedtoolcache\windows\jdk\8.0.292\x64\jre\..\bin\javadoc.exe" (in directory "D:\a\droolsjbpm-integration\droolsjbpm-integration\kiegroup\droolsjbpm_integration\kie-server-parent\kie-server-services\kie-server-services-task-assigning\kie-server-services-task-assigning-user-system\kie-server-services-task-assigning-user-system-api\target\apidocs"): CreateProcess error=267, The directory name is invalid

Jun 15 '21 08:06 Ginxo

@Ginxo Yup, I see. Reason for that PR was exactly to verify what may happen in windows machine. Some failures may be ignored (e.g. javadoc creation may happen just inside our "build" machines) but other code-path is expected to run on customer machine (e.g. maven-plugin execution). Main issue is that currently it seems we are not verifying what happen on windows, and it is a bit of concern from my point of view. I think a more structured approach is needed. @mariofusco @danielezonca WDYT ?

Jun 15 '21 08:06 gitgabrio

Kudos, SonarCloud Quality Gate passed!

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
No Duplication information

Jun 15 '21 10:06 sonarqubecloud[bot]

@Ginxo Yup, I see. Reason for that PR was exactly to verify what may happen in windows machine. Some failures may be ignored (e.g. javadoc creation may happen just inside our "build" machines) but other code-path is expected to run on customer machine (e.g. maven-plugin execution). Main issue is that currently it seems we are not verifying what happen on windows, and it is a bit of concern from my point of view. I think a more structured approach is needed. @mariofusco @danielezonca WDYT ?

I think making the whole -integration repo compatible with a windows build will require quite a lot of work, it is probably easier create a specific profile and configure a windows job that uses that profile. For example I agree that kie-maven-plugin should be tested also with Windows.