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

Issue with maven build: ReificationSupport fails #689

Closed
david-bouyssie opened this issue Apr 9, 2021 · 8 comments
Closed

Issue with maven build: ReificationSupport fails #689

david-bouyssie opened this issue Apr 9, 2021 · 8 comments

Comments

@david-bouyssie
Copy link

Hi there,

I have an issue with a maven build (net.alchim31.maven : scala-maven-plugin) leading to this error:

 exception during macro expansion:
java.lang.IllegalArgumentException: can't flatten val x = Seq.newBuilder[Long]
        at scala.reflect.internal.ReificationSupport$ReificationSupportImpl.toStats(ReificationSupport.scala:100)

The case class I want to deserialize is like this:
case class Task(projectId: Long, jobIds: Seq[Long])

I don't have any issue with my SBT build.

@plokhotnyuk plokhotnyuk added the bug label Apr 9, 2021
@plokhotnyuk
Copy link
Owner

plokhotnyuk commented Apr 9, 2021

@david-bouyssie David, thanks for the bug report!
For which version of Scala the compilation error was thrown?
Do you have the ability to prepare some minimal project which reproduces it?

I've found similar errors in bug reports for scalac: scala/bug#8609
I'm going to find some workaround but need to reproduce the error first.

@david-bouyssie
Copy link
Author

Sorry I missed that information.
Used Scala Version is 2.11.11

So might be a scalac issue?

I can try to make a sample project.

@david-bouyssie
Copy link
Author

This is really weird, I can't reproduce it in a simple Sandbox.
I hope I can isolate the problem but it may take some time.

@plokhotnyuk
Copy link
Owner

@plokhotnyuk David, could you please build SNAPSHOT verison for changes in the following PR and check if they work for you: #692

@david-bouyssie
Copy link
Author

Oh nice, you find a workaround!
Yes I'll do that later.

@david-bouyssie
Copy link
Author

It looks good to me with this fix.

Thanks a lot!

@plokhotnyuk
Copy link
Owner

@david-bouyssie Thank you too for your help and support!

Please peek the v2.7.2 release with the fix.

@david-bouyssie
Copy link
Author

Amazing, thanks again for your reactivity!

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

No branches or pull requests

2 participants