www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Thomas (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (INFRA-4162) Enable Nexus Access For TOMCAT
Date Fri, 16 Dec 2011 22:22:30 GMT

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

Mark Thomas commented on INFRA-4162:

This is nothing to do with /dist. This is solely about the artifacts published to Maven Central.

The community is affected in that the build scripts are still trying to publish Maven artifacts
via people.a.o which is now blocked. We are therefore, currently, unable to publish artifacts
to Maven Central. That impacts our users that rely on that route for obtaining Tomcat JARs.

Yes, this can be worked around by our end-users and yes it should be possible to change the
build scripts to publish via Nexus. However, the Tomcat community has not decided that it
wants to make this change. i.e. the decision to switch to Nexus was not made by the Tomcat
community on the Tomcat dev list.

My assumption is that the Tomcat community will retrospectively approve this change. However,
in case it does not, how much work is involved in reverting the switch to Nexus, restoring
the repo on people.a.o and returning to publishing via scp+rsync?
> Enable Nexus Access For TOMCAT
> ------------------------------
>                 Key: INFRA-4162
>                 URL: https://issues.apache.org/jira/browse/INFRA-4162
>             Project: Infrastructure
>          Issue Type: Task
>      Security Level: public(Regular issues) 
>          Components: Nexus
>            Reporter: Jean-Frederic Clere
>            Assignee: Brian Demers
>            Priority: Blocker
> Project URL: tomcat.apache.org
> SVN URL: http://svn.apache.org/repos/asf/tomcat/
> Maven Group Ids: org.apache.tomcat
> Managed By This TLP Project: tomcat

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message