Should be already (nearly all?) done.
On Thu, Dec 3, 2015 at 6:22 PM, Russel Winder wrote:
> Presumably the names of the Groovy repositories at ASF and at GitHub
> will be changed to remove the "incubator" bit?
>
> --
> Russel.
> ===
er :
>>
>> The roadmap document disappeared together with codehaus :(
>>
>>
>> Am 19.01.2016 um 19:39 schrieb Aseem Bansal:
>>>
>>> Hi
>>>
>>> This came up during gr8conf India. I asked Paul King and he said that to
>>> ask the community so it is known.
>>>
>>> I tried looking for groovy's roadmap but couldn't find anything. Where is
>>> it present?
>>
>>
>
>
We are still working on getting 2.5 out the door. Only a little bit of
experimental/spike work has gone in regards to 3.0 .
Cheers, Paul.
On Fri, Jan 29, 2016 at 5:22 AM, Clark Richey wrote:
> Hi! Does anyone have any information on the status of Groovy 3.0? Thanks!
>
> Sent from my iPhone
>
>
ed to receive it, please promptly delete this
> message and notify the sender by e-mail. Thank you.
>
>
> On Jan 28, 2016, at 14:56, Paul King wrote:
>
> We are still working on getting 2.5 out the door. Only a little bit of
> experimental/spike work has gone in regards
There was a hung job that I killed. I also got rid of incubator from
the repo url. Master seems to have built. Just waiting for the CI
server to catch up on the 2_4_X branch.
Cheers, Paul.
On Sat, Jan 30, 2016 at 8:40 PM, Pascal Schumacher
wrote:
> It still does not work. There are 490 pending b
Hi everyone,
Now that Groovy is an official Apache project, I'd encourage as many
people as possible to get along to ApacheCon conferences. The next one
is in May in Vancouver, Canada. Speakers get free entry, so I'd
encourage you to submit a talk - though the CFP closes today, so be
quick!
I wen
Any objections to Chris' request? The Jira he referred to is a small
backwards compatible enhancement (rather than bug fix). We'd normally
keep this for new releases but it does open up much nicer Spring
integration options, so I am not too worried about back-porting this
one.
Other opinions?
Che
I looked into what would be needed to backport GROOVY-7427 and it
turns out we'd need to bring across half of GROOVY-7087 as well. So,
while it can be done, I am kind of -1 on such a change and +1 on
getting the 2.5 beta out.
Cheers, Paul.
On Wed, Feb 17, 2016 at 8:29 AM, Cédric Champeau
wrote:
+1
On Sun, Feb 21, 2016 at 10:25 PM, Pascal Schumacher
wrote:
> Hi Konstantin,
>
> thanks for the in-depth check. :)
>
> Am 19.02.2016 um 08:49 schrieb Konstantin Boudnik:
>>
>> - gradle.properties is missing the ASL header and breaking the rat check.
>> I
>>figure this alone doesn't warrant
Spock for testing is by no means a show stopper!
On Wed, Feb 24, 2016 at 6:46 PM, Jesper Steen Møller
wrote:
>
> On 24. feb. 2016, at 01.21, Guillaume Laforge wrote:
>
> Sounds cool, Jesper, great to hear about your progress on the Antlr4
> grammar!
> Is there a way we can help you? How can we t
Groovy that we are
> using, and apply global xforms on Groovy core. While it might be ok, we want
> to minimize the risks.
>
> 2016-02-24 12:35 GMT+01:00 Paul King :
>>
>> Spock for testing is by no means a show stopper!
>>
>> On Wed, Feb 24, 2016 at 6:46 PM,
+1
On 18 Apr 2016 8:22 pm, "Sergei Egorov" wrote:
> +1
>
> Currently forces some really nasty workarounds because of servlet-api
> conflicts when Groovy CLI is being used. As well as jsp-api
>
> On Mon, Apr 18, 2016 at 1:19 PM daniel_sun
> wrote:
>
>> +1
>>
>>
>>
>> --
>> View this message in co
Looks like the upload snapshots was hung and it was tying up the jdk7
agent. I killed the upload job. Let's see what happens. Hopefully the
(non-uploading) jdk7 builds will go through but we'll need to check
the uploading again next time it runs.
On Sat, Apr 23, 2016 at 2:56 PM, John Wagenleitner
I am +1 on improving how we handle formatting for lists and maps. My
default position would be -1 on an implementation that smells like it
might be "yet another hack" that we have to maintain long term. The
main reason being that we are trying to streamline method selection
for our revised MOP (I k
+1 (binding)
built from src
checked RAT
validated checksums
On Mon, Jun 6, 2016 at 3:11 PM, John Wagenleitner
wrote:
> +1
>
> On Jun 3, 2016 10:20 AM, "Cédric Champeau" wrote:
>>
>> Dear community,
>>
>> I am happy to start the VOTE thread for the long awaited Apache Groovy
>> 2.4.7!
>> This r
Nice work Cédric, thanks for being release manager.
Cheers, Paul.
On Tue, Jun 7, 2016 at 6:33 PM, Cédric Champeau
wrote:
> Hi all,
>
> The vote for releasing Apache Groovy 2.4.7 has passed:
>
> - 9 +1 votes (5 binding)
> - 0 neutral vote
> - 0 negative vote
>
> Vote thread:
> https://mail-archiv
It shouldn't be deprecated or removed. I see that class in these
artifacts when building locally:
subprojects/groovy-test/target/libs/groovy-test-2.5.0-SNAPSHOT.jar
target/libs/groovy-all-2.5.0-SNAPSHOT.jar
but (as expected) not this:
target/libs/groovy-2.5.0-SNAPSHOT.jar
Also it seems correct
Yes, the link you sent has all in the name but is definitely not the
all jar. It contains none of the modules. Where did it come from
again?
Paul.
On Wed, Jun 8, 2016 at 10:49 PM, daniel_sun wrote:
> Hi Paul,
>
> I downloaded groovy-all-2.5.0-SNAPSHOT.jar by gradle(compile
> "org.codehaus.gr
Nice work everyone!
On Sun, Jun 19, 2016 at 6:33 PM, ? ? wrote:
> Hi Groovy-Dev,
>
> The new parser for groovy has reached another milestone, it now can
> handle almost all source code of Groovy in Action 2nd Edition(612 pass / 613
> total), all source code of grails-core-3.1.8(1212 pass / 12
Can you check the META-INF/services/javax.script.ScriptEngineFactory files
within the two respective jars? Mine seem identical for those two releases.
Also, what happens when you run this script in the groovyConsole:
def factory = new javax.script.ScriptEngineManager()
assert 'Groovy Scripting En
You probably want something like this:
def response = new XmlSlurper().parseText(books)
response.'**'.findAll{ i...@available.size() }.each {
it.@isavailable = 'true'
}
println groovy.xml.XmlUtil.serialize(response)
On Mon, Jul 4, 2016 at 3:05 PM, GroovyBeginner wrote:
> I'm trying to accompl
Just as a comment, you should consider asking such questions on the
users mailing list. The dev list is all about development of Groovy
itself.
In any case, your problem can probably be solved with XmlSlurper but
with more complexity than is ideal. I would use XmlParser:
def response = new XmlPar
Happy to change if there is indeed a problem but I still can't see an
issue myself.
Perhaps I need examples. More comments below. But I do agree the code
could be made
easier to read - the double negatives don't help.
On Fri, Jul 22, 2016 at 8:29 PM, Jochen Theodorou wrote:
>
>
> On 22.07.2016 0
change sounds more like a 3.0 thing.
Cheers, Paul.
On Fri, Jul 22, 2016 at 11:18 PM, Jochen Theodorou wrote:
>
>
> On 22.07.2016 13:17, Paul King wrote:
> [...]
>>
>> Which part could throw a ClassCastException above?
>
>
> the compareTo itself.
>
> actuall
more attention to some of the outstanding PRs around custom
numbers if I get time.
Cheers, Paul.
On Mon, Jul 25, 2016 at 5:05 PM, Jochen Theodorou wrote:
> On 24.07.2016 14:56, Paul King wrote:
>>
>> I think the GString check can be moved up as you suggest to improve
>> the reada
On Mon, Jul 25, 2016 at 5:05 PM, Jochen Theodorou wrote:
> On 24.07.2016 14:56, Paul King wrote:
>>
>> I think the GString check can be moved up as you suggest to improve
>> the readability of the code without breaking existing behavior, so
>> I've done that.
>
There is a (broken since creation) jdk9 CI on teamcity:
http://ci.groovy-lang.org/project.html?projectId=Groovy
It needs some tlc. :-(
The asciidoc generation should occur as part of install (does a
maven-style install of jars including doc jars) task but not for the
installGroovy task which creat
Do you want something like this?
def rows = [[ID:1, NAME:'Test1'], [ID:2, NAME:'Test2']]
def mb = new groovy.xml.MarkupBuilder()
mb.root {
rows.each { next ->
row {
next.each { k, v ->
"$k"(v)
}
}
}
}
On Sat, Jul 30, 2016 at 3:43 AM, GroovyBeginner
wrote:
> Is th
We made a few changes to ObjectRange recently on the master branch (so
no releases as of yet). I was going to rollback just the attempts to
provide a thread-safe iterator since it doesn't really provide full
thread safety, so might be misleading. Any objections?
Cheers, Paul.
Sure.
On Sun, Jul 31, 2016 at 1:50 PM, GroovyBeginner
wrote:
> Can I achieve this xml output directly after querying to the db?
>
>
>
> --
> View this message in context:
> http://groovy.329449.n5.nabble.com/Convert-Oracle-Result-sets-to-xml-tp5734358p5734375.html
> Sent from the Groovy Dev mail
You probably want to call toRowResult():
@Grab('org.hsqldb:hsqldb:2.3.2')
@GrabConfig(systemClassLoader=true)
import groovy.sql.Sql
def sql = Sql.newInstance('jdbc:hsqldb:mem:MyDb', 'sa', '',
'org.hsqldb.jdbcDriver')
sql.execute '''
DROP TABLE MyTable IF EXISTS;
CREATE TABLE MyTable (
i
Just playing around with the Apache builds again to see if I can get
something working.
Please ignore any false warnings coming from the PR builds from
Jenkins - just check that they are still fine on Travis for
confirmation. I'll probably disable the Apache builds again in a
couple of days if I ca
Just a possible alternative tweak to your idea. The Gradle project has
an Incubating annotation that can be added to classes, methods, etc.
That let's you pick a final package name now that won't need to change
later and we can remove the @Incubating once things settle down. I
don't mind having gro
Does anyone know why StaticCompileCastOptimizationTest extends
DefaultGroovyMethodsSTCTest and not just StaticTypeCheckingTestCase?
I am presuming that StaticCompileDGMTest which also extends
DefaultGroovyMethodsSTCTest handles the SC case for those tests.
Thanks, Paul.
OK, I changed it to not have the duplicate tests. Shout if you see
anything wrong.
Cheers, Paul.
On Thu, Aug 11, 2016 at 10:03 PM, Paul King wrote:
> Does anyone know why StaticCompileCastOptimizationTest extends
> DefaultGroovyMethodsSTCTest and not just StaticTypeCheckingTestCase?
&g
There are numerous ways to manipulate XML depending on exactly what
you are wanting to achieve. The following might be useful:
def xml = '''\
2
4
123
'''
def list = ['response', 'value', 'a', 'b', 'e']
def root = new XmlParser().parseText(xml
'..' is a shorthand for parent(), so the script removes unwanted nodes
by removing them from their parent node.
Cheers, Paul.
On Sun, Aug 14, 2016 at 10:31 PM, GroovyBeginner
wrote:
> Thanks It worked!! what does refer in the script. Could you please explain
> me the significance of using '..'
Just work on the part of the list which interest you. Instead of a
depthFirst() traversal as in the previous code I showed, just do
something like:
response.value.*.each {
// as before
}
Cheers, Paul.
P.S. You would be better off sending your questions to the users
mailing list not the dev on
I'll forward your email to the users list.
On Thu, Aug 18, 2016 at 8:17 PM, GroovyBeginner
wrote:
> Am facing the issue when serialising the node object. Here is my code
>
>
> but getting an error groovy.util.XmlNodePrinter.setPreserveWhitespace(Z)V
> and when used getting an
>
>
>
> --
> View t
You can use XmlNodePrinter directly. That is what serialize will use anyway:
new XmlNodePrinter().print(node)
Cheers, Paul.
On Sun, Aug 21, 2016 at 3:03 AM, GroovyBeginner
wrote:
> I have Employee Node Object of class groovy.util.Node
>
>
>
> How to convert this object to XML with out using the
I'll forward your email to the users list.
On Sun, Aug 21, 2016 at 5:06 PM, GroovyBeginner
wrote:
> I have Employee Node Object of class groovy.util.Node
>
> xml=Employees[attributes={}; value=[Employee[attributes={};
> value=[ID[attributes={}; value=[123]], Addresses[attributes={};
> value=[Add
I forwarded your email to the users list since it isn't about
development of the language codebase itself but rather about using
Groovy.
Cheers, Paul.
On Thu, Aug 25, 2016 at 12:51 AM, GroovyBeginner
wrote:
> I am unable to delete the sub child xml Nodes. Here is the input and code am
> trying w
I am just wondering what people's thoughts are on the different
approaches different parts of Groovy take for method resolution when
multiple methods are matched.
Given this code:
import groovy.transform.CompileStatic
interface FooA {}
interface FooB {}
class FooAB implements FooA, FooB
I guess I haven't looked into that part of JDK9 just yet. My first
reaction would be to try to see what work would be involved with the
"special handling". Keeping the existing behaviour (or close to it
with perhaps a few caveats) would be ideal but has to be weighed up
with the amount of work requ
4:22 AM, Jochen Theodorou wrote:
>>
>> On 27.08.2016 12:22, Paul King wrote:
>>>
>>> I am just wondering what people's thoughts are on the different
>>> approaches different parts of Groovy take for method resolution when
>>> multiple me
In terms of process, I think normally we prepare the release artefacts
and vote on release of those artefacts.
Cheers, Paul.
On Fri, Sep 23, 2016 at 3:01 AM, Jochen Theodorou wrote:
>
> +1
>
> following apache tradition this vote has to be at least 72h long... a
> timespan we will need anyway to
I didn't realise Java 8 was a requirement. I was hoping we could maybe
even sneak the new parser into Groovy 2.5 (but not turned on by
default) since we have been delayed so long and the parser is coming
along nicely.
Given the Java 8 requirement, that might be a bit more work than we
originally p
On Fri, Oct 7, 2016 at 8:16 PM, Thibault Kruse wrote:
> On Tue, Oct 4, 2016 at 1:22 AM, daniel_sun wrote:
>> 2)
>> subprojects/groovy-groovysh/src/main/groovy/org/codehaus/groovy/tools/shell/commands/DocCommand.groovy(TODO
>> confirm: https://github.com/danielsun1106/groovy-parser/issues/5);
>
>
I'll try to review over the next little while too. Looks very
promising at first glance! Exciting to see a good start!
Paul.
On Fri, Oct 7, 2016 at 9:17 PM, Guillaume Laforge wrote:
> For reference, here's the PR:
> https://github.com/apache/groovy/pull/439
>
> On Fri, Oct 7, 2016 at 1:00 PM, Se
Sergei, I might try to find time shortly to produce a spike of a
slightly improved transform similar to MapArguments. Are you happy for
me to use parts of yours if needed?
Cheers, Paul.
On Wed, Oct 5, 2016 at 12:39 AM, Sergei Egorov wrote:
> Hi Graeme,
>
> FYI a few years ago I created an AST tr
Russel, do you know a project with a similar build setup already doing
this so we can 'borrow' their approach?
On Sun, Oct 9, 2016 at 2:58 PM, Russel Winder wrote:
> Would it be possible to include the Git identifier of the changeset
> being compiled in the version number displayed by groovy -ver
On Wed, Oct 19, 2016 at 8:25 PM, Guillaume Laforge wrote:
> That's what I thought too.
> Although there's one :: case that .& doesn't support in Groovy.
> (details escape me at this point as I'm in a hurry to go & grab lunch :D)
I think these are the references you had in mind Guillaume:
https:/
nice!
On Wed, Oct 26, 2016 at 6:29 AM, Jochen Theodorou wrote:
> great stuff
>
>
> On 25.10.2016 18:25, Daniel.Sun wrote:
>>
>> Hi all,
>>
>> The brand new parser can support method reference and constructor
>> reference now. The implementation of backend is based on the discussion of
>>
We just have to be a little careful. Rightly or wrongly (search the mailing
lists for many discussions), current Groovy's '==' tries to do 'friendly
coercion' between types to try to give a business domain friendly meaning
to equality:
String[] one = ['a', 'b', 'c']
List two = ['a', 'b', 'c']
asse
Hi Daniel. Do you have any trouble running the groovyConsole on the parrot
branch? Won't start up for me. I'm travelling without access to proper
internet. I might have just grabbed a snapshot at an inopportune time.
On 11 Nov 2016 8:35 PM, "Guillaume Laforge" wrote:
> Ok, makes sense!
>
> Le v
On Sat, Nov 19, 2016 at 12:16 AM, Graeme Rocher wrote:
> In agreement with everyone else here.
>
> +1 to !in and !instanceof
> -1 to everything else
Same for me. I am undecided about sticky or not (allowing a space) but
easier to be conservative and loosen later.
I'm -1 for 'as' (no one has propo
Welcome! Glad to have you on board!
On Sat, Dec 10, 2016 at 7:55 PM, Sergei Egorov wrote:
> Hi, the Apache Groovy people!
>
> I'm excited to join the team! Big thanks to PMC for this opportunity.
>
> I wrote my first Groovy code 3.5 years ago :) Was tired of the POJO
> boilerplate :D
> Most of th
I don't know whether you would find listing 12.16 from ReGinA useful:
It is based on Jetty rather than com.sun.net.httpserver.HttpServer but
might provide some useful inspiration:
https://github.com/Dierk/GroovyInAction/blob/master/listings/chap12/Listing_12_16_GroovletExample.groovy
Also, I don
I should have mentioned the above example is more about illustrating
groovlets rather than serving up static content but it isn't too hard
to switch between the two.
On Sun, Dec 11, 2016 at 9:59 PM, Paul King wrote:
> I don't know whether you would find listing 12.16 from ReGinA u
Nice work but my suspicion is that enhancements like this are best not
bundled into parrot but just made a separate PR. There is no reason
this can't be evaluated for inclusion into 2.5 independent of when
parrot is merged. WDYT?
Cheers, Paul.
On Wed, Dec 14, 2016 at 10:06 PM, wrote:
> Reposito
Thanks John.
Yes, I should have a build-release process for testing later in the
week. The reference to oss.jfrog.org will probably disappear in due
course and point to our own repo.
Cheers, Paul.
On Mon, Dec 19, 2016 at 8:39 AM, Cédric Champeau
wrote:
> This looks to be related to the recent c
Interesting idea! I haven't used Swagger myself though, so I'm
possibly not the best to comment.
Cheers, Paul.
On Sat, Dec 24, 2016 at 8:29 AM, Roman Shaposhnik wrote:
> Hi!
>
> I was wondering if there are any bindings available
> for Groovy when it comes to creating REST APIs
> with Swagger.
Hi everyone,
I am ready to push out a 2.4.8 release. Any other last minute changes
that need to be done? If I don't hear anything further, I'll do the
first steps for the release (my) tomorrow and prepare some candidate
artefacts and a [VOTE] thread.
Cheers, Paul.
Done.
On Thu, Dec 29, 2016 at 8:56 AM, Paul King wrote:
> It's a new feature but it seems fairly non-controversial. I guess we
> could backport it.
>
> Cheers, Paul.
>
> On Thu, Dec 29, 2016 at 8:46 AM, Andres Almiray wrote:
>> Wondering if https://issues.apache.or
Dear community,
I am happy to start the VOTE thread for a Groovy 2.4.8 release!
This release includes 82 bug fixes/improvements as outlined in the changelog:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318123&version=12335950
Tag:
https://git1-us-west.apache.org/repos/asf
ssertion failed:
>
> assert 'Hello World' == 'hello world'.split(' ').collect{ it.uncapitalize()
> }.join(' ')
>
> | | | |
>
> false | [hello, world] hello world
>
> [hello, world]
>
>
> Am 30.12.2016 um 07:25 schrieb Paul King:
Can you give some more info? I can't replicate.
Cheers, Paul.
On Sat, Dec 31, 2016 at 4:46 AM, Jochen Theodorou wrote:
> On 30.12.2016 07:25, Paul King wrote:
>>
>> Dear community,
>>
>> I am happy to start the VOTE thread for a Groovy 2.4.8 release!
>>
that works.
Cheers, Paul.
On Sat, Dec 31, 2016 at 11:16 AM, Jochen Theodorou wrote:
> On 30.12.2016 22:13, Paul King wrote:
>>
>> Can you give some more info? I can't replicate.
>
>
> I copied the 3.2.1 wrapper over and then tried to start... this is what I
> got.
> Jus
used for the
> build? If not any gradle version will work we need to specify that in the
> build instructions for the source distribution at least.
>
> bye Jochen
>
> On 31.12.2016 03:25, Paul King wrote:
>>
>> The README gives bootstrap instructions for building fr
> On 31.12.2016 12:38, Paul King wrote:
> [...]
>>
>> There is a 'gradleVersion' property (set in the build.gradle file)
>> which is used when bootstrapping the wrapper, so no need for further
>> instructions in that regard.
>
>
> ah, ok. I am used to
uot; to update the wrapper jar
> and gradlew scripts. If we don't need it anymore, I say we remove both the
> property and wrapper.gradle.
>
> -Keegan
>
> On Sat, Dec 31, 2016 at 7:29 AM, Paul King wrote:
>>
>> I imagine some of them could be moved but I think
7:54 PM, Paul King wrote:
> Darn. Thanks for spotting that. Yes I fixed that on master previously
> but didn't notice that I forgot to merge the fix when backporting and
> CI was failing for a different reason so I ignored what I thought was
> a false positive.
>
> It's o
Dear community,
I am happy to start the VOTE thread for a Groovy 2.4.8 release!
This release includes 84 bug fixes/improvements as outlined in the changelog:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318123&version=12335950
Tag:
https://git1-us-west.apache.org/repos/asf
asc) as
> it does not exist.
>
> * Try:
> Run with --stacktrace option to get the stack trace. Run with --info or
> --debug option to get more log output.
>
> BUILD FAILED
> ---
>
>
> On Sun, Jan 8, 2017 at 10:33 PM, Paul King
Perhaps something can be done but some people use snapshots without
any timestamps. As long as that didn't break. I think years ago it
became a lot slower in that scenario if we auto set 'changing'. Not
sure if that is the case any longer.
Cheers, Paul.
On Tue, Jan 10, 2017 at 6:48 PM, Romain Man
and ran gradlew from there which is 2.3. I get the error
> with both. Not sure if I need to set up a property to point to gpg keys,
> but haven't had to do that in the past.
>
> On Mon, Jan 9, 2017 at 7:42 PM, Paul King wrote:
>>
>> Can you check the version of gradle th
gt;>
>>
>>
>> -
>>
>> Uwe Schindler
>>
>> Achterdiek 19, D-28357 Bremen
>>
>> http://www.thetaphi.de
>>
>> eMail: u...@thetaphi.de
>>
>>
>>
>> From: Cédric Champeau [mailto:cedric.champ...@gmail.com]
&
[Hopefully for real this time]
Dear community,
I am happy to start the VOTE thread for a Groovy 2.4.8 release!
This release includes 85 bug fixes/improvements as outlined in the changelog:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318123&version=12335950
Tag:
https://g
A little early to give an exact ETA Jim. I'll update here when I know more.
On Wed, Jan 11, 2017 at 2:05 AM, Jim Northrop
wrote:
> Do we have an ETA date when we can chg our gradle configs to pull 2.4.8
> please?
>
> Sent from my iPad
>
>> On 10 Jan 2017,
I am happy to announce that the vote has passed with four binding +1
votes and one non-binding +1 vote.
Binding: Paul King, Guillaume Laforge, Jochen Theodorou, Cédric Champeau.
Non-binding: Jacopo Cappellato.
(We had additional +1s earlier on the same binary artifacts but the
VOTE was restarted
Dear community,
The Apache Groovy team is pleased to announce version 2.4.8 of Apache Groovy.
Apache Groovy is a multi-facet programming language for the JVM.
Further details can be found at the http://groovy.apache.org website.
This release is a maintenance release of the GROOVY_2_4_X branch.
It
I am thinking we should do a 2.5.0-beta-1 release and possibly a 2.4.9
in a couple of weeks time. For 2.5.0-beta-1, it would be nice to have
the groovy macro PR reviewed and added (I know several of us have a
review on our TODO lists) but I think if we don't get it reviewed we
can do that in a beta
Hi Daniel,
Other comments have kind of superseded this one. The only thing I'll
add is that I am not averse to finding a way to let 2.5 users try the
new parser somehow - but as Cédric said, not at the expensive of
overcomplicating our normal release.
Cheers, Paul.
On Tue, Jan 17, 2017 at 6:48
Yes, the plan was always to create the 2_5_X branch before releasing
2.5.0-beta-1 and it makes sense to bump master to 3. If there is ever a
need for a 2_6_X, that can come later.
On Wed, Jan 18, 2017 at 8:22 PM, Cédric Champeau
wrote:
> I'm +1 on Andrés' plan. Let's have 2_4_X, 2_5_X and `mas
Just a heads-up that the auto website publishing on the CI server was
flakey last week - I spoke to a couple of you directly about it - but
just to raise awareness I'll repeat here.
It started failing a couple of days before I did the last release and
without intervention (as far as I know) is fix
+1 with a few comments below.
There has been discussion about releases for 2.4.9, 2.5.0-beta-1 and
3.0.0-ea-1. Perhaps we should split between us? I'd suggest I do the first
two with you as "co-pilot" and swap roles for the third?
Wrt promoting our release process/scripts, I'd probably hold off a
Wasn't the consensus to have parrot just in 3.0? So we could make the 2_5_X
branch now?
On 20 Jan 2017 8:08 PM, "Jochen Theodorou" wrote:
>
>
> On 19.01.2017 20:07, Paul King wrote:
>
>> +1 with a few comments below.
>>
>> There has been discussi
compiling the src from 7 or running on 7. So probably some build changes
and plugin capability.
Cheers Paul.
On 21 Jan 2017 5:01 AM, "Jochen Theodorou" wrote:
> On 20.01.2017 13:14, Paul King wrote:
>
>> Wasn't the consensus to have parrot just in 3.0? So we could mak
I plan to experiment with creating an "uber" jar (maybe using a
different name) for 2.5 that would have the parrot parser. It would be
like the indy jars for now, requiring a move into the correct
directory to enable. But it isn't high up on my priority list just
yet.
Cheers, Paul.
On Wed, Jan 2
Hi, for traits we explicitly prohibit protected (and package private)
methods - see the doco for some details. For properties however, we
never check (in 2.4.7 and earlier) for that case (protected) and in
fact include the property in the trait as if it was private. I was
thinking of adding an extr
I think it is a bit hard to compare those two numbers.
Antlr4 grammar build steps are:
gradlew test
JDK8 Build steps are:
gradlew clean test // with Indy
gradlew clean test // without Indy
And as a general comment, the CI server has numerous jobs that are kicked
off from the main builds, so expe
I have nothing against splitting the currently ear-marked 3.0 into 3
and 4 versions. We need to set expectations within the community when
the time comes and at least for me there are a number of technical
questions that spring to mind around parrot lambda syntax vs Java
lambdas and JDK8 that I thi
This thread has kind of gone into debate mode but I guess for the
record I would be -1 on any releases having parrot that weren't marked
as "experimental" or "incubating" until we thrash out future plans for
dealing with Java 8 features (default methods on interfaces/"real"
lambda expressions). I d
I have forwarded your question to the users list which is specifically
designed for usage questions about Groovy.
This list is for discussions about developing the Groovy language itself.
Cheers, Paul.
-- Forwarded message --
From: pppablo
Date: Fri, Feb 3, 2017 at 4:15 AM
Subje
I kind of got the impression that the thread seemed to turn into a
discussion thread - but happy to be corrected if others didn't get
that impression.
My impression was that there was a lot of consensus around what we
want in the next "non-bugfix" release (e.g. macros and jdk 7+) but
some fuzzines
One of the agents unregistered itself yesterday. I restarted it but it
has re-run all the nightly builds yet. I just re-started Nextflow and
it seems ok.
Cheers, Paul.
On Tue, Feb 14, 2017 at 6:05 AM, Paolo Di Tommaso
wrote:
> Hi,
>
> Has something recently changed in the joint build configurati
I am ready to release 2.4.9. Last call for any changes/fixes you want
in that release.
Cheers, Paul.
I like the idea. I thought perhaps groovy.attach.annotation.groovydoc
was a bit of a long prop name but I haven't thought of a better one
yet.
Cheers, Paul.
On Fri, Feb 24, 2017 at 12:46 PM, Daniel Sun wrote:
> Hi all,
>
> I am going to add a new annotation Groovydoc(Retention: RUNTIME),
>
Hi Daniel,
I believe we have had that issue for a while, so I think it can wait
until 2.4.10 which we can certainly release very soon if we need to.
There are a number of bugs which I am hoping to work on over the next
couple of weeks, so we'll hopefully have plenty of justification in
another rel
Dear community,
I am happy to start the VOTE thread for a Groovy 2.4.9 release!
This release includes 12 bug fixes/improvements as outlined in the changelog:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318123&version=12339147
Tag:
https://git1-us-west.apache.org/repos/asf
1 - 100 of 1312 matches
Mail list logo
