db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kristian Waagan (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-4400) Document the process of producing Maven 2 artifacts for Derby
Date Thu, 26 Nov 2009 11:16:39 GMT

     [ 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-1b-SetDerbyVersion.diff

Thanks for looking at the patch, Dag.

I have made more changes, which means there may be more things to fix now ;)
I hope I haven't included too much information. I think I'll refer to the README in the release
process documentation, and only outline the overall steps there.

The instructions for deploying worked for me when deploying locally on my own machine (note
that this is 'mvn deploy', not 'mvn install'). All you need to test this is to allow scp connections
and [parts of] the directory structure has to exist. NOTE: You also have to change the repository
tag in the top-level POM.
Since the Apache repos is write-once, I'll try to deploy there (the changes will be ignored
and nothing will be distributed to the central repos).

Besides from reviewing the documentation changes, the instructions and the Java program need
to be tested on Windows. I know Windows users have gotten into trouble before, and I'm not
sure if the deploy step will work. In that case, we may have to update the instructions on
how to specify a different program to transfer the artifacts to the repos.

Patch ready for further comments.

> 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:,
>            Reporter: Kristian Waagan
>            Assignee: Kristian Waagan
>         Attachments: derby-4400-1a-SetDerbyVersion.diff, derby-4400-1b-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
> 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.

View raw message