Skip to content

Conversation

@gsmet
Copy link
Member

@gsmet gsmet commented Dec 15, 2016

Waiting for jbossas/patch-gen#17 to be integrated and a new alpha released.

Uses Groovy 2.4.8-SNAPSHOT as it has important fixes regarding JDK9 ea+148 support.

Copy link
Member

@gunnarmorling gunnarmorling left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@gsmet Looks good overall. Some commenting would be nice so we know (roughly) which each add-opens is needed for so we can hopefully remove them again soon.

On the sharing of locations, it seems not to happen across metadata providers, right? Not a big problem, I'm still wondering though whether we only should switch to accessible members when creating the aggregated model. Then we could do it exactly once. Not sure though whether it's worth the effort. Maybe something for later (also to reduce conflicts with my concurrent work).

README.md Outdated
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could you add a comment saying which is needed for what? So we can track it more easily and check whether we can remove any after a component or plug-in update.

cdi/pom.xml Outdated
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same here.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is it an optimization to avoid creating a stream instance?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes. It's the common case so I thought we might as well be as efficient as possible.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we even need that any longer?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah right, removed :).

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Shouldn't it be a TypeArgumentConstraintLocation?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No, it's the one which will be wrapped later. It's strictly equivalent to the existing code.

@gsmet
Copy link
Member Author

gsmet commented Dec 15, 2016

Pushed a new version with fixes and more comments.

@gsmet
Copy link
Member Author

gsmet commented Dec 15, 2016

On the sharing of locations, it seems not to happen across metadata providers, right? Not a big problem, I'm still wondering though whether we only should switch to accessible members when creating the aggregated model. Then we could do it exactly once. Not sure though whether it's worth the effort. Maybe something for later (also to reduce conflicts with my concurrent work).

Yes, that might be something we want to do in the future but it's orthogonal to this patch.

<properties>
<surefire.argLine.extension>--add-modules ${jigsaw.modules}</surefire.argLine.extension>
<maven-surefire-plugin.argLine.add-modules>--add-modules=${maven-surefire-plugin.jigsaw.modules}</maven-surefire-plugin.argLine.add-modules>
<arquillian.javaVmArguments.add-opens>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Wow, that's a whole lot. They are all required by WildFly?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I took them from the WF patch referenced by Tomaz. I think it's better to be in line with their expectations. I didn't play hide and seek for this one.

@gunnarmorling
Copy link
Member

gunnarmorling commented Dec 16, 2016 via email

@gsmet
Copy link
Member Author

gsmet commented Dec 17, 2016

@gunnarmorling pushed a new version:

  • only use Groovy 2.4.8-SNAPSHOT for JDK 9
  • upgrade patch-gen-maven-plugin to 2.0.1.Alpha3 that Alexey released

I think it's ready to go now. I'll work on the backports once this is in.

@gunnarmorling gunnarmorling merged commit a919079 into hibernate:master Dec 17, 2016
@gunnarmorling
Copy link
Member

Looks reat now! Merged, thanks, @gsmet!

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants