You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Kristian Waagan (JIRA)" <ji...@apache.org> on 2009/10/07 13:36:31 UTC
[jira] Created: (DERBY-4400) Document the process of producing
Maven 2 artifacts for Derby
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
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.
[jira] Updated: (DERBY-4400) Document the process of producing
Maven 2 artifacts for Derby
Posted by "Kristian Waagan (JIRA)" <ji...@apache.org>.
[ 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: 10.5.4.0, 10.6.0.0
> 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 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.
[jira] Closed: (DERBY-4400) Document the process of producing Maven
2 artifacts for Derby
Posted by "Kristian Waagan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-4400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kristian Waagan closed DERBY-4400.
----------------------------------
Closing, as there are no outstanding issues to address from the 10.6 release.
> 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.3.1, 10.6.1.0
> Reporter: Kristian Waagan
> Assignee: Kristian Waagan
> Fix For: 10.6.1.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.
[jira] Updated: (DERBY-4400) Document the process of producing
Maven 2 artifacts for Derby
Posted by "Kristian Waagan (JIRA)" <ji...@apache.org>.
[ 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: 10.5.4.0, 10.6.0.0
> 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 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.
[jira] Updated: (DERBY-4400) Document the process of producing
Maven 2 artifacts for Derby
Posted by "Kristian Waagan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-4400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kristian Waagan updated DERBY-4400:
-----------------------------------
Issue & fix info: [Patch Available]
> 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.
[jira] Updated: (DERBY-4400) Document the process of producing
Maven 2 artifacts for Derby
Posted by "Kristian Waagan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-4400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kristian Waagan updated DERBY-4400:
-----------------------------------
Issue & fix info: (was: [Patch Available])
Fix Version/s: 10.6.0.0
> 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
>
>
> 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.
[jira] Commented: (DERBY-4400) Document the process of producing
Maven 2 artifacts for Derby
Posted by "Dag H. Wanvik (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Assigned: (DERBY-4400) Document the process of producing
Maven 2 artifacts for Derby
Posted by "Kristian Waagan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-4400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kristian Waagan reassigned DERBY-4400:
--------------------------------------
Assignee: Kristian Waagan
> 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.
[jira] Commented: (DERBY-4400) Document the process of producing
Maven 2 artifacts for Derby
Posted by "Kristian Waagan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-4400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12835673#action_12835673 ]
Kristian Waagan commented on DERBY-4400:
----------------------------------------
Made some formatting changes and fixed some typos with revision 911768.
> 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.
[jira] Updated: (DERBY-4400) Document the process of producing
Maven 2 artifacts for Derby
Posted by "Kristian Waagan (JIRA)" <ji...@apache.org>.
[ 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-1c-SetDerbyVersion.diff
Attached patch 1c, which fixes some formatting and spelling errors.
Committed to trunk with revision 888385.
> 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
>
>
> 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.
[jira] Resolved: (DERBY-4400) Document the process of producing
Maven 2 artifacts for Derby
Posted by "Kristian Waagan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-4400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kristian Waagan resolved DERBY-4400.
------------------------------------
Resolution: Fixed
First revision of instructions on the wiki has been written (see http://wiki.apache.org/db-derby/DerbySnapshotOrRelease, "Deploy to Maven repository.")
I'm resolving the issue now, but I won't close it until after 10.6 has been released.
> 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.
[jira] Updated: (DERBY-4400) Document the process of producing
Maven 2 artifacts for Derby
Posted by "Kristian Waagan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-4400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kristian Waagan updated DERBY-4400:
-----------------------------------
Issue & fix info: (was: [Patch Available])
Thanks, Dag!
Committed patch 2a to trunk with revision 889126.
> 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.
[jira] Updated: (DERBY-4400) Document the process of producing
Maven 2 artifacts for Derby
Posted by "Kristian Waagan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-4400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kristian Waagan updated DERBY-4400:
-----------------------------------
Issue & fix info: [Patch Available]
> 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.
[jira] Commented: (DERBY-4400) Document the process of producing
Maven 2 artifacts for Derby
Posted by "Dag H. Wanvik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-4400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12788210#action_12788210 ]
Dag H. Wanvik commented on DERBY-4400:
--------------------------------------
Read through changes; look good to me (although I didn't test deployment -;). +1
> 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.
[jira] Updated: (DERBY-4400) Document the process of producing
Maven 2 artifacts for Derby
Posted by "Kristian Waagan (JIRA)" <ji...@apache.org>.
[ 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.