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

[Greg Stein <gs...@gmail.com>]

Hi all,

I wanted to send a note that Infra has seen a couple requests from podlings
to publish under third-party Maven groupId coordinates (com.alibaba and
org.netbeans). Unless/until the Foundation owns these domains, we cannot
allow publishing under those coordinates.

Needless to say, we'll never own alibaba.com :p ... Maybe one day, we'll
get netbeans.org (what is the status on that?) ... But we cannot publish
convenience binaries to Maven Central before such time.

And please note that I said "convenience binaries". This is an important
point for the two podlings: the Foundation makes source code releases.
Period. Full stop. Both podlings can do that today -- there is nothing
inhibiting making such releases. ... What *cannot* be done is publishing
convenience binaries to those third-party coordinates.

The podlings will be able to publish under org.apache, 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 <br...@infinity.nu> wrote:

> Was there discussion somewhere that decided to allow an Apache project
> to publish coordinates using com.alibaba? From my perspective this is
> highly unusual for an ASF project. From a central point of view, the
> fact that com.alibaba is registered to publish from a completely
> different repo (oss.sonatype.org) this creates potential for confusion
> over the provenance of the artifacts.
>
> On Wed, May 2, 2018 at 9:30 PM, Chris Lambertus <cm...@apache.org> wrote:
> >
> >
> > On May 2, 2018, at 5:51 PM, Jun Liu <li...@apache.org> wrote:
> >
> > Hi,
> >
> > We are preparing for the first apache incubating release for dubbo, turns
> > out we lack of some nexus permissions, this blocks our process.
> >
> > Could someone help us please? Here is the ticket asking permissions :
> > https://issues.apache.org/jira/browse/INFRA-16451
> >
> > Best regards,
> > Jun
> >
> >
> >
> > I don’t know how to approach this when the groupID doesn’t match
> org.apache.
> > I’ve requested help from the Sonatype folks.
> >
> > -Chris
> >
>

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

[Von Gosling <vo...@apache.org>]

Hi,

Dubbo teams are making every endeavor to prepare the first formal release under the apache way, I also help teams to sweep away the binary and source liences problems :-) 


Best Regards,
Von Gosling

> 在 2018年5月10日，16:31，Huxing Zhang <hu...@apache.org> 写道：
> 
> Hi,
> 
> On Thu, May 10, 2018 at 3:59 PM, Willem Jiang <willem.jiang@gmail.com <ma...@gmail.com>> wrote:
>> Is there any plan for going through the vote process of Binary file?
> 
> Yes, binaries will also go through the vote process.
> 
>> Normally there are lots of work on the License files of Binary durning the
>> first release.
>> Maybe we should need to vote the binary file as well.
>> 
>> 
>> Willem Jiang
>> 
>> Blog: http://willemjiang.blogspot.com (English)
>>          http://jnn.iteye.com  (Chinese)
>> Twitter: willemjiang
>> Weibo: 姜宁willem
>> 
>> On Wed, May 9, 2018 at 4:34 PM, Huxing Zhang <hu...@apache.org> wrote:
>> 
>>> On Wed, May 9, 2018 at 3:35 PM, Bertrand Delacretaz
>>> <bd...@codeconsult.ch> wrote:
>>>> On Wed, May 9, 2018 at 3:44 AM, Huxing Zhang <hu...@apache.org> wrote:
>>>>> ...The maven artifact is the most significant for most of the Dubbo
>>>>> users, so we want to include a maven artifact in the release....
>>>> 
>>>> Binaries are NOT part of Apache Releases, as mentioned earlier in this
>>> thread.
>>> 
>>> Yes, we fully understood that.
>>> 
>>> Here what I mean "release" does not mean an Apache release, it is
>>> actually a "hybrid" release, which includes:
>>> 
>>> * source (following Apache release policy)
>>> * binary (it is optional but still following Apache release policy)
>>> * Maven artifacts under third-party coordinates (Non Apache release)
>>> 
>>>> 
>>>> Dubbo mentors, I think we need a clear description of how these
>>>> "hybrid" releases are done, to avoid any misunderstandings.
>>>> 
>>>> Justin mentioned in this thread that that's been discussed on your dev
>>>> list, so you probably just need to summarize that and include the URL
>>>> in your next Incubator report.
>>>> 
>>>> -Bertrand
>>> 
>>> --
>>> Best Regards！
>>> Huxing
>>> 
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>> For additional commands, e-mail: general-help@incubator.apache.org
>>> 
>>> 
> 
> -- 
> Best Regards！
> Huxing

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

[Ted Dunning <te...@gmail.com>]

There may be binary convenience artifacts, but let's not dignify them by
the name release. They aren't, after all.



On Thu, May 10, 2018 at 8:56 AM, Matt Sicker <bo...@gmail.com> wrote:

> I still minimally require proper gpg signatures on binary artifacts. The
> source artifacts are what get far more scrutiny, but the binaries are
> released on apache.org after all.
>
> On 10 May 2018 at 10:20, Roman Shaposhnik <ro...@shaposhnik.org> wrote:
>
> > On Thu, May 10, 2018 at 4:17 AM, sebb <se...@gmail.com> wrote:
> > > On 10 May 2018 at 11:37, Greg Stein <gs...@gmail.com> wrote:
> > >> On Thu, May 10, 2018 at 3:31 AM, Huxing Zhang <hu...@apache.org>
> > wrote:
> > >>
> > >>> Hi,
> > >>>
> > >>> On Thu, May 10, 2018 at 3:59 PM, Willem Jiang <
> willem.jiang@gmail.com>
> > >>> wrote:
> > >>> > Is there any plan for going through the vote process of Binary
> file?
> > >>>
> > >>> Yes, binaries will also go through the vote process.
> > >>
> > >>
> > >> No. It makes no sense.
> > >>
> > >> There is NO WAY to verify a binary. Even compiling from source to
> > binary on
> > >> your machine, and trying to compare against a target binary will
> > generally
> > >> fail since timestamps are embedded. Or maybe there are different
> > compilers
> > >> being used.
> > >>
> > >> The Foundation *never* votes on binaries, because the Foundation DOES
> > NOT
> > >> RELEASE BINARIES. The Foundation only votes/authorizes/releases source
> > >> code. REPEAT: only source code.
> > >>
> > >> Only source. Which is verifiable. Which has provenance.
> > >
> > > The LICENCE and NOTICE files that accompany the binary artifact are
> > > text, and IMO should be checked against the contents of the binary
> > > artifact.
> > > For example, if the binary bundles jars from other projects, the L&N
> > > need to agree with the bundled contents.
> >
> > +1000! That has been a well established practice in the Incubator and
> > as such I see no reason not to keep following it.
> >
> > In addition to that, a reasonable effort should be put into making sure
> > that the binary bundle doesn't drag in bits with incompatible licenses
> > (such as GPL). That's why verifying LICENSE in the binary bundle
> > is NOT a simple exersize of comparing it to the source bundle.
> >
> > Thanks,
> > Roman.
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> > For additional commands, e-mail: general-help@incubator.apache.org
> >
> >
>
>
> --
> Matt Sicker <bo...@gmail.com>
>

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

[Greg Stein <gs...@gmail.com>]

On Thu, May 10, 2018 at 3:25 PM, Roman Shaposhnik <ro...@shaposhnik.org>
wrote:

> On Thu, May 10, 2018 at 9:50 AM, Julian Hyde <jh...@apache.org> 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.
>
> That's actually a great way to put it.
>

Yeah, it really is. Props to Julian!

Cheers,
-g

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

[Justin Mclean <ju...@classsoftware.com>]

Hi,

>> As a mentor, I strongly advise against podlings making binary releases, especially for the first release.
>> It’s difficult enough to get L&N correct for source releases, and when a binary release is being make
>> at the same time with necessarily different L&N, the PPMC tend to get hopelessly confused.
> 
> Big +1 here. This is exactly what I advise my podlings as well.

Which was the advice given here but as most of their users use the binary not the source it was decided to do both.

Thanks,
Justin
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org

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

[Justin Mclean <ju...@classsoftware.com>]

Hi,

Looking at the release candidate just made both the license and notice for the source release and the connivance binary are going to be just about identical as there's only 2 3rd party jars included and none of the other jars contain 3rd party code (other than what is mentioned in LICENSE), both the 3rd party jars are apache licensed so it’s optional if they are mention in LICENSE. Nice if they are but not essential. [1] Neither have NOTICE files so there no effect on the Apache Dubbo’s NOTICE.

Thanks,
Justin

1. http://www.apache.org/dev/licensing-howto.html#alv2-dep
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org

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

[Justin Mclean <ju...@classsoftware.com>]

Hi,

Looking at the release candidate just made both the license and notice for the source release and the connivance binary are going to be just about identical as there's only 2 3rd party jars included and none of the other jars contain 3rd party code (other than what is mentioned in LICENSE), both the 3rd party jars are apache licensed so it’s optional if they are mention in LICENSE. Nice if they are but not essential. [1] Neither have NOTICE file so there no effect on the Apache Dubbo’s NOTICE.

Thanks,
Justin

1. http://www.apache.org/dev/licensing-howto.html#alv2-dep

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

[Justin Mclean <ju...@me.com>]

Hi,

>> As a mentor, I strongly advise against podlings making binary releases, especially for the first release.
>> It’s difficult enough to get L&N correct for source releases, and when a binary release is being make
>> at the same time with necessarily different L&N, the PPMC tend to get hopelessly confused.
> 
> Big +1 here. This is exactly what I advise my podlings as well.

Which was the advice given here but as most of their users use the binary not the source it was decided to do both.

Thanks,
Justin

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

[Greg Stein <gs...@gmail.com>]

On Thu, May 10, 2018 at 3:25 PM, Roman Shaposhnik <ro...@shaposhnik.org>
wrote:

> On Thu, May 10, 2018 at 9:50 AM, Julian Hyde <jh...@apache.org> 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.
>
> That's actually a great way to put it.
>

Yeah, it really is. Props to Julian!

Cheers,
-g

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

[Roman Shaposhnik <ro...@shaposhnik.org>]

On Thu, May 10, 2018 at 9:50 AM, Julian Hyde <jh...@apache.org> 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.

That's actually a great way to put it.

> As a mentor, I strongly advise against podlings making binary releases, especially for the first release.
> It’s difficult enough to get L&N correct for source releases, and when a binary release is being make
> at the same time with necessarily different L&N, the PPMC tend to get hopelessly confused.

Big +1 here. This is exactly what I advise my podlings as well.

Thanks,
Roman.

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org

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

[Bertrand Delacretaz <bd...@codeconsult.ch>]

On Thu, May 10, 2018 at 6:50 PM, Julian Hyde <jh...@apache.org> 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....

One useful thing that people could do with binary artifacts is to say
"I use the binary with sha256 digest XYZ and it works for me" - but
that doesn't make the Apache Releases, they are still unverifiable
binaries regardless.

-Bertrand

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

[Bertrand Delacretaz <bd...@codeconsult.ch>]

On Thu, May 10, 2018 at 6:50 PM, Julian Hyde <jh...@apache.org> 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....

One useful thing that people could do with binary artifacts is to say
"I use the binary with sha256 digest XYZ and it works for me" - but
that doesn't make the Apache Releases, they are still unverifiable
binaries regardless.

-Bertrand

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org

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

[Roman Shaposhnik <ro...@shaposhnik.org>]

On Thu, May 10, 2018 at 9:50 AM, Julian Hyde <jh...@apache.org> 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.

That's actually a great way to put it.

> As a mentor, I strongly advise against podlings making binary releases, especially for the first release.
> It’s difficult enough to get L&N correct for source releases, and when a binary release is being make
> at the same time with necessarily different L&N, the PPMC tend to get hopelessly confused.

Big +1 here. This is exactly what I advise my podlings as well.

Thanks,
Roman.

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

[Julian Hyde <jh...@apache.org>]

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.

As a mentor, I strongly advise against podlings making binary releases, especially for the first release. It’s difficult enough to get L&N correct for source releases, and when a binary release is being make at the same time with necessarily different L&N, the PPMC tend to get hopelessly confused.

Bundling artifacts is very common in the Java world, where shading is a best practice and is made very easy by maven.

Julian


> On May 10, 2018, at 9:06 AM, sebb <se...@gmail.com> wrote:
> 
> On 10 May 2018 at 16:56, Matt Sicker <bo...@gmail.com> wrote:
>> I still minimally require proper gpg signatures on binary artifacts. The
>> source artifacts are what get far more scrutiny, but the binaries are
>> released on apache.org after all.
> 
> +1
> 
> It may also be possible to verify that the binary package works.
> This obviously depends very much on the project.
> 
> In the case of Java code, it's possible to verify that the jars
> contain the expected package names.
> Also that the META-INF directory contains NOTICE and LICENSE files, etc.
> 
>> On 10 May 2018 at 10:20, Roman Shaposhnik <ro...@shaposhnik.org> wrote:
>> 
>>> On Thu, May 10, 2018 at 4:17 AM, sebb <se...@gmail.com> wrote:
>>>> On 10 May 2018 at 11:37, Greg Stein <gs...@gmail.com> wrote:
>>>>> On Thu, May 10, 2018 at 3:31 AM, Huxing Zhang <hu...@apache.org>
>>> wrote:
>>>>> 
>>>>>> Hi,
>>>>>> 
>>>>>> On Thu, May 10, 2018 at 3:59 PM, Willem Jiang <wi...@gmail.com>
>>>>>> wrote:
>>>>>>> Is there any plan for going through the vote process of Binary file?
>>>>>> 
>>>>>> Yes, binaries will also go through the vote process.
>>>>> 
>>>>> 
>>>>> No. It makes no sense.
>>>>> 
>>>>> There is NO WAY to verify a binary. Even compiling from source to
>>> binary on
>>>>> your machine, and trying to compare against a target binary will
>>> generally
>>>>> fail since timestamps are embedded. Or maybe there are different
>>> compilers
>>>>> being used.
>>>>> 
>>>>> The Foundation *never* votes on binaries, because the Foundation DOES
>>> NOT
>>>>> RELEASE BINARIES. The Foundation only votes/authorizes/releases source
>>>>> code. REPEAT: only source code.
>>>>> 
>>>>> Only source. Which is verifiable. Which has provenance.
>>>> 
>>>> The LICENCE and NOTICE files that accompany the binary artifact are
>>>> text, and IMO should be checked against the contents of the binary
>>>> artifact.
>>>> For example, if the binary bundles jars from other projects, the L&N
>>>> need to agree with the bundled contents.
>>> 
>>> +1000! That has been a well established practice in the Incubator and
>>> as such I see no reason not to keep following it.
>>> 
>>> In addition to that, a reasonable effort should be put into making sure
>>> that the binary bundle doesn't drag in bits with incompatible licenses
>>> (such as GPL). That's why verifying LICENSE in the binary bundle
>>> is NOT a simple exersize of comparing it to the source bundle.
>>> 
>>> Thanks,
>>> Roman.
>>> 
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>> For additional commands, e-mail: general-help@incubator.apache.org
>>> 
>>> 
>> 
>> 
>> --
>> Matt Sicker <bo...@gmail.com>
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org

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

[Julian Hyde <jh...@apache.org>]

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.

As a mentor, I strongly advise against podlings making binary releases, especially for the first release. It’s difficult enough to get L&N correct for source releases, and when a binary release is being make at the same time with necessarily different L&N, the PPMC tend to get hopelessly confused.

Bundling artifacts is very common in the Java world, where shading is a best practice and is made very easy by maven.

Julian


> On May 10, 2018, at 9:06 AM, sebb <se...@gmail.com> wrote:
> 
> On 10 May 2018 at 16:56, Matt Sicker <bo...@gmail.com> wrote:
>> I still minimally require proper gpg signatures on binary artifacts. The
>> source artifacts are what get far more scrutiny, but the binaries are
>> released on apache.org after all.
> 
> +1
> 
> It may also be possible to verify that the binary package works.
> This obviously depends very much on the project.
> 
> In the case of Java code, it's possible to verify that the jars
> contain the expected package names.
> Also that the META-INF directory contains NOTICE and LICENSE files, etc.
> 
>> On 10 May 2018 at 10:20, Roman Shaposhnik <ro...@shaposhnik.org> wrote:
>> 
>>> On Thu, May 10, 2018 at 4:17 AM, sebb <se...@gmail.com> wrote:
>>>> On 10 May 2018 at 11:37, Greg Stein <gs...@gmail.com> wrote:
>>>>> On Thu, May 10, 2018 at 3:31 AM, Huxing Zhang <hu...@apache.org>
>>> wrote:
>>>>> 
>>>>>> Hi,
>>>>>> 
>>>>>> On Thu, May 10, 2018 at 3:59 PM, Willem Jiang <wi...@gmail.com>
>>>>>> wrote:
>>>>>>> Is there any plan for going through the vote process of Binary file?
>>>>>> 
>>>>>> Yes, binaries will also go through the vote process.
>>>>> 
>>>>> 
>>>>> No. It makes no sense.
>>>>> 
>>>>> There is NO WAY to verify a binary. Even compiling from source to
>>> binary on
>>>>> your machine, and trying to compare against a target binary will
>>> generally
>>>>> fail since timestamps are embedded. Or maybe there are different
>>> compilers
>>>>> being used.
>>>>> 
>>>>> The Foundation *never* votes on binaries, because the Foundation DOES
>>> NOT
>>>>> RELEASE BINARIES. The Foundation only votes/authorizes/releases source
>>>>> code. REPEAT: only source code.
>>>>> 
>>>>> Only source. Which is verifiable. Which has provenance.
>>>> 
>>>> The LICENCE and NOTICE files that accompany the binary artifact are
>>>> text, and IMO should be checked against the contents of the binary
>>>> artifact.
>>>> For example, if the binary bundles jars from other projects, the L&N
>>>> need to agree with the bundled contents.
>>> 
>>> +1000! That has been a well established practice in the Incubator and
>>> as such I see no reason not to keep following it.
>>> 
>>> In addition to that, a reasonable effort should be put into making sure
>>> that the binary bundle doesn't drag in bits with incompatible licenses
>>> (such as GPL). That's why verifying LICENSE in the binary bundle
>>> is NOT a simple exersize of comparing it to the source bundle.
>>> 
>>> Thanks,
>>> Roman.
>>> 
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>> For additional commands, e-mail: general-help@incubator.apache.org
>>> 
>>> 
>> 
>> 
>> --
>> Matt Sicker <bo...@gmail.com>
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
> 

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

[sebb <se...@gmail.com>]

On 10 May 2018 at 16:56, Matt Sicker <bo...@gmail.com> wrote:
> I still minimally require proper gpg signatures on binary artifacts. The
> source artifacts are what get far more scrutiny, but the binaries are
> released on apache.org after all.

+1

It may also be possible to verify that the binary package works.
This obviously depends very much on the project.

In the case of Java code, it's possible to verify that the jars
contain the expected package names.
Also that the META-INF directory contains NOTICE and LICENSE files, etc.

> On 10 May 2018 at 10:20, Roman Shaposhnik <ro...@shaposhnik.org> wrote:
>
>> On Thu, May 10, 2018 at 4:17 AM, sebb <se...@gmail.com> wrote:
>> > On 10 May 2018 at 11:37, Greg Stein <gs...@gmail.com> wrote:
>> >> On Thu, May 10, 2018 at 3:31 AM, Huxing Zhang <hu...@apache.org>
>> wrote:
>> >>
>> >>> Hi,
>> >>>
>> >>> On Thu, May 10, 2018 at 3:59 PM, Willem Jiang <wi...@gmail.com>
>> >>> wrote:
>> >>> > Is there any plan for going through the vote process of Binary file?
>> >>>
>> >>> Yes, binaries will also go through the vote process.
>> >>
>> >>
>> >> No. It makes no sense.
>> >>
>> >> There is NO WAY to verify a binary. Even compiling from source to
>> binary on
>> >> your machine, and trying to compare against a target binary will
>> generally
>> >> fail since timestamps are embedded. Or maybe there are different
>> compilers
>> >> being used.
>> >>
>> >> The Foundation *never* votes on binaries, because the Foundation DOES
>> NOT
>> >> RELEASE BINARIES. The Foundation only votes/authorizes/releases source
>> >> code. REPEAT: only source code.
>> >>
>> >> Only source. Which is verifiable. Which has provenance.
>> >
>> > The LICENCE and NOTICE files that accompany the binary artifact are
>> > text, and IMO should be checked against the contents of the binary
>> > artifact.
>> > For example, if the binary bundles jars from other projects, the L&N
>> > need to agree with the bundled contents.
>>
>> +1000! That has been a well established practice in the Incubator and
>> as such I see no reason not to keep following it.
>>
>> In addition to that, a reasonable effort should be put into making sure
>> that the binary bundle doesn't drag in bits with incompatible licenses
>> (such as GPL). That's why verifying LICENSE in the binary bundle
>> is NOT a simple exersize of comparing it to the source bundle.
>>
>> Thanks,
>> Roman.
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> For additional commands, e-mail: general-help@incubator.apache.org
>>
>>
>
>
> --
> Matt Sicker <bo...@gmail.com>

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

[sebb <se...@gmail.com>]

On 10 May 2018 at 16:56, Matt Sicker <bo...@gmail.com> wrote:
> I still minimally require proper gpg signatures on binary artifacts. The
> source artifacts are what get far more scrutiny, but the binaries are
> released on apache.org after all.

+1

It may also be possible to verify that the binary package works.
This obviously depends very much on the project.

In the case of Java code, it's possible to verify that the jars
contain the expected package names.
Also that the META-INF directory contains NOTICE and LICENSE files, etc.

> On 10 May 2018 at 10:20, Roman Shaposhnik <ro...@shaposhnik.org> wrote:
>
>> On Thu, May 10, 2018 at 4:17 AM, sebb <se...@gmail.com> wrote:
>> > On 10 May 2018 at 11:37, Greg Stein <gs...@gmail.com> wrote:
>> >> On Thu, May 10, 2018 at 3:31 AM, Huxing Zhang <hu...@apache.org>
>> wrote:
>> >>
>> >>> Hi,
>> >>>
>> >>> On Thu, May 10, 2018 at 3:59 PM, Willem Jiang <wi...@gmail.com>
>> >>> wrote:
>> >>> > Is there any plan for going through the vote process of Binary file?
>> >>>
>> >>> Yes, binaries will also go through the vote process.
>> >>
>> >>
>> >> No. It makes no sense.
>> >>
>> >> There is NO WAY to verify a binary. Even compiling from source to
>> binary on
>> >> your machine, and trying to compare against a target binary will
>> generally
>> >> fail since timestamps are embedded. Or maybe there are different
>> compilers
>> >> being used.
>> >>
>> >> The Foundation *never* votes on binaries, because the Foundation DOES
>> NOT
>> >> RELEASE BINARIES. The Foundation only votes/authorizes/releases source
>> >> code. REPEAT: only source code.
>> >>
>> >> Only source. Which is verifiable. Which has provenance.
>> >
>> > The LICENCE and NOTICE files that accompany the binary artifact are
>> > text, and IMO should be checked against the contents of the binary
>> > artifact.
>> > For example, if the binary bundles jars from other projects, the L&N
>> > need to agree with the bundled contents.
>>
>> +1000! That has been a well established practice in the Incubator and
>> as such I see no reason not to keep following it.
>>
>> In addition to that, a reasonable effort should be put into making sure
>> that the binary bundle doesn't drag in bits with incompatible licenses
>> (such as GPL). That's why verifying LICENSE in the binary bundle
>> is NOT a simple exersize of comparing it to the source bundle.
>>
>> Thanks,
>> Roman.
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> For additional commands, e-mail: general-help@incubator.apache.org
>>
>>
>
>
> --
> Matt Sicker <bo...@gmail.com>

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org

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

[Ted Dunning <te...@gmail.com>]

There may be binary convenience artifacts, but let's not dignify them by
the name release. They aren't, after all.



On Thu, May 10, 2018 at 8:56 AM, Matt Sicker <bo...@gmail.com> wrote:

> I still minimally require proper gpg signatures on binary artifacts. The
> source artifacts are what get far more scrutiny, but the binaries are
> released on apache.org after all.
>
> On 10 May 2018 at 10:20, Roman Shaposhnik <ro...@shaposhnik.org> wrote:
>
> > On Thu, May 10, 2018 at 4:17 AM, sebb <se...@gmail.com> wrote:
> > > On 10 May 2018 at 11:37, Greg Stein <gs...@gmail.com> wrote:
> > >> On Thu, May 10, 2018 at 3:31 AM, Huxing Zhang <hu...@apache.org>
> > wrote:
> > >>
> > >>> Hi,
> > >>>
> > >>> On Thu, May 10, 2018 at 3:59 PM, Willem Jiang <
> willem.jiang@gmail.com>
> > >>> wrote:
> > >>> > Is there any plan for going through the vote process of Binary
> file?
> > >>>
> > >>> Yes, binaries will also go through the vote process.
> > >>
> > >>
> > >> No. It makes no sense.
> > >>
> > >> There is NO WAY to verify a binary. Even compiling from source to
> > binary on
> > >> your machine, and trying to compare against a target binary will
> > generally
> > >> fail since timestamps are embedded. Or maybe there are different
> > compilers
> > >> being used.
> > >>
> > >> The Foundation *never* votes on binaries, because the Foundation DOES
> > NOT
> > >> RELEASE BINARIES. The Foundation only votes/authorizes/releases source
> > >> code. REPEAT: only source code.
> > >>
> > >> Only source. Which is verifiable. Which has provenance.
> > >
> > > The LICENCE and NOTICE files that accompany the binary artifact are
> > > text, and IMO should be checked against the contents of the binary
> > > artifact.
> > > For example, if the binary bundles jars from other projects, the L&N
> > > need to agree with the bundled contents.
> >
> > +1000! That has been a well established practice in the Incubator and
> > as such I see no reason not to keep following it.
> >
> > In addition to that, a reasonable effort should be put into making sure
> > that the binary bundle doesn't drag in bits with incompatible licenses
> > (such as GPL). That's why verifying LICENSE in the binary bundle
> > is NOT a simple exersize of comparing it to the source bundle.
> >
> > Thanks,
> > Roman.
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> > For additional commands, e-mail: general-help@incubator.apache.org
> >
> >
>
>
> --
> Matt Sicker <bo...@gmail.com>
>

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

[Matt Sicker <bo...@gmail.com>]

I still minimally require proper gpg signatures on binary artifacts. The
source artifacts are what get far more scrutiny, but the binaries are
released on apache.org after all.

On 10 May 2018 at 10:20, Roman Shaposhnik <ro...@shaposhnik.org> wrote:

> On Thu, May 10, 2018 at 4:17 AM, sebb <se...@gmail.com> wrote:
> > On 10 May 2018 at 11:37, Greg Stein <gs...@gmail.com> wrote:
> >> On Thu, May 10, 2018 at 3:31 AM, Huxing Zhang <hu...@apache.org>
> wrote:
> >>
> >>> Hi,
> >>>
> >>> On Thu, May 10, 2018 at 3:59 PM, Willem Jiang <wi...@gmail.com>
> >>> wrote:
> >>> > Is there any plan for going through the vote process of Binary file?
> >>>
> >>> Yes, binaries will also go through the vote process.
> >>
> >>
> >> No. It makes no sense.
> >>
> >> There is NO WAY to verify a binary. Even compiling from source to
> binary on
> >> your machine, and trying to compare against a target binary will
> generally
> >> fail since timestamps are embedded. Or maybe there are different
> compilers
> >> being used.
> >>
> >> The Foundation *never* votes on binaries, because the Foundation DOES
> NOT
> >> RELEASE BINARIES. The Foundation only votes/authorizes/releases source
> >> code. REPEAT: only source code.
> >>
> >> Only source. Which is verifiable. Which has provenance.
> >
> > The LICENCE and NOTICE files that accompany the binary artifact are
> > text, and IMO should be checked against the contents of the binary
> > artifact.
> > For example, if the binary bundles jars from other projects, the L&N
> > need to agree with the bundled contents.
>
> +1000! That has been a well established practice in the Incubator and
> as such I see no reason not to keep following it.
>
> In addition to that, a reasonable effort should be put into making sure
> that the binary bundle doesn't drag in bits with incompatible licenses
> (such as GPL). That's why verifying LICENSE in the binary bundle
> is NOT a simple exersize of comparing it to the source bundle.
>
> Thanks,
> Roman.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>


-- 
Matt Sicker <bo...@gmail.com>

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

[Matt Sicker <bo...@gmail.com>]

I still minimally require proper gpg signatures on binary artifacts. The
source artifacts are what get far more scrutiny, but the binaries are
released on apache.org after all.

On 10 May 2018 at 10:20, Roman Shaposhnik <ro...@shaposhnik.org> wrote:

> On Thu, May 10, 2018 at 4:17 AM, sebb <se...@gmail.com> wrote:
> > On 10 May 2018 at 11:37, Greg Stein <gs...@gmail.com> wrote:
> >> On Thu, May 10, 2018 at 3:31 AM, Huxing Zhang <hu...@apache.org>
> wrote:
> >>
> >>> Hi,
> >>>
> >>> On Thu, May 10, 2018 at 3:59 PM, Willem Jiang <wi...@gmail.com>
> >>> wrote:
> >>> > Is there any plan for going through the vote process of Binary file?
> >>>
> >>> Yes, binaries will also go through the vote process.
> >>
> >>
> >> No. It makes no sense.
> >>
> >> There is NO WAY to verify a binary. Even compiling from source to
> binary on
> >> your machine, and trying to compare against a target binary will
> generally
> >> fail since timestamps are embedded. Or maybe there are different
> compilers
> >> being used.
> >>
> >> The Foundation *never* votes on binaries, because the Foundation DOES
> NOT
> >> RELEASE BINARIES. The Foundation only votes/authorizes/releases source
> >> code. REPEAT: only source code.
> >>
> >> Only source. Which is verifiable. Which has provenance.
> >
> > The LICENCE and NOTICE files that accompany the binary artifact are
> > text, and IMO should be checked against the contents of the binary
> > artifact.
> > For example, if the binary bundles jars from other projects, the L&N
> > need to agree with the bundled contents.
>
> +1000! That has been a well established practice in the Incubator and
> as such I see no reason not to keep following it.
>
> In addition to that, a reasonable effort should be put into making sure
> that the binary bundle doesn't drag in bits with incompatible licenses
> (such as GPL). That's why verifying LICENSE in the binary bundle
> is NOT a simple exersize of comparing it to the source bundle.
>
> Thanks,
> Roman.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>


-- 
Matt Sicker <bo...@gmail.com>

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

[Roman Shaposhnik <ro...@shaposhnik.org>]

On Thu, May 10, 2018 at 4:17 AM, sebb <se...@gmail.com> wrote:
> On 10 May 2018 at 11:37, Greg Stein <gs...@gmail.com> wrote:
>> On Thu, May 10, 2018 at 3:31 AM, Huxing Zhang <hu...@apache.org> wrote:
>>
>>> Hi,
>>>
>>> On Thu, May 10, 2018 at 3:59 PM, Willem Jiang <wi...@gmail.com>
>>> wrote:
>>> > Is there any plan for going through the vote process of Binary file?
>>>
>>> Yes, binaries will also go through the vote process.
>>
>>
>> No. It makes no sense.
>>
>> There is NO WAY to verify a binary. Even compiling from source to binary on
>> your machine, and trying to compare against a target binary will generally
>> fail since timestamps are embedded. Or maybe there are different compilers
>> being used.
>>
>> The Foundation *never* votes on binaries, because the Foundation DOES NOT
>> RELEASE BINARIES. The Foundation only votes/authorizes/releases source
>> code. REPEAT: only source code.
>>
>> Only source. Which is verifiable. Which has provenance.
>
> The LICENCE and NOTICE files that accompany the binary artifact are
> text, and IMO should be checked against the contents of the binary
> artifact.
> For example, if the binary bundles jars from other projects, the L&N
> need to agree with the bundled contents.

+1000! That has been a well established practice in the Incubator and
as such I see no reason not to keep following it.

In addition to that, a reasonable effort should be put into making sure
that the binary bundle doesn't drag in bits with incompatible licenses
(such as GPL). That's why verifying LICENSE in the binary bundle
is NOT a simple exersize of comparing it to the source bundle.

Thanks,
Roman.

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

[Roman Shaposhnik <ro...@shaposhnik.org>]

On Thu, May 10, 2018 at 4:17 AM, sebb <se...@gmail.com> wrote:
> On 10 May 2018 at 11:37, Greg Stein <gs...@gmail.com> wrote:
>> On Thu, May 10, 2018 at 3:31 AM, Huxing Zhang <hu...@apache.org> wrote:
>>
>>> Hi,
>>>
>>> On Thu, May 10, 2018 at 3:59 PM, Willem Jiang <wi...@gmail.com>
>>> wrote:
>>> > Is there any plan for going through the vote process of Binary file?
>>>
>>> Yes, binaries will also go through the vote process.
>>
>>
>> No. It makes no sense.
>>
>> There is NO WAY to verify a binary. Even compiling from source to binary on
>> your machine, and trying to compare against a target binary will generally
>> fail since timestamps are embedded. Or maybe there are different compilers
>> being used.
>>
>> The Foundation *never* votes on binaries, because the Foundation DOES NOT
>> RELEASE BINARIES. The Foundation only votes/authorizes/releases source
>> code. REPEAT: only source code.
>>
>> Only source. Which is verifiable. Which has provenance.
>
> The LICENCE and NOTICE files that accompany the binary artifact are
> text, and IMO should be checked against the contents of the binary
> artifact.
> For example, if the binary bundles jars from other projects, the L&N
> need to agree with the bundled contents.

+1000! That has been a well established practice in the Incubator and
as such I see no reason not to keep following it.

In addition to that, a reasonable effort should be put into making sure
that the binary bundle doesn't drag in bits with incompatible licenses
(such as GPL). That's why verifying LICENSE in the binary bundle
is NOT a simple exersize of comparing it to the source bundle.

Thanks,
Roman.

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org

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

[sebb <se...@gmail.com>]

On 10 May 2018 at 11:37, Greg Stein <gs...@gmail.com> wrote:
> On Thu, May 10, 2018 at 3:31 AM, Huxing Zhang <hu...@apache.org> wrote:
>
>> Hi,
>>
>> On Thu, May 10, 2018 at 3:59 PM, Willem Jiang <wi...@gmail.com>
>> wrote:
>> > Is there any plan for going through the vote process of Binary file?
>>
>> Yes, binaries will also go through the vote process.
>
>
> No. It makes no sense.
>
> There is NO WAY to verify a binary. Even compiling from source to binary on
> your machine, and trying to compare against a target binary will generally
> fail since timestamps are embedded. Or maybe there are different compilers
> being used.
>
> The Foundation *never* votes on binaries, because the Foundation DOES NOT
> RELEASE BINARIES. The Foundation only votes/authorizes/releases source
> code. REPEAT: only source code.
>
> Only source. Which is verifiable. Which has provenance.

The LICENCE and NOTICE files that accompany the binary artifact are
text, and IMO should be checked against the contents of the binary
artifact.
For example, if the binary bundles jars from other projects, the L&N
need to agree with the bundled contents.

> Regards,
> -g
> (Member, skipping my Infra hat)

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

[Justin Mclean <ju...@me.com>]

Hi,

> There is NO WAY to verify a binary. Even compiling from source to binary on
> your machine, and trying to compare against a target binary will generally
> fail since timestamps are embedded. Or maybe there are different compilers
> being used.

As per ASF policy a connivance binary can be release as the same time [1] and it needs to comply with license and notice policy [2].

It usually very easy to check a binary (and I’ve done it 100’s of time) by uncompress the jar or just editing it directly to see what is bundled inside it.

Thanks,
Justin

1. http://www.apache.org/legal/release-policy.html#compiled-packages
2. http://www.apache.org/dev/licensing-howto.html#binary

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

[Justin Mclean <ju...@classsoftware.com>]

Hi,

> There is NO WAY to verify a binary. Even compiling from source to binary on
> your machine, and trying to compare against a target binary will generally
> fail since timestamps are embedded. Or maybe there are different compilers
> being used.

As per ASF policy a connivance binary can be release as the same time [1] and it needs to comply with license and notice policy [2].

It usually very easy to check a binary (and I’ve done it 100’s of time) by uncompress the jar or just editing it directly to see what is bundled inside it.

Thanks,
Justin

1. http://www.apache.org/legal/release-policy.html#compiled-packages
2. http://www.apache.org/dev/licensing-howto.html#binary
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org

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

[sebb <se...@gmail.com>]

On 10 May 2018 at 11:37, Greg Stein <gs...@gmail.com> wrote:
> On Thu, May 10, 2018 at 3:31 AM, Huxing Zhang <hu...@apache.org> wrote:
>
>> Hi,
>>
>> On Thu, May 10, 2018 at 3:59 PM, Willem Jiang <wi...@gmail.com>
>> wrote:
>> > Is there any plan for going through the vote process of Binary file?
>>
>> Yes, binaries will also go through the vote process.
>
>
> No. It makes no sense.
>
> There is NO WAY to verify a binary. Even compiling from source to binary on
> your machine, and trying to compare against a target binary will generally
> fail since timestamps are embedded. Or maybe there are different compilers
> being used.
>
> The Foundation *never* votes on binaries, because the Foundation DOES NOT
> RELEASE BINARIES. The Foundation only votes/authorizes/releases source
> code. REPEAT: only source code.
>
> Only source. Which is verifiable. Which has provenance.

The LICENCE and NOTICE files that accompany the binary artifact are
text, and IMO should be checked against the contents of the binary
artifact.
For example, if the binary bundles jars from other projects, the L&N
need to agree with the bundled contents.

> Regards,
> -g
> (Member, skipping my Infra hat)

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org

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

[Greg Stein <gs...@gmail.com>]

On Thu, May 10, 2018 at 3:31 AM, Huxing Zhang <hu...@apache.org> wrote:

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


No. It makes no sense.

There is NO WAY to verify a binary. Even compiling from source to binary on
your machine, and trying to compare against a target binary will generally
fail since timestamps are embedded. Or maybe there are different compilers
being used.

The Foundation *never* votes on binaries, because the Foundation DOES NOT
RELEASE BINARIES. The Foundation only votes/authorizes/releases source
code. REPEAT: only source code.

Only source. Which is verifiable. Which has provenance.

Regards,
-g
(Member, skipping my Infra hat)

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

[Greg Stein <gs...@gmail.com>]

On Thu, May 10, 2018 at 3:31 AM, Huxing Zhang <hu...@apache.org> wrote:

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


No. It makes no sense.

There is NO WAY to verify a binary. Even compiling from source to binary on
your machine, and trying to compare against a target binary will generally
fail since timestamps are embedded. Or maybe there are different compilers
being used.

The Foundation *never* votes on binaries, because the Foundation DOES NOT
RELEASE BINARIES. The Foundation only votes/authorizes/releases source
code. REPEAT: only source code.

Only source. Which is verifiable. Which has provenance.

Regards,
-g
(Member, skipping my Infra hat)

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

[Huxing Zhang <hu...@apache.org>]

Hi,

On Thu, May 10, 2018 at 3:59 PM, Willem Jiang <wi...@gmail.com> wrote:
> Is there any plan for going through the vote process of Binary file?

Yes, binaries will also go through the vote process.

> Normally there are lots of work on the License files of Binary durning the
> first release.
> Maybe we should need to vote the binary file as well.
>
>
> Willem Jiang
>
> Blog: http://willemjiang.blogspot.com (English)
>           http://jnn.iteye.com  (Chinese)
> Twitter: willemjiang
> Weibo: 姜宁willem
>
> On Wed, May 9, 2018 at 4:34 PM, Huxing Zhang <hu...@apache.org> wrote:
>
>> On Wed, May 9, 2018 at 3:35 PM, Bertrand Delacretaz
>> <bd...@codeconsult.ch> wrote:
>> > On Wed, May 9, 2018 at 3:44 AM, Huxing Zhang <hu...@apache.org> wrote:
>> >> ...The maven artifact is the most significant for most of the Dubbo
>> >> users, so we want to include a maven artifact in the release....
>> >
>> > Binaries are NOT part of Apache Releases, as mentioned earlier in this
>> thread.
>>
>> Yes, we fully understood that.
>>
>> Here what I mean "release" does not mean an Apache release, it is
>> actually a "hybrid" release, which includes:
>>
>> * source (following Apache release policy)
>> * binary (it is optional but still following Apache release policy)
>> * Maven artifacts under third-party coordinates (Non Apache release)
>>
>> >
>> > Dubbo mentors, I think we need a clear description of how these
>> > "hybrid" releases are done, to avoid any misunderstandings.
>> >
>> > Justin mentioned in this thread that that's been discussed on your dev
>> > list, so you probably just need to summarize that and include the URL
>> > in your next Incubator report.
>> >
>> > -Bertrand
>>
>> --
>> Best Regards！
>> Huxing
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> For additional commands, e-mail: general-help@incubator.apache.org
>>
>>

-- 
Best Regards！
Huxing

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org

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

[Huxing Zhang <hu...@apache.org>]

Hi,

On Thu, May 10, 2018 at 3:59 PM, Willem Jiang <wi...@gmail.com> wrote:
> Is there any plan for going through the vote process of Binary file?

Yes, binaries will also go through the vote process.

> Normally there are lots of work on the License files of Binary durning the
> first release.
> Maybe we should need to vote the binary file as well.
>
>
> Willem Jiang
>
> Blog: http://willemjiang.blogspot.com (English)
>           http://jnn.iteye.com  (Chinese)
> Twitter: willemjiang
> Weibo: 姜宁willem
>
> On Wed, May 9, 2018 at 4:34 PM, Huxing Zhang <hu...@apache.org> wrote:
>
>> On Wed, May 9, 2018 at 3:35 PM, Bertrand Delacretaz
>> <bd...@codeconsult.ch> wrote:
>> > On Wed, May 9, 2018 at 3:44 AM, Huxing Zhang <hu...@apache.org> wrote:
>> >> ...The maven artifact is the most significant for most of the Dubbo
>> >> users, so we want to include a maven artifact in the release....
>> >
>> > Binaries are NOT part of Apache Releases, as mentioned earlier in this
>> thread.
>>
>> Yes, we fully understood that.
>>
>> Here what I mean "release" does not mean an Apache release, it is
>> actually a "hybrid" release, which includes:
>>
>> * source (following Apache release policy)
>> * binary (it is optional but still following Apache release policy)
>> * Maven artifacts under third-party coordinates (Non Apache release)
>>
>> >
>> > Dubbo mentors, I think we need a clear description of how these
>> > "hybrid" releases are done, to avoid any misunderstandings.
>> >
>> > Justin mentioned in this thread that that's been discussed on your dev
>> > list, so you probably just need to summarize that and include the URL
>> > in your next Incubator report.
>> >
>> > -Bertrand
>>
>> --
>> Best Regards！
>> Huxing
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> For additional commands, e-mail: general-help@incubator.apache.org
>>
>>

-- 
Best Regards！
Huxing

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

[Justin Mclean <ju...@gmail.com>]

Hi,,
IMO it only the source release that is important and unless we find a
serious issue like GPL licensed software in the binary all is good.
Particularly if you call out that they may be issues with the binary
license and notice files as part of the vote email. This is an incubating
project and it's not expected to get everything right first go.

Thanks,
Justin

On Thu., 10 May 2018, 5:59 pm Willem Jiang, <wi...@gmail.com> wrote:

> Is there any plan for going through the vote process of Binary file?
> Normally there are lots of work on the License files of Binary durning the
> first release.
> Maybe we should need to vote the binary file as well.
>
>
> Willem Jiang
>
> Blog: http://willemjiang.blogspot.com (English)
>           http://jnn.iteye.com  (Chinese)
> Twitter: willemjiang
> Weibo: 姜宁willem
>
> On Wed, May 9, 2018 at 4:34 PM, Huxing Zhang <hu...@apache.org> wrote:
>
> > On Wed, May 9, 2018 at 3:35 PM, Bertrand Delacretaz
> > <bd...@codeconsult.ch> wrote:
> > > On Wed, May 9, 2018 at 3:44 AM, Huxing Zhang <hu...@apache.org>
> wrote:
> > >> ...The maven artifact is the most significant for most of the Dubbo
> > >> users, so we want to include a maven artifact in the release....
> > >
> > > Binaries are NOT part of Apache Releases, as mentioned earlier in this
> > thread.
> >
> > Yes, we fully understood that.
> >
> > Here what I mean "release" does not mean an Apache release, it is
> > actually a "hybrid" release, which includes:
> >
> > * source (following Apache release policy)
> > * binary (it is optional but still following Apache release policy)
> > * Maven artifacts under third-party coordinates (Non Apache release)
> >
> > >
> > > Dubbo mentors, I think we need a clear description of how these
> > > "hybrid" releases are done, to avoid any misunderstandings.
> > >
> > > Justin mentioned in this thread that that's been discussed on your dev
> > > list, so you probably just need to summarize that and include the URL
> > > in your next Incubator report.
> > >
> > > -Bertrand
> >
> > --
> > Best Regards！
> > Huxing
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> > For additional commands, e-mail: general-help@incubator.apache.org
> >
> >
>

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

[Willem Jiang <wi...@gmail.com>]

Is there any plan for going through the vote process of Binary file?
Normally there are lots of work on the License files of Binary durning the
first release.
Maybe we should need to vote the binary file as well.


Willem Jiang

Blog: http://willemjiang.blogspot.com (English)
          http://jnn.iteye.com  (Chinese)
Twitter: willemjiang
Weibo: 姜宁willem

On Wed, May 9, 2018 at 4:34 PM, Huxing Zhang <hu...@apache.org> wrote:

> On Wed, May 9, 2018 at 3:35 PM, Bertrand Delacretaz
> <bd...@codeconsult.ch> wrote:
> > On Wed, May 9, 2018 at 3:44 AM, Huxing Zhang <hu...@apache.org> wrote:
> >> ...The maven artifact is the most significant for most of the Dubbo
> >> users, so we want to include a maven artifact in the release....
> >
> > Binaries are NOT part of Apache Releases, as mentioned earlier in this
> thread.
>
> Yes, we fully understood that.
>
> Here what I mean "release" does not mean an Apache release, it is
> actually a "hybrid" release, which includes:
>
> * source (following Apache release policy)
> * binary (it is optional but still following Apache release policy)
> * Maven artifacts under third-party coordinates (Non Apache release)
>
> >
> > Dubbo mentors, I think we need a clear description of how these
> > "hybrid" releases are done, to avoid any misunderstandings.
> >
> > Justin mentioned in this thread that that's been discussed on your dev
> > list, so you probably just need to summarize that and include the URL
> > in your next Incubator report.
> >
> > -Bertrand
>
> --
> Best Regards！
> Huxing
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>

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

[Willem Jiang <wi...@gmail.com>]

Is there any plan for going through the vote process of Binary file?
Normally there are lots of work on the License files of Binary durning the
first release.
Maybe we should need to vote the binary file as well.


Willem Jiang

Blog: http://willemjiang.blogspot.com (English)
          http://jnn.iteye.com  (Chinese)
Twitter: willemjiang
Weibo: 姜宁willem

On Wed, May 9, 2018 at 4:34 PM, Huxing Zhang <hu...@apache.org> wrote:

> On Wed, May 9, 2018 at 3:35 PM, Bertrand Delacretaz
> <bd...@codeconsult.ch> wrote:
> > On Wed, May 9, 2018 at 3:44 AM, Huxing Zhang <hu...@apache.org> wrote:
> >> ...The maven artifact is the most significant for most of the Dubbo
> >> users, so we want to include a maven artifact in the release....
> >
> > Binaries are NOT part of Apache Releases, as mentioned earlier in this
> thread.
>
> Yes, we fully understood that.
>
> Here what I mean "release" does not mean an Apache release, it is
> actually a "hybrid" release, which includes:
>
> * source (following Apache release policy)
> * binary (it is optional but still following Apache release policy)
> * Maven artifacts under third-party coordinates (Non Apache release)
>
> >
> > Dubbo mentors, I think we need a clear description of how these
> > "hybrid" releases are done, to avoid any misunderstandings.
> >
> > Justin mentioned in this thread that that's been discussed on your dev
> > list, so you probably just need to summarize that and include the URL
> > in your next Incubator report.
> >
> > -Bertrand
>
> --
> Best Regards！
> Huxing
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>

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

[Greg Stein <gs...@gmail.com>]

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
community (release) processes, so please go about your business :-)


On Wed, May 9, 2018 at 3:34 AM, Huxing Zhang <hu...@apache.org> wrote:

> On Wed, May 9, 2018 at 3:35 PM, Bertrand Delacretaz
> <bd...@codeconsult.ch> wrote:
> > On Wed, May 9, 2018 at 3:44 AM, Huxing Zhang <hu...@apache.org> wrote:
> >> ...The maven artifact is the most significant for most of the Dubbo
> >> users, so we want to include a maven artifact in the release....
> >
> > Binaries are NOT part of Apache Releases, as mentioned earlier in this
> thread.
>
> Yes, we fully understood that.
>
> Here what I mean "release" does not mean an Apache release, it is
> actually a "hybrid" release, which includes:
>
> * source (following Apache release policy)
> * binary (it is optional but still following Apache release policy)
> * Maven artifacts under third-party coordinates (Non Apache release)
>
> >
> > Dubbo mentors, I think we need a clear description of how these
> > "hybrid" releases are done, to avoid any misunderstandings.
> >
> > Justin mentioned in this thread that that's been discussed on your dev
> > list, so you probably just need to summarize that and include the URL
> > in your next Incubator report.
> >
> > -Bertrand
>
> --
> Best Regards！
> Huxing
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>

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

[Greg Stein <gs...@gmail.com>]

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
community (release) processes, so please go about your business :-)


On Wed, May 9, 2018 at 3:34 AM, Huxing Zhang <hu...@apache.org> wrote:

> On Wed, May 9, 2018 at 3:35 PM, Bertrand Delacretaz
> <bd...@codeconsult.ch> wrote:
> > On Wed, May 9, 2018 at 3:44 AM, Huxing Zhang <hu...@apache.org> wrote:
> >> ...The maven artifact is the most significant for most of the Dubbo
> >> users, so we want to include a maven artifact in the release....
> >
> > Binaries are NOT part of Apache Releases, as mentioned earlier in this
> thread.
>
> Yes, we fully understood that.
>
> Here what I mean "release" does not mean an Apache release, it is
> actually a "hybrid" release, which includes:
>
> * source (following Apache release policy)
> * binary (it is optional but still following Apache release policy)
> * Maven artifacts under third-party coordinates (Non Apache release)
>
> >
> > Dubbo mentors, I think we need a clear description of how these
> > "hybrid" releases are done, to avoid any misunderstandings.
> >
> > Justin mentioned in this thread that that's been discussed on your dev
> > list, so you probably just need to summarize that and include the URL
> > in your next Incubator report.
> >
> > -Bertrand
>
> --
> Best Regards！
> Huxing
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>

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

[Huxing Zhang <hu...@apache.org>]

On Wed, May 9, 2018 at 3:35 PM, Bertrand Delacretaz
<bd...@codeconsult.ch> wrote:
> On Wed, May 9, 2018 at 3:44 AM, Huxing Zhang <hu...@apache.org> wrote:
>> ...The maven artifact is the most significant for most of the Dubbo
>> users, so we want to include a maven artifact in the release....
>
> Binaries are NOT part of Apache Releases, as mentioned earlier in this thread.

Yes, we fully understood that.

Here what I mean "release" does not mean an Apache release, it is
actually a "hybrid" release, which includes:

* source (following Apache release policy)
* binary (it is optional but still following Apache release policy)
* Maven artifacts under third-party coordinates (Non Apache release)

>
> Dubbo mentors, I think we need a clear description of how these
> "hybrid" releases are done, to avoid any misunderstandings.
>
> Justin mentioned in this thread that that's been discussed on your dev
> list, so you probably just need to summarize that and include the URL
> in your next Incubator report.
>
> -Bertrand

-- 
Best Regards！
Huxing

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

[Justin Mclean <ju...@classsoftware.com>]

Hi,

>> ...The maven artifact is the most significant for most of the Dubbo
>> users, so we want to include a maven artifact in the release....
> 
> Binaries are NOT part of Apache Releases, as mentioned earlier in this thread.

Apache Dubbo is aware of that and it has been made clear on the dev list several times. The context above is that it’s users are not aware of that (currently) and not all want to compile from source. Other projects (ie Apache Flex or Apache Open Office) face the same issue, although probably to a greater extent.

> Dubbo mentors, I think we need a clear description of how these
> "hybrid" releases are done, to avoid any misunderstandings.

The release process will be documented as part of the release to document and help future release managers.

Here’s two threads on the release [1][2] that might help. (Note most of the emails there predates this discussion).

Thanks,
Justin 

1. https://lists.apache.org/thread.html/114d04c1aaa8141ba99ef14bc75081c512989b55c9b0a81636704fa6@%3Cdev.dubbo.apache.org%3E
2. https://lists.apache.org/thread.html/5265f8fc0315270f5b908f38a4e47c856784bc39214af6ffa3efcdf4@%3Cdev.dubbo.apache.org%3E

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

[Huxing Zhang <hu...@apache.org>]

On Wed, May 9, 2018 at 3:35 PM, Bertrand Delacretaz
<bd...@codeconsult.ch> wrote:
> On Wed, May 9, 2018 at 3:44 AM, Huxing Zhang <hu...@apache.org> wrote:
>> ...The maven artifact is the most significant for most of the Dubbo
>> users, so we want to include a maven artifact in the release....
>
> Binaries are NOT part of Apache Releases, as mentioned earlier in this thread.

Yes, we fully understood that.

Here what I mean "release" does not mean an Apache release, it is
actually a "hybrid" release, which includes:

* source (following Apache release policy)
* binary (it is optional but still following Apache release policy)
* Maven artifacts under third-party coordinates (Non Apache release)

>
> Dubbo mentors, I think we need a clear description of how these
> "hybrid" releases are done, to avoid any misunderstandings.
>
> Justin mentioned in this thread that that's been discussed on your dev
> list, so you probably just need to summarize that and include the URL
> in your next Incubator report.
>
> -Bertrand

-- 
Best Regards！
Huxing

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org

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

[Justin Mclean <ju...@classsoftware.com>]

Hi,

>> ...The maven artifact is the most significant for most of the Dubbo
>> users, so we want to include a maven artifact in the release....
> 
> Binaries are NOT part of Apache Releases, as mentioned earlier in this thread.

Apache Dubbo is aware of that and it has been made clear on the dev list several times. The context above is that it’s users are not aware of that (currently) and not all want to compile from source. Other projects (ie Apache Flex or Apache Open Office) face the same issue, although probably to a greater extent.

> Dubbo mentors, I think we need a clear description of how these
> "hybrid" releases are done, to avoid any misunderstandings.

The release process will be documented as part of the release to document and help future release managers.

Here’s two threads on the release [1][2] that might help. (Note most of the emails there predates this discussion).

Thanks,
Justin 

1. https://lists.apache.org/thread.html/114d04c1aaa8141ba99ef14bc75081c512989b55c9b0a81636704fa6@%3Cdev.dubbo.apache.org%3E
2. https://lists.apache.org/thread.html/5265f8fc0315270f5b908f38a4e47c856784bc39214af6ffa3efcdf4@%3Cdev.dubbo.apache.org%3E
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org

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

[Bertrand Delacretaz <bd...@codeconsult.ch>]

On Wed, May 9, 2018 at 3:44 AM, Huxing Zhang <hu...@apache.org> wrote:
> ...The maven artifact is the most significant for most of the Dubbo
> users, so we want to include a maven artifact in the release....

Binaries are NOT part of Apache Releases, as mentioned earlier in this thread.

Dubbo mentors, I think we need a clear description of how these
"hybrid" releases are done, to avoid any misunderstandings.

Justin mentioned in this thread that that's been discussed on your dev
list, so you probably just need to summarize that and include the URL
in your next Incubator report.

-Bertrand

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org

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

[Bertrand Delacretaz <bd...@codeconsult.ch>]

On Wed, May 9, 2018 at 3:44 AM, Huxing Zhang <hu...@apache.org> wrote:
> ...The maven artifact is the most significant for most of the Dubbo
> users, so we want to include a maven artifact in the release....

Binaries are NOT part of Apache Releases, as mentioned earlier in this thread.

Dubbo mentors, I think we need a clear description of how these
"hybrid" releases are done, to avoid any misunderstandings.

Justin mentioned in this thread that that's been discussed on your dev
list, so you probably just need to summarize that and include the URL
in your next Incubator report.

-Bertrand

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

[Huxing Zhang <hu...@apache.org>]

Hi,

I would like to clarify more on a wider range.

Dubbo will always trying to follow the ASF release policy as much as possible.

The reason why the group id remains com.alibaba is for compatibility
purpose. It might take some time for Dubbo to to change the group id
as well as package name, we've already had some idea, and the work is
expected to be done later.

While Dubbo has already had a very large user base, one of our primary
concern it to keep a stable release cycle, therefore a release with
existing group id is needed.

The maven artifact is the most significant for most of the Dubbo
users, so we want to include a maven artifact in the release. Since
ASF does not allow third-party coordinates to be published, so we
proposed to make the source (as well as binary) release to Apache
mirror system, and then publish the maven artifact to nexus with our
exiting approach.

On Wed, May 9, 2018 at 8:08 AM, Justin Mclean <ju...@classsoftware.com> wrote:
> Hi,
>
>> But nothing prevents Alibaba from publishing under coordinates that they
>> control.
>>
>> It needs to be clear however that it is alibaba publishing there, not
>> Apache.
>
> The has been discussed on list with Dubbo and that’s the approach they are going to take with their first release. They are aware will need to change the package name at some later point.
>
> Thanks,
> Justin
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>

-- 
Best Regards！
Huxing

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org

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

[Huxing Zhang <hu...@apache.org>]

Hi,

I would like to clarify more on a wider range.

Dubbo will always trying to follow the ASF release policy as much as possible.

The reason why the group id remains com.alibaba is for compatibility
purpose. It might take some time for Dubbo to to change the group id
as well as package name, we've already had some idea, and the work is
expected to be done later.

While Dubbo has already had a very large user base, one of our primary
concern it to keep a stable release cycle, therefore a release with
existing group id is needed.

The maven artifact is the most significant for most of the Dubbo
users, so we want to include a maven artifact in the release. Since
ASF does not allow third-party coordinates to be published, so we
proposed to make the source (as well as binary) release to Apache
mirror system, and then publish the maven artifact to nexus with our
exiting approach.

On Wed, May 9, 2018 at 8:08 AM, Justin Mclean <ju...@classsoftware.com> wrote:
> Hi,
>
>> But nothing prevents Alibaba from publishing under coordinates that they
>> control.
>>
>> It needs to be clear however that it is alibaba publishing there, not
>> Apache.
>
> The has been discussed on list with Dubbo and that’s the approach they are going to take with their first release. They are aware will need to change the package name at some later point.
>
> Thanks,
> Justin
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>

-- 
Best Regards！
Huxing

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

[Justin Mclean <ju...@classsoftware.com>]

Hi,

> Maybe the first release should be Apache for the source with Alibaba making the binary release through their current Maven release process.

Which is my understanding of what they are going to do. They were also going to vote on the binary to check it’s OK but not have that as part of the ASF release. I think we’re all on the same page here.

Thanks,
Justin

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

[Justin Mclean <ju...@classsoftware.com>]

Hi,

> Maybe the first release should be Apache for the source with Alibaba making the binary release through their current Maven release process.

Which is my understanding of what they are going to do. They were also going to vote on the binary to check it’s OK but not have that as part of the ASF release. I think we’re all on the same page here.

Thanks,
Justin
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org

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

[Dave Fisher <da...@comcast.net>]

Hi -

Sent from my iPhone

> On May 8, 2018, at 5:08 PM, Justin Mclean <ju...@classsoftware.com> wrote:
> 
> Hi,
> 
>> But nothing prevents Alibaba from publishing under coordinates that they
>> control.
>> 
>> It needs to be clear however that it is alibaba publishing there, not
>> Apache.
> 
> The has been discussed on list with Dubbo and that’s the approach they are going to take with their first release. They are aware will need to change the package name at some later point.

Maybe the first release should be Apache for the source with Alibaba making the binary release through their current Maven release process.

Regards,
Dave

> 
> Thanks,
> Justin
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
> 

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

[Dave Fisher <da...@comcast.net>]

Hi -

Sent from my iPhone

> On May 8, 2018, at 5:08 PM, Justin Mclean <ju...@classsoftware.com> wrote:
> 
> Hi,
> 
>> But nothing prevents Alibaba from publishing under coordinates that they
>> control.
>> 
>> It needs to be clear however that it is alibaba publishing there, not
>> Apache.
> 
> The has been discussed on list with Dubbo and that’s the approach they are going to take with their first release. They are aware will need to change the package name at some later point.

Maybe the first release should be Apache for the source with Alibaba making the binary release through their current Maven release process.

Regards,
Dave

> 
> Thanks,
> Justin
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org

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

[Justin Mclean <ju...@classsoftware.com>]

Hi,

> But nothing prevents Alibaba from publishing under coordinates that they
> control.
> 
> It needs to be clear however that it is alibaba publishing there, not
> Apache.

The has been discussed on list with Dubbo and that’s the approach they are going to take with their first release. They are aware will need to change the package name at some later point.

Thanks,
Justin

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

[Justin Mclean <ju...@classsoftware.com>]

Hi,

> But nothing prevents Alibaba from publishing under coordinates that they
> control.
> 
> It needs to be clear however that it is alibaba publishing there, not
> Apache.

The has been discussed on list with Dubbo and that’s the approach they are going to take with their first release. They are aware will need to change the package name at some later point.

Thanks,
Justin
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org

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

[Ted Dunning <te...@gmail.com>]

Greg has it all correct.

But nothing prevents Alibaba from publishing under coordinates that they
control.

It needs to be clear however that it is alibaba publishing there, not
Apache.

On Tue, May 8, 2018, 13:56 Greg Stein <gs...@gmail.com> wrote:

> Hi all,
>
> I wanted to send a note that Infra has seen a couple requests from podlings
> to publish under third-party Maven groupId coordinates (com.alibaba and
> org.netbeans). Unless/until the Foundation owns these domains, we cannot
> allow publishing under those coordinates.
>
> Needless to say, we'll never own alibaba.com :p ... Maybe one day, we'll
> get netbeans.org (what is the status on that?) ... But we cannot publish
> convenience binaries to Maven Central before such time.
>
> And please note that I said "convenience binaries". This is an important
> point for the two podlings: the Foundation makes source code releases.
> Period. Full stop. Both podlings can do that today -- there is nothing
> inhibiting making such releases. ... What *cannot* be done is publishing
> convenience binaries to those third-party coordinates.
>
> The podlings will be able to publish under org.apache, 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 <br...@infinity.nu> wrote:
>
> > Was there discussion somewhere that decided to allow an Apache project
> > to publish coordinates using com.alibaba? From my perspective this is
> > highly unusual for an ASF project. From a central point of view, the
> > fact that com.alibaba is registered to publish from a completely
> > different repo (oss.sonatype.org) this creates potential for confusion
> > over the provenance of the artifacts.
> >
> > On Wed, May 2, 2018 at 9:30 PM, Chris Lambertus <cm...@apache.org> wrote:
> > >
> > >
> > > On May 2, 2018, at 5:51 PM, Jun Liu <li...@apache.org> wrote:
> > >
> > > Hi,
> > >
> > > We are preparing for the first apache incubating release for dubbo,
> turns
> > > out we lack of some nexus permissions, this blocks our process.
> > >
> > > Could someone help us please? Here is the ticket asking permissions :
> > > https://issues.apache.org/jira/browse/INFRA-16451
> > >
> > > Best regards,
> > > Jun
> > >
> > >
> > >
> > > I don’t know how to approach this when the groupID doesn’t match
> > org.apache.
> > > I’ve requested help from the Sonatype folks.
> > >
> > > -Chris
> > >
> >
>

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

[Ted Dunning <te...@gmail.com>]

Greg has it all correct.

But nothing prevents Alibaba from publishing under coordinates that they
control.

It needs to be clear however that it is alibaba publishing there, not
Apache.

On Tue, May 8, 2018, 13:56 Greg Stein <gs...@gmail.com> wrote:

> Hi all,
>
> I wanted to send a note that Infra has seen a couple requests from podlings
> to publish under third-party Maven groupId coordinates (com.alibaba and
> org.netbeans). Unless/until the Foundation owns these domains, we cannot
> allow publishing under those coordinates.
>
> Needless to say, we'll never own alibaba.com :p ... Maybe one day, we'll
> get netbeans.org (what is the status on that?) ... But we cannot publish
> convenience binaries to Maven Central before such time.
>
> And please note that I said "convenience binaries". This is an important
> point for the two podlings: the Foundation makes source code releases.
> Period. Full stop. Both podlings can do that today -- there is nothing
> inhibiting making such releases. ... What *cannot* be done is publishing
> convenience binaries to those third-party coordinates.
>
> The podlings will be able to publish under org.apache, 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 <br...@infinity.nu> wrote:
>
> > Was there discussion somewhere that decided to allow an Apache project
> > to publish coordinates using com.alibaba? From my perspective this is
> > highly unusual for an ASF project. From a central point of view, the
> > fact that com.alibaba is registered to publish from a completely
> > different repo (oss.sonatype.org) this creates potential for confusion
> > over the provenance of the artifacts.
> >
> > On Wed, May 2, 2018 at 9:30 PM, Chris Lambertus <cm...@apache.org> wrote:
> > >
> > >
> > > On May 2, 2018, at 5:51 PM, Jun Liu <li...@apache.org> wrote:
> > >
> > > Hi,
> > >
> > > We are preparing for the first apache incubating release for dubbo,
> turns
> > > out we lack of some nexus permissions, this blocks our process.
> > >
> > > Could someone help us please? Here is the ticket asking permissions :
> > > https://issues.apache.org/jira/browse/INFRA-16451
> > >
> > > Best regards,
> > > Jun
> > >
> > >
> > >
> > > I don’t know how to approach this when the groupID doesn’t match
> > org.apache.
> > > I’ve requested help from the Sonatype folks.
> > >
> > > -Chris
> > >
> >
>

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

[Eric Barboni <sk...@apache.org>]

Hi 
I found information here (hope this is enough)
https://central.sonatype.org/pages/requirements.html
I'm not sure of the dev section

Maybe and idea is to have a flag to generate a parent pom and to have each pom inherit instead of generating lines of xml replicating the same info.

Best Regards
Eric

-----Message d'origine-----
De : John McDonnell <mc...@gmail.com> 
Envoyé : vendredi 7 décembre 2018 19:19
À : dev@netbeans.incubator.apache.org
Objet : Re: Publishing Maven Artifacts under netbeans.org (was Re: Publishing Maven artifacts under third-party coordinates (was: Set up Nexus staging profile for Dubbo ...))

Hi Eric,

Forgive my ignorance I previously tried finding the minimum pom requirements but couldn't find them anywhere. I guess I was looking up the wrong thing.

If you can send on a link then I might have time this weekend to modify the plug-in to support additional elements like license,scm etc as properties

John

On Fri 7 Dec 2018, 12:15 Eric Barboni <skygo@apache.org wrote:

> Hi,
>  I will say ASAP, because I also need it but currently I focus on the 
> build of the website for the tools because code donation is done but 
> has no new home.
>
>  Concerning the artefacts, the issue is that generated pom doesn’t 
> have the minimum requierement. (Licences sections, url section, and 
> scm section)
>
>  If anyone have the possibility to help on this point it would be very 
> helpful it's time consuming to wait for artifacts to be generated.
>
> An icomplete PR is under progress for buildscript doing
> apidoc+mavenartifacts
>
> Best Regards
>
> Eric
> -----Message d'origine-----
> De : Jean-Marc Borer <jm...@gmail.com> Envoyé : vendredi 7 décembre 
> 2018 11:09 À : dev@netbeans.incubator.apache.org Objet : Re: 
> Publishing Maven Artifacts under netbeans.org (was Re:
> Publishing Maven artifacts under third-party coordinates (was: Set up 
> Nexus staging profile for Dubbo ...))
>
> Hi Eric,
>
> And when do you think, will this be completed (rough estimation is ok)?
>
> Cheers,
>
> JM
>
> On Tue, Nov 13, 2018 at 12:11 AM Eric Barboni <sk...@apache.org> wrote:
>
> > HI,
> >  There is also a issue there:
> > https://issues.apache.org/jira/browse/INFRA-17127
> >
> > but artefact pom.xml that was done on bits.netbeans.org/nexus are 
> > not complete enough to get to maven central.
> > So
> > 1) We had the possibility to get the nb-repository-plugin (and other 
> > related mavenutils) to be handled by Apache NetBeans (incubating) To 
> > complete we need to have documentation site for those plugin to 
> > allow redirect and end properly the code donation.
> > -- documentation is part of the whole NetBeans website
> > (bits.netbeans.org) that will contains javadocs so we are discussing 
> > on that on the mailing now (topic
> > bits.netbeans.org/Javadoc/mavenutils)
> >
> > Then ...
> > RELEASE90) We need to use the release90 branch and do a full build 
> > with all artefacts (Javadoc, source) to allow nb-repository-plugin 
> > to take items and create the repository. (We need to ensure pom.xml
> quality).
> > Apache NetBeans 9.0 will have a limited set of artefacts compared to
> > 8.2 because it will contains only what was donated at the time.
> >
> > RELEASE100) We will do the same with Apache NetBeans 10, artefact 
> > set will be bigger than 9.0 but limited compared to 8.2 , as the 
> > plugin will be ready, it will go faster to achieve
> >
> > dev-SNAPSHOT)Parallel to that, we also will need a SNAPSHOT version 
> > for the nighly builds.
> >
> >  Regards
> > Eric
> >
> > -----Message d'origine-----
> > De : Ryan Cuprak <rc...@gmail.com> Envoyé : lundi 12 novembre 2018 
> > 23:28 À : dev@netbeans.incubator.apache.org Objet : Re: Publishing 
> > Maven Artifacts under netbeans.org (was Re:
> > Publishing Maven artifacts under third-party coordinates (was: Set 
> > up Nexus staging profile for Dubbo ...))
> >
> > I just did a search and there is a task in JIRA:
> >
> > https://issues.apache.org/jira/browse/NETBEANS-467?jql=project%20%3D
> > %2
> > 0NETBEANS%20AND%20text%20~%20nexus
> >
> > I think the task needs to be split-up into sub-tasks with the first 
> > task being a proposal for how it would be implemented.
> >
> > -Ryan
> >
> > > On Nov 12, 2018, at 11:16 PM, Antonio <an...@vieiro.net> wrote:
> > >
> > > What needs to be done is learning what needs to be done :-)
> > >
> > > I'll report on my findings.
> > >
> > > Cheers,
> > > Antonio
> > >
> > > El 12/11/18 a las 23:14, Geertjan Wielenga escribió:
> > >> You are right. If you know what needs to be done, do it.
> > >> Gj
> > >> On Monday, November 12, 2018, Antonio <an...@vieiro.net> wrote:
> > >>> Hi all,
> > >>>
> > >>> Recovering this old thread of may 2018...
> > >>>
> > >>> Since the ASF now owns the netbeans.org domain, that means that 
> > >>> we can now publish artifacts to Maven Central using the 
> > >>> netbeans.org
> > domain.
> > >>>
> > >>> So there's no need to host a NetBeans Nexus Repository ourselves 
> > >>> under http://bits.netbeans.org/nexus (serving binaries out of 
> > >>> the Apache Mirror System is problematic, AFAIK).
> > >>>
> > >>> Am I right?
> > >>>
> > >>> Thanks,
> > >>> Antonio
> > >>>
> > >>>
> > >>> El 10/5/18 a las 0:30, Emilian Bold escribió:
> > >>>
> > >>>> So, no official Maven artifacts until Apache gets the 
> > >>>> netbeans.org domain too?
> > >>>>
> > >>>> I wonder, since people would still have to edit their pom.xml 
> > >>>> files to update the version -- would it really be so hard to 
> > >>>> switch to org.apache groupIDs?
> > >>>>
> > >>>> We still keep the package names, etc. just change these 
> > >>>> Maven-specific coordinates.
> > >>>>
> > >>>> --emi
> > >>>>
> > >>>> ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
> > >>>>
> > >>>> On 8 May 2018 8:56 PM, Greg Stein <gs...@gmail.com> wrote:
> > >>>>
> > >>>> Hi all,
> > >>>>>
> > >>>>> I wanted to send a note that Infra has seen a couple requests 
> > >>>>> from podlings
> > >>>>>
> > >>>>> to publish under third-party Maven groupId coordinates 
> > >>>>> (com.alibaba and
> > >>>>>
> > >>>>> org.netbeans). Unless/until the Foundation owns these domains, 
> > >>>>> we cannot
> > >>>>>
> > >>>>> allow publishing under those coordinates.
> > >>>>>
> > >>>>> Needless to say, we'll never own alibaba.com :p ... Maybe one 
> > >>>>> day, we'll
> > >>>>>
> > >>>>> get netbeans.org (what is the status on that?) ... But we 
> > >>>>> cannot publish
> > >>>>>
> > >>>>> convenience binaries to Maven Central before such time.
> > >>>>>
> > >>>>> And please note that I said "convenience binaries". This is an 
> > >>>>> important
> > >>>>>
> > >>>>> point for the two podlings: the Foundation makes source code
> > releases.
> > >>>>>
> > >>>>> Period. Full stop. Both podlings can do that today -- there is 
> > >>>>> nothing
> > >>>>>
> > >>>>> inhibiting making such releases. ... What cannot be done is 
> > >>>>> publishing
> > >>>>>
> > >>>>> convenience binaries to those third-party coordinates.
> > >>>>>
> > >>>>> The podlings will be able to publish under org.apache, 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 brianf@infinity.nu
> wrote:
> > >>>>>
> > >>>>> Was there discussion somewhere that decided to allow an Apache 
> > >>>>> project
> > >>>>>>
> > >>>>>> to publish coordinates using com.alibaba? From my perspective 
> > >>>>>> this is
> > >>>>>>
> > >>>>>> highly unusual for an ASF project. From a central point of 
> > >>>>>> view, the
> > >>>>>>
> > >>>>>> fact that com.alibaba is registered to publish from a 
> > >>>>>> completely
> > >>>>>>
> > >>>>>> different repo (oss.sonatype.org) this creates potential for 
> > >>>>>> confusion
> > >>>>>>
> > >>>>>> over the provenance of the artifacts.
> > >>>>>>
> > >>>>>> On Wed, May 2, 2018 at 9:30 PM, Chris Lambertus 
> > >>>>>> cml@apache.org
> > wrote:
> > >>>>>>
> > >>>>>> On May 2, 2018, at 5:51 PM, Jun Liu liujun@apache.org wrote:
> > >>>>>>>
> > >>>>>>> Hi,
> > >>>>>>>
> > >>>>>>> We are preparing for the first apache incubating release for 
> > >>>>>>> dubbo, turns
> > >>>>>>>
> > >>>>>>> out we lack of some nexus permissions, this blocks our process.
> > >>>>>>>
> > >>>>>>> Could someone help us please? Here is the ticket asking
> > permissions :
> > >>>>>>>
> > >>>>>>> https://issues.apache.org/jira/browse/INFRA-16451
> > >>>>>>>
> > >>>>>>> Best regards,
> > >>>>>>>
> > >>>>>>> Jun
> > >>>>>>>
> > >>>>>>> I don’t know how to approach this when the groupID doesn’t 
> > >>>>>>> match
> > >>>>>>>
> > >>>>>>> org.apache.
> > >>>>>>>
> > >>>>>>> I’ve requested help from the Sonatype folks.
> > >>>>>>>
> > >>>>>>> -Chris
> > >>>>>>>
> > >>>>>>
> > >>>>
> > >>>>
> > >>>> ---------------------------------------------------------------
> > >>>> --
> > >>>> --
> > >>>> -- To unsubscribe, e-mail:
> > >>>> dev-unsubscribe@netbeans.incubator.apache.org
> > >>>> For additional commands, e-mail:
> > >>>> dev-help@netbeans.incubator.apache.org
> > >>>>
> > >>>> For further information about the NetBeans mailing lists, visit:
> > >>>> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+li
> > >>>> st
> > >>>> s
> > >>>>
> > >>>>
> > >>>>
> > >>>>
> > >>> ----------------------------------------------------------------
> > >>> --
> > >>> --
> > >>> - To unsubscribe, e-mail:
> > >>> dev-unsubscribe@netbeans.incubator.apache.org
> > >>> For additional commands, e-mail:
> > >>> dev-help@netbeans.incubator.apache.org
> > >>>
> > >>> For further information about the NetBeans mailing lists, visit:
> > >>> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lis
> > >>> ts
> > >>>
> > >>>
> > >>>
> > >>>
> > >
> > > ------------------------------------------------------------------
> > > --
> > > - To unsubscribe, e-mail:
> > > dev-unsubscribe@netbeans.incubator.apache.org
> > > For additional commands, e-mail:
> > > dev-help@netbeans.incubator.apache.org
> > >
> > > For further information about the NetBeans mailing lists, visit:
> > > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
> > >
> > >
> > >
> >
> >
> > --------------------------------------------------------------------
> > - To unsubscribe, e-mail: 
> > dev-unsubscribe@netbeans.incubator.apache.org
> > For additional commands, e-mail:
> > dev-help@netbeans.incubator.apache.org
> >
> > For further information about the NetBeans mailing lists, visit:
> > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
> >
> >
> >
> >
> >
> > --------------------------------------------------------------------
> > - To unsubscribe, e-mail: 
> > dev-unsubscribe@netbeans.incubator.apache.org
> > For additional commands, e-mail:
> > dev-help@netbeans.incubator.apache.org
> >
> > For further information about the NetBeans mailing lists, visit:
> > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
> >
> >
> >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
> For additional commands, e-mail: 
> dev-help@netbeans.incubator.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>
>


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
For additional commands, e-mail: dev-help@netbeans.incubator.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

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

[John McDonnell <mc...@gmail.com>]

Hi Eric,

Forgive my ignorance I previously tried finding the minimum pom
requirements but couldn't find them anywhere. I guess I was looking up the
wrong thing.

If you can send on a link then I might have time this weekend to modify the
plug-in to support additional elements like license,scm etc as properties

John

On Fri 7 Dec 2018, 12:15 Eric Barboni <skygo@apache.org wrote:

> Hi,
>  I will say ASAP, because I also need it but currently I focus on the
> build of the website for the tools because code donation is done but has no
> new home.
>
>  Concerning the artefacts, the issue is that generated pom doesn’t have
> the minimum requierement. (Licences sections, url section, and scm section)
>
>  If anyone have the possibility to help on this point it would be very
> helpful it's time consuming to wait for artifacts to be generated.
>
> An icomplete PR is under progress for buildscript doing
> apidoc+mavenartifacts
>
> Best Regards
>
> Eric
> -----Message d'origine-----
> De : Jean-Marc Borer <jm...@gmail.com>
> Envoyé : vendredi 7 décembre 2018 11:09
> À : dev@netbeans.incubator.apache.org
> Objet : Re: Publishing Maven Artifacts under netbeans.org (was Re:
> Publishing Maven artifacts under third-party coordinates (was: Set up Nexus
> staging profile for Dubbo ...))
>
> Hi Eric,
>
> And when do you think, will this be completed (rough estimation is ok)?
>
> Cheers,
>
> JM
>
> On Tue, Nov 13, 2018 at 12:11 AM Eric Barboni <sk...@apache.org> wrote:
>
> > HI,
> >  There is also a issue there:
> > https://issues.apache.org/jira/browse/INFRA-17127
> >
> > but artefact pom.xml that was done on bits.netbeans.org/nexus are not
> > complete enough to get to maven central.
> > So
> > 1) We had the possibility to get the nb-repository-plugin (and other
> > related mavenutils) to be handled by Apache NetBeans (incubating) To
> > complete we need to have documentation site for those plugin to allow
> > redirect and end properly the code donation.
> > -- documentation is part of the whole NetBeans website
> > (bits.netbeans.org) that will contains javadocs so we are discussing
> > on that on the mailing now (topic
> > bits.netbeans.org/Javadoc/mavenutils)
> >
> > Then ...
> > RELEASE90) We need to use the release90 branch and do a full build
> > with all artefacts (Javadoc, source) to allow nb-repository-plugin to
> > take items and create the repository. (We need to ensure pom.xml
> quality).
> > Apache NetBeans 9.0 will have a limited set of artefacts compared to
> > 8.2 because it will contains only what was donated at the time.
> >
> > RELEASE100) We will do the same with Apache NetBeans 10, artefact set
> > will be bigger than 9.0 but limited compared to 8.2 , as the plugin
> > will be ready, it will go faster to achieve
> >
> > dev-SNAPSHOT)Parallel to that, we also will need a SNAPSHOT version
> > for the nighly builds.
> >
> >  Regards
> > Eric
> >
> > -----Message d'origine-----
> > De : Ryan Cuprak <rc...@gmail.com>
> > Envoyé : lundi 12 novembre 2018 23:28
> > À : dev@netbeans.incubator.apache.org
> > Objet : Re: Publishing Maven Artifacts under netbeans.org (was Re:
> > Publishing Maven artifacts under third-party coordinates (was: Set up
> > Nexus staging profile for Dubbo ...))
> >
> > I just did a search and there is a task in JIRA:
> >
> > https://issues.apache.org/jira/browse/NETBEANS-467?jql=project%20%3D%2
> > 0NETBEANS%20AND%20text%20~%20nexus
> >
> > I think the task needs to be split-up into sub-tasks with the first
> > task being a proposal for how it would be implemented.
> >
> > -Ryan
> >
> > > On Nov 12, 2018, at 11:16 PM, Antonio <an...@vieiro.net> wrote:
> > >
> > > What needs to be done is learning what needs to be done :-)
> > >
> > > I'll report on my findings.
> > >
> > > Cheers,
> > > Antonio
> > >
> > > El 12/11/18 a las 23:14, Geertjan Wielenga escribió:
> > >> You are right. If you know what needs to be done, do it.
> > >> Gj
> > >> On Monday, November 12, 2018, Antonio <an...@vieiro.net> wrote:
> > >>> Hi all,
> > >>>
> > >>> Recovering this old thread of may 2018...
> > >>>
> > >>> Since the ASF now owns the netbeans.org domain, that means that we
> > >>> can now publish artifacts to Maven Central using the netbeans.org
> > domain.
> > >>>
> > >>> So there's no need to host a NetBeans Nexus Repository ourselves
> > >>> under http://bits.netbeans.org/nexus (serving binaries out of the
> > >>> Apache Mirror System is problematic, AFAIK).
> > >>>
> > >>> Am I right?
> > >>>
> > >>> Thanks,
> > >>> Antonio
> > >>>
> > >>>
> > >>> El 10/5/18 a las 0:30, Emilian Bold escribió:
> > >>>
> > >>>> So, no official Maven artifacts until Apache gets the
> > >>>> netbeans.org domain too?
> > >>>>
> > >>>> I wonder, since people would still have to edit their pom.xml
> > >>>> files to update the version -- would it really be so hard to
> > >>>> switch to org.apache groupIDs?
> > >>>>
> > >>>> We still keep the package names, etc. just change these
> > >>>> Maven-specific coordinates.
> > >>>>
> > >>>> --emi
> > >>>>
> > >>>> ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
> > >>>>
> > >>>> On 8 May 2018 8:56 PM, Greg Stein <gs...@gmail.com> wrote:
> > >>>>
> > >>>> Hi all,
> > >>>>>
> > >>>>> I wanted to send a note that Infra has seen a couple requests
> > >>>>> from podlings
> > >>>>>
> > >>>>> to publish under third-party Maven groupId coordinates
> > >>>>> (com.alibaba and
> > >>>>>
> > >>>>> org.netbeans). Unless/until the Foundation owns these domains,
> > >>>>> we cannot
> > >>>>>
> > >>>>> allow publishing under those coordinates.
> > >>>>>
> > >>>>> Needless to say, we'll never own alibaba.com :p ... Maybe one
> > >>>>> day, we'll
> > >>>>>
> > >>>>> get netbeans.org (what is the status on that?) ... But we cannot
> > >>>>> publish
> > >>>>>
> > >>>>> convenience binaries to Maven Central before such time.
> > >>>>>
> > >>>>> And please note that I said "convenience binaries". This is an
> > >>>>> important
> > >>>>>
> > >>>>> point for the two podlings: the Foundation makes source code
> > releases.
> > >>>>>
> > >>>>> Period. Full stop. Both podlings can do that today -- there is
> > >>>>> nothing
> > >>>>>
> > >>>>> inhibiting making such releases. ... What cannot be done is
> > >>>>> publishing
> > >>>>>
> > >>>>> convenience binaries to those third-party coordinates.
> > >>>>>
> > >>>>> The podlings will be able to publish under org.apache, 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 brianf@infinity.nu
> wrote:
> > >>>>>
> > >>>>> Was there discussion somewhere that decided to allow an Apache
> > >>>>> project
> > >>>>>>
> > >>>>>> to publish coordinates using com.alibaba? From my perspective
> > >>>>>> this is
> > >>>>>>
> > >>>>>> highly unusual for an ASF project. From a central point of
> > >>>>>> view, the
> > >>>>>>
> > >>>>>> fact that com.alibaba is registered to publish from a
> > >>>>>> completely
> > >>>>>>
> > >>>>>> different repo (oss.sonatype.org) this creates potential for
> > >>>>>> confusion
> > >>>>>>
> > >>>>>> over the provenance of the artifacts.
> > >>>>>>
> > >>>>>> On Wed, May 2, 2018 at 9:30 PM, Chris Lambertus cml@apache.org
> > wrote:
> > >>>>>>
> > >>>>>> On May 2, 2018, at 5:51 PM, Jun Liu liujun@apache.org wrote:
> > >>>>>>>
> > >>>>>>> Hi,
> > >>>>>>>
> > >>>>>>> We are preparing for the first apache incubating release for
> > >>>>>>> dubbo, turns
> > >>>>>>>
> > >>>>>>> out we lack of some nexus permissions, this blocks our process.
> > >>>>>>>
> > >>>>>>> Could someone help us please? Here is the ticket asking
> > permissions :
> > >>>>>>>
> > >>>>>>> https://issues.apache.org/jira/browse/INFRA-16451
> > >>>>>>>
> > >>>>>>> Best regards,
> > >>>>>>>
> > >>>>>>> Jun
> > >>>>>>>
> > >>>>>>> I don’t know how to approach this when the groupID doesn’t
> > >>>>>>> match
> > >>>>>>>
> > >>>>>>> org.apache.
> > >>>>>>>
> > >>>>>>> I’ve requested help from the Sonatype folks.
> > >>>>>>>
> > >>>>>>> -Chris
> > >>>>>>>
> > >>>>>>
> > >>>>
> > >>>>
> > >>>> -----------------------------------------------------------------
> > >>>> --
> > >>>> -- To unsubscribe, e-mail:
> > >>>> dev-unsubscribe@netbeans.incubator.apache.org
> > >>>> For additional commands, e-mail:
> > >>>> dev-help@netbeans.incubator.apache.org
> > >>>>
> > >>>> For further information about the NetBeans mailing lists, visit:
> > >>>> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+list
> > >>>> s
> > >>>>
> > >>>>
> > >>>>
> > >>>>
> > >>> ------------------------------------------------------------------
> > >>> --
> > >>> - To unsubscribe, e-mail:
> > >>> dev-unsubscribe@netbeans.incubator.apache.org
> > >>> For additional commands, e-mail:
> > >>> dev-help@netbeans.incubator.apache.org
> > >>>
> > >>> For further information about the NetBeans mailing lists, visit:
> > >>> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
> > >>>
> > >>>
> > >>>
> > >>>
> > >
> > > --------------------------------------------------------------------
> > > - To unsubscribe, e-mail:
> > > dev-unsubscribe@netbeans.incubator.apache.org
> > > For additional commands, e-mail:
> > > dev-help@netbeans.incubator.apache.org
> > >
> > > For further information about the NetBeans mailing lists, visit:
> > > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
> > >
> > >
> > >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
> > For additional commands, e-mail:
> > dev-help@netbeans.incubator.apache.org
> >
> > For further information about the NetBeans mailing lists, visit:
> > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
> >
> >
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
> > For additional commands, e-mail:
> > dev-help@netbeans.incubator.apache.org
> >
> > For further information about the NetBeans mailing lists, visit:
> > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
> >
> >
> >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
> For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>
>

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

[Eric Barboni <sk...@apache.org>]

Hi, 
 I will say ASAP, because I also need it but currently I focus on the build of the website for the tools because code donation is done but has no new home.

 Concerning the artefacts, the issue is that generated pom doesn’t have the minimum requierement. (Licences sections, url section, and scm section)
 
 If anyone have the possibility to help on this point it would be very helpful it's time consuming to wait for artifacts to be generated.

An icomplete PR is under progress for buildscript doing apidoc+mavenartifacts

Best Regards

Eric
-----Message d'origine-----
De : Jean-Marc Borer <jm...@gmail.com> 
Envoyé : vendredi 7 décembre 2018 11:09
À : dev@netbeans.incubator.apache.org
Objet : Re: Publishing Maven Artifacts under netbeans.org (was Re: Publishing Maven artifacts under third-party coordinates (was: Set up Nexus staging profile for Dubbo ...))

Hi Eric,

And when do you think, will this be completed (rough estimation is ok)?

Cheers,

JM

On Tue, Nov 13, 2018 at 12:11 AM Eric Barboni <sk...@apache.org> wrote:

> HI,
>  There is also a issue there:
> https://issues.apache.org/jira/browse/INFRA-17127
>
> but artefact pom.xml that was done on bits.netbeans.org/nexus are not 
> complete enough to get to maven central.
> So
> 1) We had the possibility to get the nb-repository-plugin (and other 
> related mavenutils) to be handled by Apache NetBeans (incubating) To 
> complete we need to have documentation site for those plugin to allow 
> redirect and end properly the code donation.
> -- documentation is part of the whole NetBeans website 
> (bits.netbeans.org) that will contains javadocs so we are discussing 
> on that on the mailing now (topic 
> bits.netbeans.org/Javadoc/mavenutils)
>
> Then ...
> RELEASE90) We need to use the release90 branch and do a full build 
> with all artefacts (Javadoc, source) to allow nb-repository-plugin to 
> take items and create the repository. (We need to ensure pom.xml quality).
> Apache NetBeans 9.0 will have a limited set of artefacts compared to 
> 8.2 because it will contains only what was donated at the time.
>
> RELEASE100) We will do the same with Apache NetBeans 10, artefact set 
> will be bigger than 9.0 but limited compared to 8.2 , as the plugin 
> will be ready, it will go faster to achieve
>
> dev-SNAPSHOT)Parallel to that, we also will need a SNAPSHOT version 
> for the nighly builds.
>
>  Regards
> Eric
>
> -----Message d'origine-----
> De : Ryan Cuprak <rc...@gmail.com>
> Envoyé : lundi 12 novembre 2018 23:28
> À : dev@netbeans.incubator.apache.org
> Objet : Re: Publishing Maven Artifacts under netbeans.org (was Re:
> Publishing Maven artifacts under third-party coordinates (was: Set up 
> Nexus staging profile for Dubbo ...))
>
> I just did a search and there is a task in JIRA:
>
> https://issues.apache.org/jira/browse/NETBEANS-467?jql=project%20%3D%2
> 0NETBEANS%20AND%20text%20~%20nexus
>
> I think the task needs to be split-up into sub-tasks with the first 
> task being a proposal for how it would be implemented.
>
> -Ryan
>
> > On Nov 12, 2018, at 11:16 PM, Antonio <an...@vieiro.net> wrote:
> >
> > What needs to be done is learning what needs to be done :-)
> >
> > I'll report on my findings.
> >
> > Cheers,
> > Antonio
> >
> > El 12/11/18 a las 23:14, Geertjan Wielenga escribió:
> >> You are right. If you know what needs to be done, do it.
> >> Gj
> >> On Monday, November 12, 2018, Antonio <an...@vieiro.net> wrote:
> >>> Hi all,
> >>>
> >>> Recovering this old thread of may 2018...
> >>>
> >>> Since the ASF now owns the netbeans.org domain, that means that we 
> >>> can now publish artifacts to Maven Central using the netbeans.org
> domain.
> >>>
> >>> So there's no need to host a NetBeans Nexus Repository ourselves 
> >>> under http://bits.netbeans.org/nexus (serving binaries out of the 
> >>> Apache Mirror System is problematic, AFAIK).
> >>>
> >>> Am I right?
> >>>
> >>> Thanks,
> >>> Antonio
> >>>
> >>>
> >>> El 10/5/18 a las 0:30, Emilian Bold escribió:
> >>>
> >>>> So, no official Maven artifacts until Apache gets the 
> >>>> netbeans.org domain too?
> >>>>
> >>>> I wonder, since people would still have to edit their pom.xml 
> >>>> files to update the version -- would it really be so hard to 
> >>>> switch to org.apache groupIDs?
> >>>>
> >>>> We still keep the package names, etc. just change these 
> >>>> Maven-specific coordinates.
> >>>>
> >>>> --emi
> >>>>
> >>>> ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
> >>>>
> >>>> On 8 May 2018 8:56 PM, Greg Stein <gs...@gmail.com> wrote:
> >>>>
> >>>> Hi all,
> >>>>>
> >>>>> I wanted to send a note that Infra has seen a couple requests 
> >>>>> from podlings
> >>>>>
> >>>>> to publish under third-party Maven groupId coordinates 
> >>>>> (com.alibaba and
> >>>>>
> >>>>> org.netbeans). Unless/until the Foundation owns these domains, 
> >>>>> we cannot
> >>>>>
> >>>>> allow publishing under those coordinates.
> >>>>>
> >>>>> Needless to say, we'll never own alibaba.com :p ... Maybe one 
> >>>>> day, we'll
> >>>>>
> >>>>> get netbeans.org (what is the status on that?) ... But we cannot 
> >>>>> publish
> >>>>>
> >>>>> convenience binaries to Maven Central before such time.
> >>>>>
> >>>>> And please note that I said "convenience binaries". This is an 
> >>>>> important
> >>>>>
> >>>>> point for the two podlings: the Foundation makes source code
> releases.
> >>>>>
> >>>>> Period. Full stop. Both podlings can do that today -- there is 
> >>>>> nothing
> >>>>>
> >>>>> inhibiting making such releases. ... What cannot be done is 
> >>>>> publishing
> >>>>>
> >>>>> convenience binaries to those third-party coordinates.
> >>>>>
> >>>>> The podlings will be able to publish under org.apache, 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 brianf@infinity.nu wrote:
> >>>>>
> >>>>> Was there discussion somewhere that decided to allow an Apache 
> >>>>> project
> >>>>>>
> >>>>>> to publish coordinates using com.alibaba? From my perspective 
> >>>>>> this is
> >>>>>>
> >>>>>> highly unusual for an ASF project. From a central point of 
> >>>>>> view, the
> >>>>>>
> >>>>>> fact that com.alibaba is registered to publish from a 
> >>>>>> completely
> >>>>>>
> >>>>>> different repo (oss.sonatype.org) this creates potential for 
> >>>>>> confusion
> >>>>>>
> >>>>>> over the provenance of the artifacts.
> >>>>>>
> >>>>>> On Wed, May 2, 2018 at 9:30 PM, Chris Lambertus cml@apache.org
> wrote:
> >>>>>>
> >>>>>> On May 2, 2018, at 5:51 PM, Jun Liu liujun@apache.org wrote:
> >>>>>>>
> >>>>>>> Hi,
> >>>>>>>
> >>>>>>> We are preparing for the first apache incubating release for 
> >>>>>>> dubbo, turns
> >>>>>>>
> >>>>>>> out we lack of some nexus permissions, this blocks our process.
> >>>>>>>
> >>>>>>> Could someone help us please? Here is the ticket asking
> permissions :
> >>>>>>>
> >>>>>>> https://issues.apache.org/jira/browse/INFRA-16451
> >>>>>>>
> >>>>>>> Best regards,
> >>>>>>>
> >>>>>>> Jun
> >>>>>>>
> >>>>>>> I don’t know how to approach this when the groupID doesn’t 
> >>>>>>> match
> >>>>>>>
> >>>>>>> org.apache.
> >>>>>>>
> >>>>>>> I’ve requested help from the Sonatype folks.
> >>>>>>>
> >>>>>>> -Chris
> >>>>>>>
> >>>>>>
> >>>>
> >>>>
> >>>> -----------------------------------------------------------------
> >>>> --
> >>>> -- To unsubscribe, e-mail:
> >>>> dev-unsubscribe@netbeans.incubator.apache.org
> >>>> For additional commands, e-mail:
> >>>> dev-help@netbeans.incubator.apache.org
> >>>>
> >>>> For further information about the NetBeans mailing lists, visit:
> >>>> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+list
> >>>> s
> >>>>
> >>>>
> >>>>
> >>>>
> >>> ------------------------------------------------------------------
> >>> --
> >>> - To unsubscribe, e-mail:
> >>> dev-unsubscribe@netbeans.incubator.apache.org
> >>> For additional commands, e-mail:
> >>> dev-help@netbeans.incubator.apache.org
> >>>
> >>> For further information about the NetBeans mailing lists, visit:
> >>> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
> >>>
> >>>
> >>>
> >>>
> >
> > --------------------------------------------------------------------
> > - To unsubscribe, e-mail: 
> > dev-unsubscribe@netbeans.incubator.apache.org
> > For additional commands, e-mail:
> > dev-help@netbeans.incubator.apache.org
> >
> > For further information about the NetBeans mailing lists, visit:
> > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
> >
> >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
> For additional commands, e-mail: 
> dev-help@netbeans.incubator.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
> For additional commands, e-mail: 
> dev-help@netbeans.incubator.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>
>


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
For additional commands, e-mail: dev-help@netbeans.incubator.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

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

[Jean-Marc Borer <jm...@gmail.com>]

Hi Eric,

And when do you think, will this be completed (rough estimation is ok)?

Cheers,

JM

On Tue, Nov 13, 2018 at 12:11 AM Eric Barboni <sk...@apache.org> wrote:

> HI,
>  There is also a issue there:
> https://issues.apache.org/jira/browse/INFRA-17127
>
> but artefact pom.xml that was done on bits.netbeans.org/nexus are not
> complete enough to get to maven central.
> So
> 1) We had the possibility to get the nb-repository-plugin (and other
> related mavenutils) to be handled by Apache NetBeans (incubating)
> To complete we need to have documentation site for those plugin to allow
> redirect and end properly the code donation.
> -- documentation is part of the whole NetBeans website (bits.netbeans.org)
> that will contains javadocs so we are discussing on that on the mailing now
> (topic bits.netbeans.org/Javadoc/mavenutils)
>
> Then ...
> RELEASE90) We need to use the release90 branch and do a full build with
> all artefacts (Javadoc, source) to allow nb-repository-plugin to take items
> and create the repository. (We need to ensure pom.xml quality).
> Apache NetBeans 9.0 will have a limited set of artefacts compared to 8.2
> because it will contains only what was donated at the time.
>
> RELEASE100) We will do the same with Apache NetBeans 10, artefact set will
> be bigger than 9.0 but limited compared to 8.2 , as the plugin will be
> ready, it will go faster to achieve
>
> dev-SNAPSHOT)Parallel to that, we also will need a SNAPSHOT version for
> the nighly builds.
>
>  Regards
> Eric
>
> -----Message d'origine-----
> De : Ryan Cuprak <rc...@gmail.com>
> Envoyé : lundi 12 novembre 2018 23:28
> À : dev@netbeans.incubator.apache.org
> Objet : Re: Publishing Maven Artifacts under netbeans.org (was Re:
> Publishing Maven artifacts under third-party coordinates (was: Set up Nexus
> staging profile for Dubbo ...))
>
> I just did a search and there is a task in JIRA:
>
> https://issues.apache.org/jira/browse/NETBEANS-467?jql=project%20%3D%20NETBEANS%20AND%20text%20~%20nexus
>
> I think the task needs to be split-up into sub-tasks with the first task
> being a proposal for how it would be implemented.
>
> -Ryan
>
> > On Nov 12, 2018, at 11:16 PM, Antonio <an...@vieiro.net> wrote:
> >
> > What needs to be done is learning what needs to be done :-)
> >
> > I'll report on my findings.
> >
> > Cheers,
> > Antonio
> >
> > El 12/11/18 a las 23:14, Geertjan Wielenga escribió:
> >> You are right. If you know what needs to be done, do it.
> >> Gj
> >> On Monday, November 12, 2018, Antonio <an...@vieiro.net> wrote:
> >>> Hi all,
> >>>
> >>> Recovering this old thread of may 2018...
> >>>
> >>> Since the ASF now owns the netbeans.org domain, that means that we
> >>> can now publish artifacts to Maven Central using the netbeans.org
> domain.
> >>>
> >>> So there's no need to host a NetBeans Nexus Repository ourselves
> >>> under http://bits.netbeans.org/nexus (serving binaries out of the
> >>> Apache Mirror System is problematic, AFAIK).
> >>>
> >>> Am I right?
> >>>
> >>> Thanks,
> >>> Antonio
> >>>
> >>>
> >>> El 10/5/18 a las 0:30, Emilian Bold escribió:
> >>>
> >>>> So, no official Maven artifacts until Apache gets the netbeans.org
> >>>> domain too?
> >>>>
> >>>> I wonder, since people would still have to edit their pom.xml files
> >>>> to update the version -- would it really be so hard to switch to
> >>>> org.apache groupIDs?
> >>>>
> >>>> We still keep the package names, etc. just change these
> >>>> Maven-specific coordinates.
> >>>>
> >>>> --emi
> >>>>
> >>>> ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
> >>>>
> >>>> On 8 May 2018 8:56 PM, Greg Stein <gs...@gmail.com> wrote:
> >>>>
> >>>> Hi all,
> >>>>>
> >>>>> I wanted to send a note that Infra has seen a couple requests from
> >>>>> podlings
> >>>>>
> >>>>> to publish under third-party Maven groupId coordinates
> >>>>> (com.alibaba and
> >>>>>
> >>>>> org.netbeans). Unless/until the Foundation owns these domains, we
> >>>>> cannot
> >>>>>
> >>>>> allow publishing under those coordinates.
> >>>>>
> >>>>> Needless to say, we'll never own alibaba.com :p ... Maybe one day,
> >>>>> we'll
> >>>>>
> >>>>> get netbeans.org (what is the status on that?) ... But we cannot
> >>>>> publish
> >>>>>
> >>>>> convenience binaries to Maven Central before such time.
> >>>>>
> >>>>> And please note that I said "convenience binaries". This is an
> >>>>> important
> >>>>>
> >>>>> point for the two podlings: the Foundation makes source code
> releases.
> >>>>>
> >>>>> Period. Full stop. Both podlings can do that today -- there is
> >>>>> nothing
> >>>>>
> >>>>> inhibiting making such releases. ... What cannot be done is
> >>>>> publishing
> >>>>>
> >>>>> convenience binaries to those third-party coordinates.
> >>>>>
> >>>>> The podlings will be able to publish under org.apache, 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 brianf@infinity.nu wrote:
> >>>>>
> >>>>> Was there discussion somewhere that decided to allow an Apache
> >>>>> project
> >>>>>>
> >>>>>> to publish coordinates using com.alibaba? From my perspective
> >>>>>> this is
> >>>>>>
> >>>>>> highly unusual for an ASF project. From a central point of view,
> >>>>>> the
> >>>>>>
> >>>>>> fact that com.alibaba is registered to publish from a completely
> >>>>>>
> >>>>>> different repo (oss.sonatype.org) this creates potential for
> >>>>>> confusion
> >>>>>>
> >>>>>> over the provenance of the artifacts.
> >>>>>>
> >>>>>> On Wed, May 2, 2018 at 9:30 PM, Chris Lambertus cml@apache.org
> wrote:
> >>>>>>
> >>>>>> On May 2, 2018, at 5:51 PM, Jun Liu liujun@apache.org wrote:
> >>>>>>>
> >>>>>>> Hi,
> >>>>>>>
> >>>>>>> We are preparing for the first apache incubating release for
> >>>>>>> dubbo, turns
> >>>>>>>
> >>>>>>> out we lack of some nexus permissions, this blocks our process.
> >>>>>>>
> >>>>>>> Could someone help us please? Here is the ticket asking
> permissions :
> >>>>>>>
> >>>>>>> https://issues.apache.org/jira/browse/INFRA-16451
> >>>>>>>
> >>>>>>> Best regards,
> >>>>>>>
> >>>>>>> Jun
> >>>>>>>
> >>>>>>> I don’t know how to approach this when the groupID doesn’t match
> >>>>>>>
> >>>>>>> org.apache.
> >>>>>>>
> >>>>>>> I’ve requested help from the Sonatype folks.
> >>>>>>>
> >>>>>>> -Chris
> >>>>>>>
> >>>>>>
> >>>>
> >>>>
> >>>> -------------------------------------------------------------------
> >>>> -- To unsubscribe, e-mail:
> >>>> dev-unsubscribe@netbeans.incubator.apache.org
> >>>> For additional commands, e-mail:
> >>>> dev-help@netbeans.incubator.apache.org
> >>>>
> >>>> For further information about the NetBeans mailing lists, visit:
> >>>> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
> >>>>
> >>>>
> >>>>
> >>>>
> >>> --------------------------------------------------------------------
> >>> - To unsubscribe, e-mail:
> >>> dev-unsubscribe@netbeans.incubator.apache.org
> >>> For additional commands, e-mail:
> >>> dev-help@netbeans.incubator.apache.org
> >>>
> >>> For further information about the NetBeans mailing lists, visit:
> >>> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
> >>>
> >>>
> >>>
> >>>
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
> > For additional commands, e-mail:
> > dev-help@netbeans.incubator.apache.org
> >
> > For further information about the NetBeans mailing lists, visit:
> > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
> >
> >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
> For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
> For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>
>

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

[Eric Barboni <sk...@apache.org>]

HI,
 There is also a issue there:
https://issues.apache.org/jira/browse/INFRA-17127

but artefact pom.xml that was done on bits.netbeans.org/nexus are not complete enough to get to maven central.
So 
1) We had the possibility to get the nb-repository-plugin (and other related mavenutils) to be handled by Apache NetBeans (incubating)
To complete we need to have documentation site for those plugin to allow redirect and end properly the code donation.
-- documentation is part of the whole NetBeans website (bits.netbeans.org) that will contains javadocs so we are discussing on that on the mailing now (topic bits.netbeans.org/Javadoc/mavenutils)

Then ...
RELEASE90) We need to use the release90 branch and do a full build with all artefacts (Javadoc, source) to allow nb-repository-plugin to take items and create the repository. (We need to ensure pom.xml quality). 
Apache NetBeans 9.0 will have a limited set of artefacts compared to 8.2 because it will contains only what was donated at the time.

RELEASE100) We will do the same with Apache NetBeans 10, artefact set will be bigger than 9.0 but limited compared to 8.2 , as the plugin will be ready, it will go faster to achieve

dev-SNAPSHOT)Parallel to that, we also will need a SNAPSHOT version for the nighly builds.

 Regards
Eric

-----Message d'origine-----
De : Ryan Cuprak <rc...@gmail.com> 
Envoyé : lundi 12 novembre 2018 23:28
À : dev@netbeans.incubator.apache.org
Objet : Re: Publishing Maven Artifacts under netbeans.org (was Re: Publishing Maven artifacts under third-party coordinates (was: Set up Nexus staging profile for Dubbo ...))

I just did a search and there is a task in JIRA:
https://issues.apache.org/jira/browse/NETBEANS-467?jql=project%20%3D%20NETBEANS%20AND%20text%20~%20nexus

I think the task needs to be split-up into sub-tasks with the first task being a proposal for how it would be implemented. 

-Ryan

> On Nov 12, 2018, at 11:16 PM, Antonio <an...@vieiro.net> wrote:
> 
> What needs to be done is learning what needs to be done :-)
> 
> I'll report on my findings.
> 
> Cheers,
> Antonio
> 
> El 12/11/18 a las 23:14, Geertjan Wielenga escribió:
>> You are right. If you know what needs to be done, do it.
>> Gj
>> On Monday, November 12, 2018, Antonio <an...@vieiro.net> wrote:
>>> Hi all,
>>> 
>>> Recovering this old thread of may 2018...
>>> 
>>> Since the ASF now owns the netbeans.org domain, that means that we 
>>> can now publish artifacts to Maven Central using the netbeans.org domain.
>>> 
>>> So there's no need to host a NetBeans Nexus Repository ourselves 
>>> under http://bits.netbeans.org/nexus (serving binaries out of the 
>>> Apache Mirror System is problematic, AFAIK).
>>> 
>>> Am I right?
>>> 
>>> Thanks,
>>> Antonio
>>> 
>>> 
>>> El 10/5/18 a las 0:30, Emilian Bold escribió:
>>> 
>>>> So, no official Maven artifacts until Apache gets the netbeans.org 
>>>> domain too?
>>>> 
>>>> I wonder, since people would still have to edit their pom.xml files 
>>>> to update the version -- would it really be so hard to switch to 
>>>> org.apache groupIDs?
>>>> 
>>>> We still keep the package names, etc. just change these 
>>>> Maven-specific coordinates.
>>>> 
>>>> --emi
>>>> 
>>>> ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
>>>> 
>>>> On 8 May 2018 8:56 PM, Greg Stein <gs...@gmail.com> wrote:
>>>> 
>>>> Hi all,
>>>>> 
>>>>> I wanted to send a note that Infra has seen a couple requests from 
>>>>> podlings
>>>>> 
>>>>> to publish under third-party Maven groupId coordinates 
>>>>> (com.alibaba and
>>>>> 
>>>>> org.netbeans). Unless/until the Foundation owns these domains, we 
>>>>> cannot
>>>>> 
>>>>> allow publishing under those coordinates.
>>>>> 
>>>>> Needless to say, we'll never own alibaba.com :p ... Maybe one day, 
>>>>> we'll
>>>>> 
>>>>> get netbeans.org (what is the status on that?) ... But we cannot 
>>>>> publish
>>>>> 
>>>>> convenience binaries to Maven Central before such time.
>>>>> 
>>>>> And please note that I said "convenience binaries". This is an 
>>>>> important
>>>>> 
>>>>> point for the two podlings: the Foundation makes source code releases.
>>>>> 
>>>>> Period. Full stop. Both podlings can do that today -- there is 
>>>>> nothing
>>>>> 
>>>>> inhibiting making such releases. ... What cannot be done is 
>>>>> publishing
>>>>> 
>>>>> convenience binaries to those third-party coordinates.
>>>>> 
>>>>> The podlings will be able to publish under org.apache, 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 brianf@infinity.nu wrote:
>>>>> 
>>>>> Was there discussion somewhere that decided to allow an Apache 
>>>>> project
>>>>>> 
>>>>>> to publish coordinates using com.alibaba? From my perspective 
>>>>>> this is
>>>>>> 
>>>>>> highly unusual for an ASF project. From a central point of view, 
>>>>>> the
>>>>>> 
>>>>>> fact that com.alibaba is registered to publish from a completely
>>>>>> 
>>>>>> different repo (oss.sonatype.org) this creates potential for 
>>>>>> confusion
>>>>>> 
>>>>>> over the provenance of the artifacts.
>>>>>> 
>>>>>> On Wed, May 2, 2018 at 9:30 PM, Chris Lambertus cml@apache.org wrote:
>>>>>> 
>>>>>> On May 2, 2018, at 5:51 PM, Jun Liu liujun@apache.org wrote:
>>>>>>> 
>>>>>>> Hi,
>>>>>>> 
>>>>>>> We are preparing for the first apache incubating release for 
>>>>>>> dubbo, turns
>>>>>>> 
>>>>>>> out we lack of some nexus permissions, this blocks our process.
>>>>>>> 
>>>>>>> Could someone help us please? Here is the ticket asking permissions :
>>>>>>> 
>>>>>>> https://issues.apache.org/jira/browse/INFRA-16451
>>>>>>> 
>>>>>>> Best regards,
>>>>>>> 
>>>>>>> Jun
>>>>>>> 
>>>>>>> I don’t know how to approach this when the groupID doesn’t match
>>>>>>> 
>>>>>>> org.apache.
>>>>>>> 
>>>>>>> I’ve requested help from the Sonatype folks.
>>>>>>> 
>>>>>>> -Chris
>>>>>>> 
>>>>>> 
>>>> 
>>>> 
>>>> -------------------------------------------------------------------
>>>> -- To unsubscribe, e-mail: 
>>>> dev-unsubscribe@netbeans.incubator.apache.org
>>>> For additional commands, e-mail: 
>>>> dev-help@netbeans.incubator.apache.org
>>>> 
>>>> For further information about the NetBeans mailing lists, visit:
>>>> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>>>> 
>>>> 
>>>> 
>>>> 
>>> --------------------------------------------------------------------
>>> - To unsubscribe, e-mail: 
>>> dev-unsubscribe@netbeans.incubator.apache.org
>>> For additional commands, e-mail: 
>>> dev-help@netbeans.incubator.apache.org
>>> 
>>> For further information about the NetBeans mailing lists, visit:
>>> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>>> 
>>> 
>>> 
>>> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
> For additional commands, e-mail: 
> dev-help@netbeans.incubator.apache.org
> 
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
> 
> 
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
For additional commands, e-mail: dev-help@netbeans.incubator.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists





---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
For additional commands, e-mail: dev-help@netbeans.incubator.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

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

[Ryan Cuprak <rc...@gmail.com>]

I just did a search and there is a task in JIRA:
https://issues.apache.org/jira/browse/NETBEANS-467?jql=project%20%3D%20NETBEANS%20AND%20text%20~%20nexus

I think the task needs to be split-up into sub-tasks with the first task being a proposal for how it would be implemented. 

-Ryan

> On Nov 12, 2018, at 11:16 PM, Antonio <an...@vieiro.net> wrote:
> 
> What needs to be done is learning what needs to be done :-)
> 
> I'll report on my findings.
> 
> Cheers,
> Antonio
> 
> El 12/11/18 a las 23:14, Geertjan Wielenga escribió:
>> You are right. If you know what needs to be done, do it.
>> Gj
>> On Monday, November 12, 2018, Antonio <an...@vieiro.net> wrote:
>>> Hi all,
>>> 
>>> Recovering this old thread of may 2018...
>>> 
>>> Since the ASF now owns the netbeans.org domain, that means that we can
>>> now publish artifacts to Maven Central using the netbeans.org domain.
>>> 
>>> So there's no need to host a NetBeans Nexus Repository ourselves under
>>> http://bits.netbeans.org/nexus (serving binaries out of the Apache Mirror
>>> System is problematic, AFAIK).
>>> 
>>> Am I right?
>>> 
>>> Thanks,
>>> Antonio
>>> 
>>> 
>>> El 10/5/18 a las 0:30, Emilian Bold escribió:
>>> 
>>>> So, no official Maven artifacts until Apache gets the netbeans.org
>>>> domain too?
>>>> 
>>>> I wonder, since people would still have to edit their pom.xml files to
>>>> update the version -- would it really be so hard to switch to org.apache
>>>> groupIDs?
>>>> 
>>>> We still keep the package names, etc. just change these Maven-specific
>>>> coordinates.
>>>> 
>>>> --emi
>>>> 
>>>> ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
>>>> 
>>>> On 8 May 2018 8:56 PM, Greg Stein <gs...@gmail.com> wrote:
>>>> 
>>>> Hi all,
>>>>> 
>>>>> I wanted to send a note that Infra has seen a couple requests from
>>>>> podlings
>>>>> 
>>>>> to publish under third-party Maven groupId coordinates (com.alibaba and
>>>>> 
>>>>> org.netbeans). Unless/until the Foundation owns these domains, we cannot
>>>>> 
>>>>> allow publishing under those coordinates.
>>>>> 
>>>>> Needless to say, we'll never own alibaba.com :p ... Maybe one day, we'll
>>>>> 
>>>>> get netbeans.org (what is the status on that?) ... But we cannot publish
>>>>> 
>>>>> convenience binaries to Maven Central before such time.
>>>>> 
>>>>> And please note that I said "convenience binaries". This is an important
>>>>> 
>>>>> point for the two podlings: the Foundation makes source code releases.
>>>>> 
>>>>> Period. Full stop. Both podlings can do that today -- there is nothing
>>>>> 
>>>>> inhibiting making such releases. ... What cannot be done is publishing
>>>>> 
>>>>> convenience binaries to those third-party coordinates.
>>>>> 
>>>>> The podlings will be able to publish under org.apache, 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 brianf@infinity.nu wrote:
>>>>> 
>>>>> Was there discussion somewhere that decided to allow an Apache project
>>>>>> 
>>>>>> to publish coordinates using com.alibaba? From my perspective this is
>>>>>> 
>>>>>> highly unusual for an ASF project. From a central point of view, the
>>>>>> 
>>>>>> fact that com.alibaba is registered to publish from a completely
>>>>>> 
>>>>>> different repo (oss.sonatype.org) this creates potential for confusion
>>>>>> 
>>>>>> over the provenance of the artifacts.
>>>>>> 
>>>>>> On Wed, May 2, 2018 at 9:30 PM, Chris Lambertus cml@apache.org wrote:
>>>>>> 
>>>>>> On May 2, 2018, at 5:51 PM, Jun Liu liujun@apache.org wrote:
>>>>>>> 
>>>>>>> Hi,
>>>>>>> 
>>>>>>> We are preparing for the first apache incubating release for dubbo,
>>>>>>> turns
>>>>>>> 
>>>>>>> out we lack of some nexus permissions, this blocks our process.
>>>>>>> 
>>>>>>> Could someone help us please? Here is the ticket asking permissions :
>>>>>>> 
>>>>>>> https://issues.apache.org/jira/browse/INFRA-16451
>>>>>>> 
>>>>>>> Best regards,
>>>>>>> 
>>>>>>> Jun
>>>>>>> 
>>>>>>> I don’t know how to approach this when the groupID doesn’t match
>>>>>>> 
>>>>>>> org.apache.
>>>>>>> 
>>>>>>> I’ve requested help from the Sonatype folks.
>>>>>>> 
>>>>>>> -Chris
>>>>>>> 
>>>>>> 
>>>> 
>>>> 
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
>>>> For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
>>>> 
>>>> For further information about the NetBeans mailing lists, visit:
>>>> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>>>> 
>>>> 
>>>> 
>>>> 
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
>>> For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
>>> 
>>> For further information about the NetBeans mailing lists, visit:
>>> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>>> 
>>> 
>>> 
>>> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
> For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
> 
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
> 
> 
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
For additional commands, e-mail: dev-help@netbeans.incubator.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

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

[Antonio <an...@vieiro.net>]

Wow, this is a long read...

https://www.apache.org/dev/publishing-maven-artifacts.html


El 12/11/18 a las 23:16, Antonio escribió:
> What needs to be done is learning what needs to be done :-)
> 
> I'll report on my findings.
> 
> Cheers,
> Antonio
> 
> El 12/11/18 a las 23:14, Geertjan Wielenga escribió:
>> You are right. If you know what needs to be done, do it.
>>
>> Gj
>>
>>
>>
>> On Monday, November 12, 2018, Antonio <an...@vieiro.net> wrote:
>>
>>> Hi all,
>>>
>>> Recovering this old thread of may 2018...
>>>
>>> Since the ASF now owns the netbeans.org domain, that means that we can
>>> now publish artifacts to Maven Central using the netbeans.org domain.
>>>
>>> So there's no need to host a NetBeans Nexus Repository ourselves under
>>> http://bits.netbeans.org/nexus (serving binaries out of the Apache 
>>> Mirror
>>> System is problematic, AFAIK).
>>>
>>> Am I right?
>>>
>>> Thanks,
>>> Antonio
>>>
>>>
>>> El 10/5/18 a las 0:30, Emilian Bold escribió:
>>>
>>>> So, no official Maven artifacts until Apache gets the netbeans.org
>>>> domain too?
>>>>
>>>> I wonder, since people would still have to edit their pom.xml files to
>>>> update the version -- would it really be so hard to switch to 
>>>> org.apache
>>>> groupIDs?
>>>>
>>>> We still keep the package names, etc. just change these Maven-specific
>>>> coordinates.
>>>>
>>>> --emi
>>>>
>>>> ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
>>>>
>>>> On 8 May 2018 8:56 PM, Greg Stein <gs...@gmail.com> wrote:
>>>>
>>>> Hi all,
>>>>>
>>>>> I wanted to send a note that Infra has seen a couple requests from
>>>>> podlings
>>>>>
>>>>> to publish under third-party Maven groupId coordinates (com.alibaba 
>>>>> and
>>>>>
>>>>> org.netbeans). Unless/until the Foundation owns these domains, we 
>>>>> cannot
>>>>>
>>>>> allow publishing under those coordinates.
>>>>>
>>>>> Needless to say, we'll never own alibaba.com :p ... Maybe one day, 
>>>>> we'll
>>>>>
>>>>> get netbeans.org (what is the status on that?) ... But we cannot 
>>>>> publish
>>>>>
>>>>> convenience binaries to Maven Central before such time.
>>>>>
>>>>> And please note that I said "convenience binaries". This is an 
>>>>> important
>>>>>
>>>>> point for the two podlings: the Foundation makes source code releases.
>>>>>
>>>>> Period. Full stop. Both podlings can do that today -- there is nothing
>>>>>
>>>>> inhibiting making such releases. ... What cannot be done is publishing
>>>>>
>>>>> convenience binaries to those third-party coordinates.
>>>>>
>>>>> The podlings will be able to publish under org.apache, 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 brianf@infinity.nu wrote:
>>>>>
>>>>> Was there discussion somewhere that decided to allow an Apache project
>>>>>>
>>>>>> to publish coordinates using com.alibaba? From my perspective this is
>>>>>>
>>>>>> highly unusual for an ASF project. From a central point of view, the
>>>>>>
>>>>>> fact that com.alibaba is registered to publish from a completely
>>>>>>
>>>>>> different repo (oss.sonatype.org) this creates potential for 
>>>>>> confusion
>>>>>>
>>>>>> over the provenance of the artifacts.
>>>>>>
>>>>>> On Wed, May 2, 2018 at 9:30 PM, Chris Lambertus cml@apache.org wrote:
>>>>>>
>>>>>> On May 2, 2018, at 5:51 PM, Jun Liu liujun@apache.org wrote:
>>>>>>>
>>>>>>> Hi,
>>>>>>>
>>>>>>> We are preparing for the first apache incubating release for dubbo,
>>>>>>> turns
>>>>>>>
>>>>>>> out we lack of some nexus permissions, this blocks our process.
>>>>>>>
>>>>>>> Could someone help us please? Here is the ticket asking 
>>>>>>> permissions :
>>>>>>>
>>>>>>> https://issues.apache.org/jira/browse/INFRA-16451
>>>>>>>
>>>>>>> Best regards,
>>>>>>>
>>>>>>> Jun
>>>>>>>
>>>>>>> I don’t know how to approach this when the groupID doesn’t match
>>>>>>>
>>>>>>> org.apache.
>>>>>>>
>>>>>>> I’ve requested help from the Sonatype folks.
>>>>>>>
>>>>>>> -Chris
>>>>>>>
>>>>>>
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
>>>> For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
>>>>
>>>> For further information about the NetBeans mailing lists, visit:
>>>> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>>>>
>>>>
>>>>
>>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
>>> For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
>>>
>>> For further information about the NetBeans mailing lists, visit:
>>> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>>>
>>>
>>>
>>>
>>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
For additional commands, e-mail: dev-help@netbeans.incubator.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

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

[Antonio <an...@vieiro.net>]

What needs to be done is learning what needs to be done :-)

I'll report on my findings.

Cheers,
Antonio

El 12/11/18 a las 23:14, Geertjan Wielenga escribió:
> You are right. If you know what needs to be done, do it.
> 
> Gj
> 
> 
> 
> On Monday, November 12, 2018, Antonio <an...@vieiro.net> wrote:
> 
>> Hi all,
>>
>> Recovering this old thread of may 2018...
>>
>> Since the ASF now owns the netbeans.org domain, that means that we can
>> now publish artifacts to Maven Central using the netbeans.org domain.
>>
>> So there's no need to host a NetBeans Nexus Repository ourselves under
>> http://bits.netbeans.org/nexus (serving binaries out of the Apache Mirror
>> System is problematic, AFAIK).
>>
>> Am I right?
>>
>> Thanks,
>> Antonio
>>
>>
>> El 10/5/18 a las 0:30, Emilian Bold escribió:
>>
>>> So, no official Maven artifacts until Apache gets the netbeans.org
>>> domain too?
>>>
>>> I wonder, since people would still have to edit their pom.xml files to
>>> update the version -- would it really be so hard to switch to org.apache
>>> groupIDs?
>>>
>>> We still keep the package names, etc. just change these Maven-specific
>>> coordinates.
>>>
>>> --emi
>>>
>>> ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
>>>
>>> On 8 May 2018 8:56 PM, Greg Stein <gs...@gmail.com> wrote:
>>>
>>> Hi all,
>>>>
>>>> I wanted to send a note that Infra has seen a couple requests from
>>>> podlings
>>>>
>>>> to publish under third-party Maven groupId coordinates (com.alibaba and
>>>>
>>>> org.netbeans). Unless/until the Foundation owns these domains, we cannot
>>>>
>>>> allow publishing under those coordinates.
>>>>
>>>> Needless to say, we'll never own alibaba.com :p ... Maybe one day, we'll
>>>>
>>>> get netbeans.org (what is the status on that?) ... But we cannot publish
>>>>
>>>> convenience binaries to Maven Central before such time.
>>>>
>>>> And please note that I said "convenience binaries". This is an important
>>>>
>>>> point for the two podlings: the Foundation makes source code releases.
>>>>
>>>> Period. Full stop. Both podlings can do that today -- there is nothing
>>>>
>>>> inhibiting making such releases. ... What cannot be done is publishing
>>>>
>>>> convenience binaries to those third-party coordinates.
>>>>
>>>> The podlings will be able to publish under org.apache, 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 brianf@infinity.nu wrote:
>>>>
>>>> Was there discussion somewhere that decided to allow an Apache project
>>>>>
>>>>> to publish coordinates using com.alibaba? From my perspective this is
>>>>>
>>>>> highly unusual for an ASF project. From a central point of view, the
>>>>>
>>>>> fact that com.alibaba is registered to publish from a completely
>>>>>
>>>>> different repo (oss.sonatype.org) this creates potential for confusion
>>>>>
>>>>> over the provenance of the artifacts.
>>>>>
>>>>> On Wed, May 2, 2018 at 9:30 PM, Chris Lambertus cml@apache.org wrote:
>>>>>
>>>>> On May 2, 2018, at 5:51 PM, Jun Liu liujun@apache.org wrote:
>>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> We are preparing for the first apache incubating release for dubbo,
>>>>>> turns
>>>>>>
>>>>>> out we lack of some nexus permissions, this blocks our process.
>>>>>>
>>>>>> Could someone help us please? Here is the ticket asking permissions :
>>>>>>
>>>>>> https://issues.apache.org/jira/browse/INFRA-16451
>>>>>>
>>>>>> Best regards,
>>>>>>
>>>>>> Jun
>>>>>>
>>>>>> I don’t know how to approach this when the groupID doesn’t match
>>>>>>
>>>>>> org.apache.
>>>>>>
>>>>>> I’ve requested help from the Sonatype folks.
>>>>>>
>>>>>> -Chris
>>>>>>
>>>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
>>> For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
>>>
>>> For further information about the NetBeans mailing lists, visit:
>>> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>>>
>>>
>>>
>>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
>> For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
>>
>> For further information about the NetBeans mailing lists, visit:
>> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>>
>>
>>
>>
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
For additional commands, e-mail: dev-help@netbeans.incubator.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

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

[Geertjan Wielenga <ge...@googlemail.com.INVALID>]

You are right. If you know what needs to be done, do it.

Gj



On Monday, November 12, 2018, Antonio <an...@vieiro.net> wrote:

> Hi all,
>
> Recovering this old thread of may 2018...
>
> Since the ASF now owns the netbeans.org domain, that means that we can
> now publish artifacts to Maven Central using the netbeans.org domain.
>
> So there's no need to host a NetBeans Nexus Repository ourselves under
> http://bits.netbeans.org/nexus (serving binaries out of the Apache Mirror
> System is problematic, AFAIK).
>
> Am I right?
>
> Thanks,
> Antonio
>
>
> El 10/5/18 a las 0:30, Emilian Bold escribió:
>
>> So, no official Maven artifacts until Apache gets the netbeans.org
>> domain too?
>>
>> I wonder, since people would still have to edit their pom.xml files to
>> update the version -- would it really be so hard to switch to org.apache
>> groupIDs?
>>
>> We still keep the package names, etc. just change these Maven-specific
>> coordinates.
>>
>> --emi
>>
>> ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
>>
>> On 8 May 2018 8:56 PM, Greg Stein <gs...@gmail.com> wrote:
>>
>> Hi all,
>>>
>>> I wanted to send a note that Infra has seen a couple requests from
>>> podlings
>>>
>>> to publish under third-party Maven groupId coordinates (com.alibaba and
>>>
>>> org.netbeans). Unless/until the Foundation owns these domains, we cannot
>>>
>>> allow publishing under those coordinates.
>>>
>>> Needless to say, we'll never own alibaba.com :p ... Maybe one day, we'll
>>>
>>> get netbeans.org (what is the status on that?) ... But we cannot publish
>>>
>>> convenience binaries to Maven Central before such time.
>>>
>>> And please note that I said "convenience binaries". This is an important
>>>
>>> point for the two podlings: the Foundation makes source code releases.
>>>
>>> Period. Full stop. Both podlings can do that today -- there is nothing
>>>
>>> inhibiting making such releases. ... What cannot be done is publishing
>>>
>>> convenience binaries to those third-party coordinates.
>>>
>>> The podlings will be able to publish under org.apache, 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 brianf@infinity.nu wrote:
>>>
>>> Was there discussion somewhere that decided to allow an Apache project
>>>>
>>>> to publish coordinates using com.alibaba? From my perspective this is
>>>>
>>>> highly unusual for an ASF project. From a central point of view, the
>>>>
>>>> fact that com.alibaba is registered to publish from a completely
>>>>
>>>> different repo (oss.sonatype.org) this creates potential for confusion
>>>>
>>>> over the provenance of the artifacts.
>>>>
>>>> On Wed, May 2, 2018 at 9:30 PM, Chris Lambertus cml@apache.org wrote:
>>>>
>>>> On May 2, 2018, at 5:51 PM, Jun Liu liujun@apache.org wrote:
>>>>>
>>>>> Hi,
>>>>>
>>>>> We are preparing for the first apache incubating release for dubbo,
>>>>> turns
>>>>>
>>>>> out we lack of some nexus permissions, this blocks our process.
>>>>>
>>>>> Could someone help us please? Here is the ticket asking permissions :
>>>>>
>>>>> https://issues.apache.org/jira/browse/INFRA-16451
>>>>>
>>>>> Best regards,
>>>>>
>>>>> Jun
>>>>>
>>>>> I don’t know how to approach this when the groupID doesn’t match
>>>>>
>>>>> org.apache.
>>>>>
>>>>> I’ve requested help from the Sonatype folks.
>>>>>
>>>>> -Chris
>>>>>
>>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
>> For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
>>
>> For further information about the NetBeans mailing lists, visit:
>> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>>
>>
>>
>>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
> For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>
>

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

[Antonio <an...@vieiro.net>]

Hi all,

Recovering this old thread of may 2018...

Since the ASF now owns the netbeans.org domain, that means that we can 
now publish artifacts to Maven Central using the netbeans.org domain.

So there's no need to host a NetBeans Nexus Repository ourselves under 
http://bits.netbeans.org/nexus (serving binaries out of the Apache 
Mirror System is problematic, AFAIK).

Am I right?

Thanks,
Antonio


El 10/5/18 a las 0:30, Emilian Bold escribió:
> So, no official Maven artifacts until Apache gets the netbeans.org domain too?
> 
> I wonder, since people would still have to edit their pom.xml files to update the version -- would it really be so hard to switch to org.apache groupIDs?
> 
> We still keep the package names, etc. just change these Maven-specific coordinates.
> 
> --emi
> 
> ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
> 
> On 8 May 2018 8:56 PM, Greg Stein <gs...@gmail.com> wrote:
> 
>> Hi all,
>>
>> I wanted to send a note that Infra has seen a couple requests from podlings
>>
>> to publish under third-party Maven groupId coordinates (com.alibaba and
>>
>> org.netbeans). Unless/until the Foundation owns these domains, we cannot
>>
>> allow publishing under those coordinates.
>>
>> Needless to say, we'll never own alibaba.com :p ... Maybe one day, we'll
>>
>> get netbeans.org (what is the status on that?) ... But we cannot publish
>>
>> convenience binaries to Maven Central before such time.
>>
>> And please note that I said "convenience binaries". This is an important
>>
>> point for the two podlings: the Foundation makes source code releases.
>>
>> Period. Full stop. Both podlings can do that today -- there is nothing
>>
>> inhibiting making such releases. ... What cannot be done is publishing
>>
>> convenience binaries to those third-party coordinates.
>>
>> The podlings will be able to publish under org.apache, 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 brianf@infinity.nu wrote:
>>
>>> Was there discussion somewhere that decided to allow an Apache project
>>>
>>> to publish coordinates using com.alibaba? From my perspective this is
>>>
>>> highly unusual for an ASF project. From a central point of view, the
>>>
>>> fact that com.alibaba is registered to publish from a completely
>>>
>>> different repo (oss.sonatype.org) this creates potential for confusion
>>>
>>> over the provenance of the artifacts.
>>>
>>> On Wed, May 2, 2018 at 9:30 PM, Chris Lambertus cml@apache.org wrote:
>>>
>>>> On May 2, 2018, at 5:51 PM, Jun Liu liujun@apache.org wrote:
>>>>
>>>> Hi,
>>>>
>>>> We are preparing for the first apache incubating release for dubbo, turns
>>>>
>>>> out we lack of some nexus permissions, this blocks our process.
>>>>
>>>> Could someone help us please? Here is the ticket asking permissions :
>>>>
>>>> https://issues.apache.org/jira/browse/INFRA-16451
>>>>
>>>> Best regards,
>>>>
>>>> Jun
>>>>
>>>> I don’t know how to approach this when the groupID doesn’t match
>>>>
>>>> org.apache.
>>>>
>>>> I’ve requested help from the Sonatype folks.
>>>>
>>>> -Chris
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
> For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
> 
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
> 
> 
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
For additional commands, e-mail: dev-help@netbeans.incubator.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

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

[Emilian Bold <em...@protonmail.ch>]

So, no official Maven artifacts until Apache gets the netbeans.org domain too?

I wonder, since people would still have to edit their pom.xml files to update the version -- would it really be so hard to switch to org.apache groupIDs?

We still keep the package names, etc. just change these Maven-specific coordinates.

--emi

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐

On 8 May 2018 8:56 PM, Greg Stein <gs...@gmail.com> wrote:

> Hi all,
> 
> I wanted to send a note that Infra has seen a couple requests from podlings
> 
> to publish under third-party Maven groupId coordinates (com.alibaba and
> 
> org.netbeans). Unless/until the Foundation owns these domains, we cannot
> 
> allow publishing under those coordinates.
> 
> Needless to say, we'll never own alibaba.com :p ... Maybe one day, we'll
> 
> get netbeans.org (what is the status on that?) ... But we cannot publish
> 
> convenience binaries to Maven Central before such time.
> 
> And please note that I said "convenience binaries". This is an important
> 
> point for the two podlings: the Foundation makes source code releases.
> 
> Period. Full stop. Both podlings can do that today -- there is nothing
> 
> inhibiting making such releases. ... What cannot be done is publishing
> 
> convenience binaries to those third-party coordinates.
> 
> The podlings will be able to publish under org.apache, 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 brianf@infinity.nu wrote:
> 
> > Was there discussion somewhere that decided to allow an Apache project
> > 
> > to publish coordinates using com.alibaba? From my perspective this is
> > 
> > highly unusual for an ASF project. From a central point of view, the
> > 
> > fact that com.alibaba is registered to publish from a completely
> > 
> > different repo (oss.sonatype.org) this creates potential for confusion
> > 
> > over the provenance of the artifacts.
> > 
> > On Wed, May 2, 2018 at 9:30 PM, Chris Lambertus cml@apache.org wrote:
> > 
> > > On May 2, 2018, at 5:51 PM, Jun Liu liujun@apache.org wrote:
> > > 
> > > Hi,
> > > 
> > > We are preparing for the first apache incubating release for dubbo, turns
> > > 
> > > out we lack of some nexus permissions, this blocks our process.
> > > 
> > > Could someone help us please? Here is the ticket asking permissions :
> > > 
> > > https://issues.apache.org/jira/browse/INFRA-16451
> > > 
> > > Best regards,
> > > 
> > > Jun
> > > 
> > > I don’t know how to approach this when the groupID doesn’t match
> > > 
> > > org.apache.
> > > 
> > > I’ve requested help from the Sonatype folks.
> > > 
> > > -Chris



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
For additional commands, e-mail: dev-help@netbeans.incubator.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

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

[Ted Dunning <te...@gmail.com>]

Greg has it all correct.

But nothing prevents Alibaba from publishing under coordinates that they
control.

It needs to be clear however that it is alibaba publishing there, not
Apache.

On Tue, May 8, 2018, 13:56 Greg Stein <gs...@gmail.com> wrote:

> Hi all,
>
> I wanted to send a note that Infra has seen a couple requests from podlings
> to publish under third-party Maven groupId coordinates (com.alibaba and
> org.netbeans). Unless/until the Foundation owns these domains, we cannot
> allow publishing under those coordinates.
>
> Needless to say, we'll never own alibaba.com :p ... Maybe one day, we'll
> get netbeans.org (what is the status on that?) ... But we cannot publish
> convenience binaries to Maven Central before such time.
>
> And please note that I said "convenience binaries". This is an important
> point for the two podlings: the Foundation makes source code releases.
> Period. Full stop. Both podlings can do that today -- there is nothing
> inhibiting making such releases. ... What *cannot* be done is publishing
> convenience binaries to those third-party coordinates.
>
> The podlings will be able to publish under org.apache, 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 <br...@infinity.nu> wrote:
>
> > Was there discussion somewhere that decided to allow an Apache project
> > to publish coordinates using com.alibaba? From my perspective this is
> > highly unusual for an ASF project. From a central point of view, the
> > fact that com.alibaba is registered to publish from a completely
> > different repo (oss.sonatype.org) this creates potential for confusion
> > over the provenance of the artifacts.
> >
> > On Wed, May 2, 2018 at 9:30 PM, Chris Lambertus <cm...@apache.org> wrote:
> > >
> > >
> > > On May 2, 2018, at 5:51 PM, Jun Liu <li...@apache.org> wrote:
> > >
> > > Hi,
> > >
> > > We are preparing for the first apache incubating release for dubbo,
> turns
> > > out we lack of some nexus permissions, this blocks our process.
> > >
> > > Could someone help us please? Here is the ticket asking permissions :
> > > https://issues.apache.org/jira/browse/INFRA-16451
> > >
> > > Best regards,
> > > Jun
> > >
> > >
> > >
> > > I don’t know how to approach this when the groupID doesn’t match
> > org.apache.
> > > I’ve requested help from the Sonatype folks.
> > >
> > > -Chris
> > >
> >
>

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

[Ted Dunning <te...@gmail.com>]

Greg has it all correct.

But nothing prevents Alibaba from publishing under coordinates that they
control.

It needs to be clear however that it is alibaba publishing there, not
Apache.

On Tue, May 8, 2018, 13:56 Greg Stein <gs...@gmail.com> wrote:

> Hi all,
>
> I wanted to send a note that Infra has seen a couple requests from podlings
> to publish under third-party Maven groupId coordinates (com.alibaba and
> org.netbeans). Unless/until the Foundation owns these domains, we cannot
> allow publishing under those coordinates.
>
> Needless to say, we'll never own alibaba.com :p ... Maybe one day, we'll
> get netbeans.org (what is the status on that?) ... But we cannot publish
> convenience binaries to Maven Central before such time.
>
> And please note that I said "convenience binaries". This is an important
> point for the two podlings: the Foundation makes source code releases.
> Period. Full stop. Both podlings can do that today -- there is nothing
> inhibiting making such releases. ... What *cannot* be done is publishing
> convenience binaries to those third-party coordinates.
>
> The podlings will be able to publish under org.apache, 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 <br...@infinity.nu> wrote:
>
> > Was there discussion somewhere that decided to allow an Apache project
> > to publish coordinates using com.alibaba? From my perspective this is
> > highly unusual for an ASF project. From a central point of view, the
> > fact that com.alibaba is registered to publish from a completely
> > different repo (oss.sonatype.org) this creates potential for confusion
> > over the provenance of the artifacts.
> >
> > On Wed, May 2, 2018 at 9:30 PM, Chris Lambertus <cm...@apache.org> wrote:
> > >
> > >
> > > On May 2, 2018, at 5:51 PM, Jun Liu <li...@apache.org> wrote:
> > >
> > > Hi,
> > >
> > > We are preparing for the first apache incubating release for dubbo,
> turns
> > > out we lack of some nexus permissions, this blocks our process.
> > >
> > > Could someone help us please? Here is the ticket asking permissions :
> > > https://issues.apache.org/jira/browse/INFRA-16451
> > >
> > > Best regards,
> > > Jun
> > >
> > >
> > >
> > > I don’t know how to approach this when the groupID doesn’t match
> > org.apache.
> > > I’ve requested help from the Sonatype folks.
> > >
> > > -Chris
> > >
> >
>