Thanks for the quick response. The asciidoc warnings are related to merging subproject and main ascidoc files (relative paths go astray). They can safely be ignored since once merged all is fine but if you can think of a nice way to get rid of the warnings I'm keen to know. ;-)
Cheers, Paul. On Sat, Jun 23, 2018 at 4:59 PM Andres Almiray <aalmi...@gmail.com> wrote: > Built and tested from source. > > There are 6 javadoc warnings > > > Task :javadoc > /Users/aalmiray/Downloads/groovy-3.0.0-alpha-3/src/main/java/org/codehaus/groovy/runtime/memoize/StampedCommonCache.java:39: > warning - Tag @link: can't find getAndPut(K, ValueProvider) in > org.codehaus.groovy.runtime.memoize.StampedCommonCache > /Users/aalmiray/Downloads/groovy-3.0.0-alpha-3/src/main/java/org/codehaus/groovy/runtime/memoize/StampedCommonCache.java:39: > warning - Tag @link: can't find getAndPut(K, ValueProvider, boolean) in > org.codehaus.groovy.runtime.memoize.StampedCommonCache > /Users/aalmiray/Downloads/groovy-3.0.0-alpha-3/src/main/java/org/codehaus/groovy/runtime/memoize/StampedCommonCache.java:59: > warning - Tag @link: reference not found: EvictionStrategy > /Users/aalmiray/Downloads/groovy-3.0.0-alpha-3/src/main/java/org/codehaus/groovy/runtime/memoize/UnlimitedConcurrentCache.java:194: > warning - Tag @link: reference not found: ValueProvider > /Users/aalmiray/Downloads/groovy-3.0.0-alpha-3/src/main/java/org/codehaus/groovy/ast/tools/GenericsUtils.java:783: > warning - Tag @link: malformed: > "#makeDeclaringAndActualGenericsTypeMap(ClassNode, ClassNode" > /Users/aalmiray/Downloads/groovy-3.0.0-alpha-3/src/main/java/org/codehaus/groovy/ast/tools/GenericsUtils.java:783: > warning - Tag @link: reference not found: > #makeDeclaringAndActualGenericsTypeMap(ClassNode, ClassNode > 6 warnings > > And quite the number of warnings related to asciidoc stylesheets. > > All tests passed. > > +1 (binding) > > ------------------------------------------- > Java Champion; Groovy Enthusiast > JCP EC Associate Seat > http://andresalmiray.com > http://www.linkedin.com/in/aalmiray > -- > What goes up, must come down. Ask any system administrator. > There are 10 types of people in the world: Those who understand binary, > and those who don't. > To understand recursion, we must first understand recursion. > > On Sat, Jun 23, 2018 at 6:15 AM, Paul King <pa...@asert.com.au> wrote: > >> >> Dear development community, >> >> I am happy to start the VOTE thread for a Groovy 3.0.0-alpha-3 release! >> This version is intended to be released at the same time as Groovy >> 2.6.0-alpha-4 >> and is the recommended next version of Groovy for users of JDK8 and above. >> >> This release includes 40 bug fixes/improvements as outlined in the >> changelog: >> >> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318123&version=12343061 >> >> Tag: >> https://git1-us-west.apache.org/repos/asf?p=groovy.git;a=tag;h=refs/tags/GROOVY_3_0_0_ALPHA_3 >> Tag commit id: f29fde1781c79c14ec6deb21bbf91913bc220c9f >> >> The artifacts to be voted on are located as follows (r27681). >> Source release: >> https://dist.apache.org/repos/dist/dev/groovy/3.0.0-alpha-3/sources >> Convenience binaries: >> https://dist.apache.org/repos/dist/dev/groovy/3.0.0-alpha-3/distribution >> >> Release artifacts are signed with a key from the following file: >> https://dist.apache.org/repos/dist/dev/groovy/KEYS >> >> Please vote on releasing this package as Apache Groovy 3.0.0-alpha-3. >> >> Reminder on ASF release approval requirements for PMC members: >> http://www.apache.org/legal/release-policy.html#release-approval >> Hints on validating checksums/signatures (but replace md5sum with >> sha256sum): >> https://www.apache.org/info/verification.html >> >> The vote is open for the next 72 hours and passes if a majority of at >> least three +1 PMC votes are cast. >> >> [ ] +1 Release Apache Groovy 3.0.0-alpha-3 >> [ ] 0 I don't have a strong opinion about this, but I assume it's ok >> [ ] -1 Do not release Apache Groovy 3.0.0-alpha-3 because... >> >> Here is my vote: >> >> +1 (binding) >> >> >
