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 <jmbo...@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 <rcup...@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 <anto...@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 <anto...@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 <gst...@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 bri...@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 c...@apache.org
> wrote:
> >>>>>>
> >>>>>> On May 2, 2018, at 5:51 PM, Jun Liu liu...@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-unsubscr...@netbeans.incubator.apache.org
> >>>> For additional commands, e-mail:
> >>>> dev-h...@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-unsubscr...@netbeans.incubator.apache.org
> >>> For additional commands, e-mail:
> >>> dev-h...@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-unsubscr...@netbeans.incubator.apache.org
> > For additional commands, e-mail:
> > dev-h...@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-unsubscr...@netbeans.incubator.apache.org
> For additional commands, e-mail: 
> dev-h...@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-unsubscr...@netbeans.incubator.apache.org
> For additional commands, e-mail: 
> dev-h...@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-unsubscr...@netbeans.incubator.apache.org
For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org

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



Reply via email to