You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@groovy.apache.org by sh...@apache.org on 2020/03/28 18:03:15 UTC

[groovy] branch GROOVY_2_6_X updated (0282fbf -> a3be80e)

This is an automated email from the ASF dual-hosted git repository.

shils pushed a change to branch GROOVY_2_6_X
in repository https://gitbox.apache.org/repos/asf/groovy.git.


    from 0282fbf  Forbidden using command chain expression in array initializer to avoid ambiguities
     new 78b43fb  fix(docs): broken links to MarkupBuilder docs (closes #1208)
     new a3be80e  fix(docs): dead links

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:
 src/spec/doc/core-domain-specific-languages.adoc | 4 ++--
 src/spec/doc/core-getting-started.adoc           | 2 +-
 src/spec/doc/core-metaprogramming.adoc           | 2 +-
 src/spec/doc/core-semantics.adoc                 | 2 +-
 4 files changed, 5 insertions(+), 5 deletions(-)


[groovy] 02/02: fix(docs): dead links

Posted by sh...@apache.org.
This is an automated email from the ASF dual-hosted git repository.

shils pushed a commit to branch GROOVY_2_6_X
in repository https://gitbox.apache.org/repos/asf/groovy.git

commit a3be80e0065c0617b85f7ad2a3c9c22feab89bf0
Author: Shil Sinha <sh...@apache.org>
AuthorDate: Sat Mar 28 10:59:26 2020 -0700

    fix(docs): dead links
---
 src/spec/doc/core-getting-started.adoc | 2 +-
 src/spec/doc/core-metaprogramming.adoc | 2 +-
 src/spec/doc/core-semantics.adoc       | 2 +-
 3 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/src/spec/doc/core-getting-started.adoc b/src/spec/doc/core-getting-started.adoc
index beb6ce5..c5ba050 100644
--- a/src/spec/doc/core-getting-started.adoc
+++ b/src/spec/doc/core-getting-started.adoc
@@ -176,7 +176,7 @@ You should now have Groovy installed properly. You can test this by typing the f
 groovysh
 ----
 
-Which should create an interactive groovy shell where you can type Groovy statements. Or to run the <<{projectdir}/subprojects/groovy-console/{specfolder}/groovy-console.adoc,Swing interactive console>> type:
+Which should create an interactive groovy shell where you can type Groovy statements. Or to run the <<groovy-console.adoc#title-heading,Swing interactive console>> type:
 
 [source,shell]
 ----
diff --git a/src/spec/doc/core-metaprogramming.adoc b/src/spec/doc/core-metaprogramming.adoc
index 32ac759..8201e79 100644
--- a/src/spec/doc/core-metaprogramming.adoc
+++ b/src/spec/doc/core-metaprogramming.adoc
@@ -2569,7 +2569,7 @@ It is often considered bad practice to reassign parameters of a method or constr
 By adding the final modifier to all parameter declarations you can avoid this practice entirely.
 Some programmers feel that adding final everywhere increases the amount of boilerplate code and makes the
 method signatures somewhat noisy. An alternative might instead be to use a code review process or apply
-a http://codenarc.org[codenarc] http://codenarc.sourceforge.net/codenarc-rules-convention.html#ParameterReassignment[rule]
+a http://codenarc.org[codenarc] https://codenarc.github.io/CodeNarc/codenarc-rules-convention.html#parameterreassignment-rule[rule]
 to give warnings if that practice is observed but these alternatives might lead to delayed feedback during
 quality checking rather than within the IDE or during compilation. The `@AutoFinal` annotation aims to
 maximise compiler/IDE feedback while retaining succinct code with minimum boilerplate noise.
diff --git a/src/spec/doc/core-semantics.adoc b/src/spec/doc/core-semantics.adoc
index 5fe3f5d..4613796 100644
--- a/src/spec/doc/core-semantics.adoc
+++ b/src/spec/doc/core-semantics.adoc
@@ -344,7 +344,7 @@ As an example, you can specify a path to an object or element of interest:
 
 In both cases, the GPath expression can be viewed as a query on an object graph.  For POJOs, the object graph is most often built by the
 program being written through object instantiation and composition; for XML processing, the object graph is the result of `parsing`
-the XML text, most often with classes like XmlParser or XmlSlurper. See <<{projectdir}/subprojects/groovy-xml/{specfolder}/xml-userguide.adoc#Processing XML,Processing XML>>
+the XML text, most often with classes like XmlParser or XmlSlurper. See <<xml-userguide.adoc#Processing XML,Processing XML>>
 for more in-depth details on consuming XML in Groovy.
 
 [TIP]


[groovy] 01/02: fix(docs): broken links to MarkupBuilder docs (closes #1208)

Posted by sh...@apache.org.
This is an automated email from the ASF dual-hosted git repository.

shils pushed a commit to branch GROOVY_2_6_X
in repository https://gitbox.apache.org/repos/asf/groovy.git

commit 78b43fb12d1ffd03953e0aadfad42773baac3d69
Author: Shil Sinha <sh...@apache.org>
AuthorDate: Thu Mar 26 05:04:51 2020 -0700

    fix(docs): broken links to MarkupBuilder docs (closes #1208)
---
 src/spec/doc/core-domain-specific-languages.adoc | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/src/spec/doc/core-domain-specific-languages.adoc b/src/spec/doc/core-domain-specific-languages.adoc
index 06f9e8d..b3ec6b6 100644
--- a/src/spec/doc/core-domain-specific-languages.adoc
+++ b/src/spec/doc/core-domain-specific-languages.adoc
@@ -1045,11 +1045,11 @@ link:type-checking-extensions.html[type checking extensions].
 
 ==== MarkupBuilder
 
-See <<_markupbuilder,Creating Xml - MarkupBuilder>>.
+See <<xml-userguide.adoc#_markupbuilder,Creating Xml - MarkupBuilder>>.
 
 ==== StreamingMarkupBuilder
 
-See <<_streamingmarkupbuilder,Creating Xml - StreamingMarkupBuilder>>.
+See <<xml-userguide.adoc#_streamingmarkupbuilder,Creating Xml - StreamingMarkupBuilder>>.
 
 include::{projectdir}/subprojects/groovy-xml/{specfolder}/sax-builder.adoc[leveloffset=+3]