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

error: no source files #313

Open
andreas-ajaib opened this issue Mar 26, 2024 · 2 comments
Open

error: no source files #313

andreas-ajaib opened this issue Mar 26, 2024 · 2 comments

Comments

@andreas-ajaib
Copy link

Got this error below when building inside container.

[ERROR] Failed to execute goal org.codehaus.mojo:jaxb2-maven-plugin:2.5.0:schemagen (schemagen) on project <omited>: 
[ERROR] +=================== [SchemaGenerator Error '<unknown>']
[ERROR] |
[ERROR] | SchemaGen did not complete its operation correctly.
[ERROR] |
[ERROR] | To re-create the error (and get a proper error message), cd to:
[ERROR] | /sources
[ERROR] | ... and fire the following on a command line/in a shell:
[ERROR] |
[ERROR] | schemagen -encoding UTF-8 -d /sources/target/schemagen-work/compile_scope -classpath file:/var/maven/repository/org/glassfish/jaxb/jaxb-xjc/2.3.2/jaxb-xjc-2.3.2.jar!/META-<omited>
[ERROR] |
[ERROR] | The following source files should be processed by schemagen:
[ERROR] | 0: file:/sources/src/main/java/com/<omited>
[ERROR] |
[ERROR] +=================== [End SchemaGenerator Error]
[ERROR] : error: no source files
[ERROR] -> [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
error building image: error building stage: failed to execute command: waiting for process to exit: exit status 1

what does this mean? cannot find similar issue.

@andreas-ajaib
Copy link
Author

I think this bug when my working dir is in another directory, eg. I am on /build, but the code is in /sources. It doesn't happen when working dir is in the parent, eg. working dir on /code, and the code is in /code/sources.

Any solution to solve this?

@slachiewicz
Copy link
Member

can You try with never plugin version?

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

2 participants