Re: Publishing Maven artifacts under third-party coordinates (was: Set up Nexus staging profile for Dubbo ...)

On Thu, May 10, 2018 at 3:25 PM, Roman Shaposhnik wrote: > On Thu, May 10, 2018 at 9:50 AM, Julian Hyde wrote: > > In other words, there are several ways to prove that a binary release is > WRONG but (to Greg’s point) there is no way to prove it RIGHT. >

Re: Publishing Maven artifacts under third-party coordinates (was: Set up Nexus staging profile for Dubbo ...)

On Thu, May 10, 2018 at 3:31 AM, Huxing Zhang wrote: > Hi, > > On Thu, May 10, 2018 at 3:59 PM, Willem Jiang > wrote: > > Is there any plan for going through the vote process of Binary file? > > Yes, binaries will also go through the vote process.

Re: Publishing Maven artifacts under third-party coordinates (was: Set up Nexus staging profile for Dubbo ...)

Please note: my initial message was not to question the release process. Merely that Infra was asked to enable provision of artifacts within Maven Central under a groupId that is not "org.apache". At the moment, we cannot / will-not work on making that possible. Infra doesn't involve itself in

Publishing Maven artifacts under third-party coordinates (was: Set up Nexus staging profile for Dubbo ...)

of course. The restriction merely applies to any compatibility/historical shims that are retained, to map the old-named packages over to new org.apache naming. Regards, Greg Stein Infrastructure Administrator, ASF On Tue, May 8, 2018 at 12:15 PM, Brian Fox <bri...@infinity.nu> wrote: > Was there d

Re: List volume and issue tracking

)PMC to choose which/how. But they cannot be sent to /dev/null. The above pattern generally provides the right breakdown for what information people what to monitor. Cheers, Greg Stein Infrastructure Administrator, ASF On Sat, Apr 7, 2018 at 10:22 PM, Ian Luo <ian@gmail.com> wrote: >