Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Scan fails when Maven module names have spaces #2

Open
marcuscraske opened this issue Jan 16, 2019 · 0 comments
Open

Scan fails when Maven module names have spaces #2

marcuscraske opened this issue Jan 16, 2019 · 0 comments

Comments

@marcuscraske
Copy link

A scan fails when any Maven module names contain spaces, and an entire module's code is ignored when the module name has punctuation.

If I have a module called "Service API", the scan fails with:

org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal com.checkmarx.maven:checkmarx-maven-plugin:8.90.1:scan (default-cli) on project paymentpages-reactor-pom: *****The Build Failed for the Following Reasons: *****SAST scan cannot be completed. status [Failed]: Failed to start scanning due to one of following reasons: source folder is empty, all source files are of an unsupported language or file format--

I've also noticed an entire module's code is ignored, when a module name contains punctuation e.g. "Service: API".

Otherwise if I rename a module "Service_API", the scan completes successfully.

Looking at the generated sources.zip file, generated during the scan, it appears each module has a directory, named after the module name.

The same issue seems to occur when uploading source files through the web portal, so not sure if it's an issue with this plugin. It depends whether Checkmarx its self has any upload restrictions/requirements on directory names, and therefore this plugin would need to sanitise module / directory names or it's a bug with the Checkmarx service.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant