infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Struberg (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (INFRA-16435) Enable Nexus Access For NetBeans
Date Wed, 16 May 2018 11:00:00 GMT

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

Mark Struberg commented on INFRA-16435:
---------------------------------------

[~cml] how did we handle this with commons-logging/commons-logging or log4j/log4j or org.codehaus.groovy?
Yes, org.apache.* is the default, but we have quite a few projects which do not use this groupId
for historic reasons, right?

> Enable Nexus Access For NetBeans
> --------------------------------
>
>                 Key: INFRA-16435
>                 URL: https://issues.apache.org/jira/browse/INFRA-16435
>             Project: Infrastructure
>          Issue Type: Task
>          Components: Nexus
>            Reporter: Jaroslav Tulach
>            Assignee: Chris Thistlethwaite
>            Priority: Major
>              Labels: maven, netbeans
>
> Project URL: http://netbeans.apache.org/
> SVN URL: https://github.com/apache/incubator-netbeans-html4j.git to begin with and (later)
https://github.com/apache/incubator-netbeans.git - the first one is Maven based and should
be straightforward. The latter uses some special upload mechanism that will need to be adjusted
to Apache infrastructure.
> Maven Group Ids: For compatibility reasons with current code and because netbeans.org
is fully owned by Apache, I suggest to stick with current groups. : org.netbeans.html (for
HTML/Java API) and org.netbeans.xxx (see http://bits.netbeans.org/nexus/content/groups/netbeans/org/netbeans/)
where xxx can be api, modules, external, cluster
> Managed By This TLP Project:



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

Mime
View raw message