[
https://issues.apache.org/jira/browse/GROOVY-5363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17099356#comment-17099356
]
Paul King commented on GROOVY-5363:
-----------------------------------
It wouldn't be groovy.streaming.* since JPMS has a requirement that package
names aren't re-used across modules.
> MarkupBuilder and StreamingMarkupBuilder should merge
> -----------------------------------------------------
>
> Key: GROOVY-5363
> URL: https://issues.apache.org/jira/browse/GROOVY-5363
> Project: Groovy
> Issue Type: Bug
> Components: XML Processing
> Affects Versions: 2.0-beta-2
> Reporter: Dr. Russel Winder
> Priority: Major
> Labels: contrib
> Fix For: 4.x
>
>
> Currently there is MarkupBuilder and StreamingMarkupBuilder. These should be
> different implementations of the same interface. The choice of streaming or
> non-streaming should be a constructor parameter or static virtual constructor
> parameter, not a difference in (visible) class name.
> The design should factor in JDK8's stream capabilities.
> Assuming Groovy adds support for Java9 modules, this class would likely
> reside in a new XML module along with a revamped slurper/parser. While
> designing the module system or setting up the envisaged XML module aren't
> really within scope of this issue, it would be good to factor in the
> requirements we know for JDK9's module capabilities, i.e., it should have a
> unique package structure.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
