[
https://issues.apache.org/jira/browse/GROOVY-9365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17026218#comment-17026218
]
Eric Milles commented on GROOVY-9365:
-------------------------------------
I don't think marking something as incubating means much. Basically once
something is part of the public API and is included in a release, we are stuck
with it. Incubating features are present in branches that can be checked out
and possibly edited by others before making their way to master. And not all
proposals will/should be accepted.
I would expect that any addition to the public API starts as a mailing list
proposal (optional) followed by a JIRA ticket followed by a Pull Request. The
PR should not be merged by the creator. Any other process is just railroading,
that is, it deprives the community of an opportunity to supply feedback and
consider alternatives.
Feedback should not be seen as unwanted, tiresome, argumentative or
exasperating. Critical review is an important step in a community-supported
project.
> Implement JavaShell to run Java code
> ------------------------------------
>
> Key: GROOVY-9365
> URL: https://issues.apache.org/jira/browse/GROOVY-9365
> Project: Groovy
> Issue Type: New Feature
> Reporter: Daniel Sun
> Assignee: Daniel Sun
> Priority: Major
> Fix For: 4.0.0-alpha-1
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Sometimes we need to compare the behaviour between Groovy and Java, so it's
> necessary to have a JavaShell to run pure Java code.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
