-
Notifications
You must be signed in to change notification settings - Fork 7
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
UnsolvedSymbolException{context='null', name='JpaRepository', cause='null'} #86
Comments
Thank you for your report. |
Yes, my Repository-Interfaces are extending the one of spring-data-jpa. |
Unfortunately, I could not reproduce the same exception in a project using JpaRepository. However, in your project, I think that SIT-CV could not grasp the dependence on spring-data-jpa. |
Originally my build.gradle looked like this:
But I also tried to make all dependencies available to all projects using this modified version:
|
I just noticed that the bootJar task of my two spring-boot-apps in this multi module project fail when I use your plugin in my project.
When I just remove the plugin (id 'io.sitoolkit.cv.sit-cv-gradle-plugin' version '1.0.0-beta.2'), it works again. So this might be some kind of dependency problem, because your project relies on Spring Boot aswell. |
UnsolvedSymbolException has been reproduced in my environment. The cause seems to be a bug of SIT-CV. I have fixed it, so please try the following fixed version to see if the problem is solved.
build.gradle
|
Also, can you try to see if bootJar also fails when using the above plug-in version? (1.0.0-beta.4-SNAPSHOT uses a newer version of Spring) |
You also need to have the com.sun:tools:1.5.0 jar in $JAVA_HOME/../lib and the gradle install tasks puts the plugin to ".m2/repository/io/sitoolkit/cv/sit-cv-gradle-plugin/1.0.0-beta.4-SNAPSHOT", but gradle looks for it in ".m2/repository/gradle/plugin/io/sitoolkit/cv/sit-cv-gradle-plugin/1.0.0-beta.4-SNAPSHOT". After sorting this out, the cvReport task and the bootJar tasks run without any problem. Thank you. |
Hello,
do you already know a approximate release date of version 1.0.0-beta.4?
kind regards
Am Fr., 15. März 2019 um 05:25 Uhr schrieb kfujinuma <
[email protected]>:
… Also, can you try to see if bootJar also fails when using the above
plug-in version? (1.0.0-beta.4-SNAPSHOT uses a new version of Spring)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#86 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ARDkxprVifgovB5yxG3e4NVdch1xWrB6ks5vWyDFgaJpZM4bhEyV>
.
|
@Lyannic We released v1.0.0-beta.4 just today! |
Thank you very much for your reply
…On Sun, 4 Aug 2019, 11:24 Yuichi Kuwahara, ***@***.***> wrote:
@Lyannic <https://github.com/Lyannic> We released v1.0.0-beta.4 just
today!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#86?email_source=notifications&email_token=AEIOJRQMSSBXOPMHTRIHVG3QC2N6NA5CNFSM4G4EJSK2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD3P5ZJY#issuecomment-517987495>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AEIOJRTKKX3QZXMJXA54N5LQC2N6NANCNFSM4G4EJSKQ>
.
|
I didn't manage to try out the official release till now. But I get the same error with 1.1.1 and also with the official 1.0.0-beta.4. |
Hello,
when I try to execute the cvReport task for a project that contains JpaRepositories, I get the following exception:
When I delete the JpaRepositories from the project, everything works fine. Do you have any idea, why it can't handle them?
Thank you in advance for any help.
The text was updated successfully, but these errors were encountered: