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 Wed, 25 Nov 2009 11:08: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-1a-SetDerbyVersion.diff

Attaching patch 1a, which adds a Java class that takes care of replacing the version tags
in the POMs. It also does some basic sanity checking of the jars that will be included in
the Maven artifacts. I did this to make the process more equal on all platforms.
I also updated README.txt.

Patch ready for review.

In addition to this, I'm working on writing new instructions for generating and publishing
Maven 2 artifacts. The home of these instructions will be http://wiki.apache.org/db-derby/DerbySnapshotOrRelease
. I haven't checked, but I think we should be able to use the Maven 2 POMs to generate artifacts
for releases off older branches as well. However, the SetDerbyVersion script as it is in patch
1a will only work with 10.5 and later because it uses the in-memory back end. This can be
changed if required.

> 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
>         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
> 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