On 31/03/2019 19:49, Jochen Theodorou wrote:
On 31.03.19 16:56, MG wrote:
[...]
The question then becomes: How could we achieve a more sweeping solution
that is less evolutionary in nature ? Maybe there are more companies
that would benefit from such an improvement, and would be willing to
parti
On 31.03.19 16:56, MG wrote:
[...]
The question then becomes: How could we achieve a more sweeping solution
that is less evolutionary in nature ? Maybe there are more companies
that would benefit from such an improvement, and would be willing to
participate in getting this done ?
It is unlikely
On 31/03/2019 14:19, Jochen Theodorou wrote:
On 31.03.19 00:57, Paul King wrote:
The other "interim" fix would be to try to have more AST xforms run
before stub generation. This would not be about trying to do stub
generation later but running (some) xforms during a first phase and then
rolli
On 31.03.19 00:57, Paul King wrote:
The other "interim" fix would be to try to have more AST xforms run
before stub generation. This would not be about trying to do stub
generation later but running (some) xforms during a first phase and then
rolling back phases and proceeding normally. This isn'
The other "interim" fix would be to try to have more AST xforms run before
stub generation. This would not be about trying to do stub generation later
but running (some) xforms during a first phase and then rolling back phases
and proceeding normally. This isn't a general solution but could cover s
Hi Jochen,
The stubs can be generated in memory... they are
still generated in files by default.
Cheers,
Daniel.Sun
-
Apache Groovy committer
Blog: http://blog.sunlan.me
Twitter: @daniel_sun
--
Sent from: http://groovy.329449.n5.nabble.com/Groovy-Dev-f372993.html
On 28.03.19 19:05, Milles, Eric (TR Tech, Content & Ops) wrote:
This subject has been discussed a few times in the past and I'd like to
give it a bump. As I mentioned in one of the bugs linked to
https://issues.apache.org/jira/browse/GROOVY-3683, joint compilation is
our main use case for Groovy
This subject has been discussed a few times in the past and I'd like to give it
a bump. As I mentioned in one of the bugs linked to
https://issues.apache.org/jira/browse/GROOVY-3683, joint compilation is our
main use case for Groovy. We have large Java projects and want to introduce
Groovy li
