on the maven topic: for almost all cases there will be no classpath problem. the most common entry point into maven was the package for "brave" which was never released under an apache group id. the underlying libraries had very few call sites in comparison. the "bom" most commonly used was also never released.
the server itself was explicitly marked as not supported as a library, so there is not much impact to group ids there. many didn't upgrade to the ASF build according to support chatter. like most projects, getting folks to upgrade is a task in itself. main thing, we will take this liability of group ids on as a community in other words, and it is less a problem than being unable to control our repositories which is the current dilemma. you dont need to worry about this. On Tue, Jun 18, 2019, 4:13 AM sebb <seb...@gmail.com> wrote: > I agree it's not a block, but there is scope for some classpath confusion. > > If someone has an app that includes both the ASF and non-ASF Zipkin > jars, both will end up on the Maven classpath. > There is no way to tell which version of a particular class will end > up being loaded. > > A Maven relocation pom might help to ensure that only one version of > the jars ends up on the Maven classpath, but I've not tried that. > > The recommended procedure is to always ensure that there is a 1:1 > relationship between Maven coords and Java package name. > There can then be no chance of incompatible jars on the classpath. > > On Mon, 17 Jun 2019 at 14:17, Sheng Wu <wu.sheng.841...@gmail.com> wrote: > > > > Hi > > Zipkin doesn’t change the java package name, and had no plan to do that. > > We just changed the groupid, and are reverting it back to `io.zipkin`. > > > > So, I don’t see this as a block. > > > > Sheng Wu > > Apache Skywalking, ShardingSphere, Zipkin > > > > > > > > > 在 2019年6月17日，下午5:57，Christofer Dutz <christofer.d...@c-ware.de> 写道： > > > > > > But if you are releasing Maven artifacts, I would assume that you > change the group-ids to not start with "org.apache...." > > > and the packages should probably be changed too. But not 100% sure if > this is just a nice-to-have or a hard requirement. > > > And also I didn't check the coordinates or package structure of the > repo ... so just ignore me, if this all doesn't apply ;-) > > > > > > Chris > > > > > > > > > > > > Am 17.06.19, 11:52 schrieb "Sheng Wu" <wu.sheng.841...@gmail.com>: > > > > > > Hi Incubator. > > > > > > As a Zipkin incubator mentor, I am asking to make Zipkin all > repositories back to original OpenZipkin org as soon as possible. > > > > > > They have done a public ml vote, result is here[1]. > > > Also, with no transfer happened about Zipkin trademark, logo, > domain, so, there is no such thing about return the trademark or permission > of using Zipkin name. > > > > > > Zipkin is a big community and a lots of dependency out there are > waiting for release. > > > > > > I think there is nothing hold this transfer, right? > > > If so, please give a clear reply. The INFRA team is waiting at this > JIRA ticket[2]. > > > > > > > > > [1] > https://lists.apache.org/thread.html/fbeb254f569d9852e9740d55532ee338580287ec384e26c7d9107964@%3Cdev.zipkin.apache.org%3E > < > https://lists.apache.org/thread.html/fbeb254f569d9852e9740d55532ee338580287ec384e26c7d9107964@%3Cdev.zipkin.apache.org%3E > > > > > [2] https://issues.apache.org/jira/browse/INFRA-18604 < > https://issues.apache.org/jira/browse/INFRA-18604> > > > > > > > > > Sheng Wu > > > Apache Skywalking, ShardingSphere, Zipkin > > > > > > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > > For additional commands, e-mail: general-h...@incubator.apache.org > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > For additional commands, e-mail: general-h...@incubator.apache.org > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
