infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eric Barboni (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (INFRA-17127) Enable Nexus Access For Apache NetBeans(incubating)
Date Tue, 23 Oct 2018 11:07:00 GMT

    [ https://issues.apache.org/jira/browse/INFRA-17127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16660446#comment-16660446
] 

Eric Barboni commented on INFRA-17127:
--------------------------------------

 (it takes time for me to elaborate)

---------------
Part html4j is the most ready,  [~jtulach] already do a lot on this point.

For me html4j part shoud the first to be tried as is already populated to central [~jtulach]
with compatible pom. At the time it was at Oracle html4j was already published to central.
Maybe we should align everything to Apache project way of publishing.

---------------
Part NetBeans IDE and tools are at early stage
For Netbeans artefacts the current maven tools generate a poor quality pom. (i.e.not licence
in it).
This will need modification of the NetBeans maven tools coming from mojo and yet at Apache
NetBeans. 

It would be nice if we can setup a staged place where we can put the "maven tool" on every
code change, so we can adjust the code to generate better pom. Another script that get the
maven tools generated to populate the staged maven2 repository place with ide artefact.

Rhough steps
0. a staged place maven2 to test (500Go of artefacts per build) with kind of a lock to be
sure it never get on central until we are sure of the artefacts quality.
1. jenkins build to populate (to a staged place) maven tool artefacts snapshot
2. jenkins build to populate (to a staged place) using maven tools snapshot the netbeans ide
artefact

Once the maven tools are ok, I guess we can ask for release for maven tools on dev list and
the related parent and libraries.






 

> Enable Nexus Access For Apache NetBeans(incubating) 
> ----------------------------------------------------
>
>                 Key: INFRA-17127
>                 URL: https://issues.apache.org/jira/browse/INFRA-17127
>             Project: Infrastructure
>          Issue Type: Task
>          Components: Nexus
>            Reporter: Eric Barboni
>            Assignee: Gavin
>            Priority: Major
>
> Hi, 
> for Apache NetBeans (incubating) we would like to publish maven artefacts to  keep previous
feature that were available at http://bits.netbeans.org/maven2/ that may go to maven central.
> How we suppose it was working before:
> Apache NetBeans (incubating) is built using Apache Ant,ant will generate jar and nbms
files,sources and javadocs.
> Then a maven tools get the artefacts and build pom and populate a maven 2 repository
. 
> Tools are under vote for ip-clearance and donation is in progress (https://issues.apache.org/jira/browse/NETBEANS-1335)
> Releasing milestone
> Build is done on a branch and the artefacts get a forced version in the pom  like <version>RELEASE82</version>
for Netbeans 8.2 or
> <version>RELEASE82-BETA</version> for Netbeans 8.2 Beta1
> Releasing snapshots
> Build is done daily on the master and the artefact were populated using SNAPSHOT and
dev-SNAPSHOT as a version in the pom. The snapshot is unique (no snapshot history). 
> Best Regards
> Eric
> Information according to the template:
>  
> Project URL:
> http://netbeans.apache.org/
> SVN URL:
> https://gitbox.apache.org/repos/asf?p=incubator-netbeans.git
> Maven Group Ids:
> prefered candidate: org.netbeans 
> (previous groupId, netbeans.org is under transfert to apache 
> https://issues.apache.org/jira/browse/INFRA-16946)
> fallback to org.apache.netbeans
> after the root group id there will be group: api,clusters,external,modules
> Managed By This TLP Project:
> N/A (Incubator for now)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message