[
https://issues.apache.org/jira/browse/DERBY-4400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kristian Waagan updated DERBY-4400:
-----------------------------------
Attachment: derby-4400-2a.stat
derby-4400-2a.diff
Attaching a follow-on patch 2a:
- deletes settings.xml, since most of the settings in there didn't take effect
- changes the deploy protocol from scp to scpexe, which makes Maven use
external commands to deploy (i.e. ssh and scp)
- additions and changes to the README
Following the latest instructions in README, I'm able to deploy the artifacts
using Maven. Please do not try to deploy :) The next release manager will get
the please of verifying the instructions.
I'd like someone to sanity check the changes made to the README before I commit.
Patch ready for review.
> Document the process of producing Maven 2 artifacts for Derby
> -------------------------------------------------------------
>
> Key: DERBY-4400
> URL: https://issues.apache.org/jira/browse/DERBY-4400
> Project: Derby
> Issue Type: Task
> Components: Documentation
> Affects Versions: 10.5.4.0, 10.6.0.0
> Reporter: Kristian Waagan
> Assignee: Kristian Waagan
> Fix For: 10.6.0.0
>
> Attachments: derby-4400-1a-SetDerbyVersion.diff,
> derby-4400-1b-SetDerbyVersion.diff, derby-4400-1c-SetDerbyVersion.diff,
> derby-4400-2a.diff, derby-4400-2a.stat
>
>
> The process of producing Maven 2 artifacts for Derby should be documented.
> Good and clear documentation is important for the following reasons:
> - The process is only carried out each time a Derby release is produced.
> - A part of our users are using Maven in their projects, and they depend on
> the Maven 2 artifacts to upgrade Derby.
> - It is likely that it isn't the same person carrying out the process from
> release to release.
> As a rough starting point, some points to cover:
> - Prerequisites, installation and environment setup.
> - The artifact build process.
> - Testing the artifacts.
> - Deploying the artifacts.
> - Verifying the deployment (with the central repository).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
