[
https://issues.apache.org/jira/browse/WHIRR-85?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tom White updated WHIRR-85:
---------------------------
Attachment: WHIRR-85.patch
This patch changes the top-level POM to inherit from the Apache POM so we can
push to the Apache Maven repos easily. I've tested it sufficiently to push to
the snapshot repo and the staging repo using the release instructions we have
now. (I had to upgrade to Maven 2.2.1 to avoid some problems with checksum
failures, see http://jira.codehaus.org/browse/MNG-4301.)
I think we should defer using the Maven release plugin to a later issue.
> Publish Maven artifacts to http://repository.apache.org
> -------------------------------------------------------
>
> Key: WHIRR-85
> URL: https://issues.apache.org/jira/browse/WHIRR-85
> Project: Whirr
> Issue Type: Sub-task
> Components: core
> Reporter: Tom White
> Assignee: Tom White
> Priority: Blocker
> Fix For: 0.1.0
>
> Attachments: WHIRR-85.patch
>
>
> The release instructions at
> https://cwiki.apache.org/confluence/display/WHIRR/How+To+Release use the
> legacy Maven repos. We should follow the new process described in
> http://www.apache.org/dev/publishing-maven-artifacts.html. To do this
> requires getting Whirr set up on Nexus (I opened INFRA-2969 for this), and
> then modifying the top-level POM and release instructions to support the
> standard process.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
