Personally, I think that it is good that moving from experimental to
non-experimental is a breaking change in the dependency - one has
backwards-incompatible changes and the other does not. If artifacts had
separate versioning we could use 0.x for this.
But biggest motivation for me are these:
Including the experimental suffix in artifact names is not a good idea
either because once we decide that it is not experimantal anymore this
will be a breaking change for users who will need then to update its
dependencies code. Also it is error-prone to use different mappings
for directories and
I missed Ken's input when writing my previous mail. Sorry.
So, to recap: I should remove "experimental" from any directory names, but
find an other way of configuring the artifact so that it still has
"experimental" in it's name.
Right?
On Sat, May 25, 2019 at 9:32 AM Jozsef Bartok wrote:
>
Yes, I'll gladly fix it, we aren't particularly keen to be labeled as
experimental either..
Btw. initially the "experimental" word was only in the Gradle module name,
but then there was some change
([BEAM-4046] decouple gradle project names and maven artifact ids - 4/2/19)
which kind of ended up
