You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@groovy.apache.org by pa...@apache.org on 2022/01/11 00:23:55 UTC
[groovy] branch GROOVY_4_0_X updated (8a6675a -> 6ee7e4b)
This is an automated email from the ASF dual-hosted git repository.
paulk pushed a change to branch GROOVY_4_0_X
in repository https://gitbox.apache.org/repos/asf/groovy.git.
from 8a6675a GROOVY-10444: Bump javaparser to 3.24.0
new 9dfa6c9 minor rewording (thanks to @chagmed on twitter)
new 6ee7e4b update verification metadata
The 2 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
gradle/verification-metadata.xml | 4 ++--
src/spec/doc/core-metaprogramming.adoc | 13 +++++++++++--
2 files changed, 13 insertions(+), 4 deletions(-)
[groovy] 02/02: update verification metadata
Posted by pa...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
paulk pushed a commit to branch GROOVY_4_0_X
in repository https://gitbox.apache.org/repos/asf/groovy.git
commit 6ee7e4b38e720f056a1b098bb2c6e4da174ce50b
Author: Paul King <pa...@asert.com.au>
AuthorDate: Tue Jan 11 10:23:41 2022 +1000
update verification metadata
---
gradle/verification-metadata.xml | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/gradle/verification-metadata.xml b/gradle/verification-metadata.xml
index 6c2d368..3305bfd 100644
--- a/gradle/verification-metadata.xml
+++ b/gradle/verification-metadata.xml
@@ -327,8 +327,8 @@
<sha512 value="f4be9bd025cfcb060529936fe29ea0a64b6b7ca2b91d1f2ca29b087e973480b6fe29deed39882d6f9e7f772d9105a5b9bb159ea6fbfe7bc559a9e833f802a47c" origin="Generated by Gradle because a key couldn't be downloaded"/>
</artifact>
</component>
- <component group="com.github.javaparser" name="javaparser-core" version="3.23.1">
- <artifact name="javaparser-core-3.23.1.jar">
+ <component group="com.github.javaparser" name="javaparser-core" version="3.24.0">
+ <artifact name="javaparser-core-3.24.0.jar">
<pgp value="253e8e4c6fb28d11748115c1249dee8e2c07a0a2"/>
</artifact>
</component>
[groovy] 01/02: minor rewording (thanks to @chagmed on twitter)
Posted by pa...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
paulk pushed a commit to branch GROOVY_4_0_X
in repository https://gitbox.apache.org/repos/asf/groovy.git
commit 9dfa6c94feac08da4fa4b156ee5a83ec880d8d95
Author: Paul King <pa...@asert.com.au>
AuthorDate: Tue Jan 11 10:06:15 2022 +1000
minor rewording (thanks to @chagmed on twitter)
---
src/spec/doc/core-metaprogramming.adoc | 13 +++++++++++--
1 file changed, 11 insertions(+), 2 deletions(-)
diff --git a/src/spec/doc/core-metaprogramming.adoc b/src/spec/doc/core-metaprogramming.adoc
index 8641276..cb15171 100644
--- a/src/spec/doc/core-metaprogramming.adoc
+++ b/src/spec/doc/core-metaprogramming.adoc
@@ -436,11 +436,20 @@ assert f.metaClass =~ /MetaClassImpl/
==== Custom metaclasses
-You can change the metaclass of any object or class and replace with a custom implementation of the `MetaClass` gapi:groovy.lang.MetaClass[interface]. Usually you will want to subclass one of the existing metaclasses `MetaClassImpl`, `DelegatingMetaClass`, `ExpandoMetaClass`, `ProxyMetaClass`, etc. otherwise you will need to implement the complete method lookup logic. Before using a new metaclass instance you should call gapid:groovy.lang.MetaClass#initialize()[] otherwise the metaclass [...]
+You can change the metaclass of any object or class and replace it with a
+custom implementation of the `MetaClass` gapi:groovy.lang.MetaClass[interface].
+Usually you will want to extend one of the existing metaclasses such as
+`MetaClassImpl`, `DelegatingMetaClass`, `ExpandoMetaClass`, or `ProxyMetaClass`;
+otherwise you will need to implement the complete method lookup logic.
+Before using a new metaclass instance you should call
+gapid:groovy.lang.MetaClass#initialize()[],
+otherwise the metaclass may or may not behave as expected.
===== Delegating metaclass
-If you only need to decorate an existing metaclass the `DelegatingMetaClass` simplifies that use case. The old metaclass implementation is still accessible via `super` making easy to apply pretransformations to the inputs, routing to other methods and postprocess the outputs.
+If you only need to decorate an existing metaclass the `DelegatingMetaClass` simplifies that use case.
+The old metaclass implementation is still accessible via `super` making it easy to apply
+pretransformations to the inputs, routing to other methods and postprocessing the outputs.
[source,groovy]
----