[
https://issues.apache.org/jira/browse/DERBY-4400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12782532#action_12782532
]
Dag H. Wanvik commented on DERBY-4400:
--------------------------------------
Thanks Kristian, tried the new README + the program to set the version, and I
successfully produced a local deployment.
I noted only two minor things followin gthe instructions:
- "b) Specify required information for one or all of the following
steps."
I'd prefer to use "sub-steps" here to be clear.
- "When these are deployed or installed locally, there will be a
md5 and a sha1 file for each artifact."
I also found an "asc" signature file for each artifact.
- For us Maven newbies, state that to run mvn, you should cd to
./maven2 first (step c); I was briefly confused, since step b)
did specifiy the directory to run from.
The program also refused to continue if I had both a sane and an
insane directory, good. I did my testing on OpenSolaris only.
> 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
> Attachments: derby-4400-1a-SetDerbyVersion.diff
>
>
> 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.
