Just a possible alternative tweak to your idea. The Gradle project has an Incubating annotation that can be added to classes, methods, etc. That let's you pick a final package name now that won't need to change later and we can remove the @Incubating once things settle down. I don't mind having groovy as the top-level package but if you need something different we could use org.apache.groovy and org.apache.groovy.internal (instead of the current codehaus package hierarchy). Just a thought.
Cheers, Paul. On Tue, Aug 9, 2016 at 11:15 AM, John Wagenleitner <john.wagenleit...@gmail.com> wrote: > On Mon, Aug 8, 2016 at 7:34 AM, Jochen Theodorou <blackd...@gmx.org> wrote: >> >> >> >> On 07.08.2016 18:09, John Wagenleitner wrote: >>> >>> I think that's a good idea. Having a new package under the normal src >>> directory in master with some sort of feature toggle I think would be >>> good and would be easier for some to help test or contribute. >>> >>> With this work and with jigsaw coming it would be nice to release a 2.5 >>> and get master on a path to 3.0. >> >> >> Are you ok with me using the package prefixes groovy.experimental and >> org.apache.groovy.experimental ? >> > > > Those prefix names sound good to me, I think the word "experimental" as part > of the prefix makes the intent clear that the content of the packages will > be volatile and not something anyone should rely on.
