infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jaroslav Tulach (JIRA)" <>
Subject [jira] [Commented] (INFRA-17347) HTML/Java API doesn't propagate from to Maven Central
Date Tue, 30 Apr 2019 03:47:00 GMT


Jaroslav Tulach commented on INFRA-17347:

Related issue is being solved as INFRA-18303

> HTML/Java API doesn't propagate from to Maven Central
> ---------------------------------------------------------------------------
>                 Key: INFRA-17347
>                 URL:
>             Project: Infrastructure
>          Issue Type: Project
>          Components: maven
>            Reporter: Jaroslav Tulach
>            Assignee: Brian Fox
>            Priority: Major
> I have a problem with - I released staging repository with
NetBeans HTML/Java API version 1.6
on Thursday Nov 31, 2018, but it's content hasn't appeared in Maven Central yet.
> Thus I repeated the same steps on Saturday Dec 1, 2018 with new upload "orgapachenetbeans-1003
(org.apache.netbeans)", but that isn't working either. The repository is still visible in
the Nexus UI and is marked as "released". The bits of {{org.netbeans.html}}
JARs are available from - e.g.
local release was OK.
> Shane Curcuru replied on the infra chat: Possibly - there may be filters on either the
ASF side or the Sonatype (who runs the maven central servers) that restrict to org.apache.*.
> In any case we should find out what is wrong and fix it. is Apache
domain and groupId {{org.netbeans.html}} is thus a valid and approved Apache groupId. We should
be able to publish such bits in the future.
> Thanks in advance for your help.

This message was sent by Atlassian JIRA

View raw message