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

japiCmp Gradle task does not have a relocatable build cache #321

Open
jprinet opened this issue Apr 19, 2022 · 2 comments
Open

japiCmp Gradle task does not have a relocatable build cache #321

jprinet opened this issue Apr 19, 2022 · 2 comments

Comments

@jprinet
Copy link
Contributor

jprinet commented Apr 19, 2022

If you run the JapiCmp task from 2 different folders with the same inputs, you can't benefit from Gradle build cache as one of the input (richReport.rules's Map) is using an absolute path as value.

In my cache relocation experience, the cost was 33 tasks executed in 33 projects totaling 39.212s building micronaut-core:
./gradlew clean check -x :http-server-netty:test

@melix
Copy link
Contributor

melix commented Apr 19, 2022

I'm actually not quite sure how to fix this properly. At least, I don't think this can be done properly simply by changing the micronaut-build project: the rules probably need to be able to use a MapProperty instead of just a Map, which requires changes to the japicmp plugin. Even if they do so, the value would still be a String...

@jprinet
Copy link
Contributor Author

jprinet commented Apr 20, 2022

I was wondering if "just" using a relative path could help.
That would be a simpler change but I'm unsure of the implications / feasibility

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