www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brian Demers (JIRA)" <j...@apache.org>
Subject [jira] Closed: (INFRA-3214) Push apache-log4j-extras 1.1 release to Nexus, set up Nexus for additional products
Date Wed, 24 Nov 2010 22:32:13 GMT

     [ https://issues.apache.org/jira/browse/INFRA-3214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Brian Demers closed INFRA-3214.
-------------------------------

    Resolution: Fixed

See: http://www.apache.org/dev/publishing-maven-artifacts.html

The previous releases have been moved into Nexus.

You will need to upload your current release to a staging repository in order to verify your
artifacts (signatures, javadoc, etc)


> Push apache-log4j-extras 1.1 release to Nexus, set up Nexus for additional products
> -----------------------------------------------------------------------------------
>
>                 Key: INFRA-3214
>                 URL: https://issues.apache.org/jira/browse/INFRA-3214
>             Project: Infrastructure
>          Issue Type: Task
>      Security Level: public(Regular issues) 
>          Components: Nexus
>            Reporter: Curt Arnold
>            Assignee: Brian Demers
>
> The Logging Services PMC has just concluded a release vote for log4j extras 1.1 and is
ready to push release artifacts into master maven repo. We have not previously dealt with
Nexus and build process staged to http://people.apache.org/builds/logging/repo.  Now ready
to move group log4j, artifact ID apache-log4j-extras, version 1.1 to master repo but need
help.
> Vote hasn't yet hit archives, but should appear soon:
> http://mail-archives.apache.org/mod_mbox/logging-log4j-dev/201011.mbox/thread?1
> Will also be shortly preparing releases for apache-log4j-component and apache-log4j-receivers.
 Will need to set up Nexus repos for them and then for a log4j release after that.  Any other
hints in setting up for Nexus would be appreciated.
> Project URL: http://logging.apache.org/log4j/companions/extras
> SVN URL: http://svn.apache.org/repos/asf/logging/log4j/companions/extras/trunk
> Maven Group Ids: log4j (old group id)
> Managed By This TLP Project: logging
> Project URL: http://logging.apache.org/log4j/companions/component
> SVN URL: http://svn.apache.org/repos/asf/logging/log4j/companions/component/trunk
> Maven Group Ids: log4j (old group id)
> Managed By This TLP Project: logging
> Project URL: http://logging.apache.org/log4j/companions/receivers
> SVN URL: http://svn.apache.org/repos/asf/logging/log4j/companions/receivers/trunk
> Maven Group Ids: log4j (old group id)
> Managed By This TLP Project: logging
> Project URL: http://logging.apache.org/log4j
> SVN URL: http://svn.apache.org/repos/asf/logging/log4jtrunk
> Maven Group Ids: log4j (old group id)
> Managed By This TLP Project: logging

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message