You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Jukka Zitting (JIRA)" <ji...@apache.org> on 2010/01/07 15:48:54 UTC
[jira] Created: (JCR-2455) Automatic staging of the non-Maven
release artefacts
Automatic staging of the non-Maven release artefacts
----------------------------------------------------
Key: JCR-2455
URL: https://issues.apache.org/jira/browse/JCR-2455
Project: Jackrabbit Content Repository
Issue Type: Improvement
Components: maven
Reporter: Jukka Zitting
Assignee: Jukka Zitting
Priority: Minor
Currently the Jackrabbit release process includes the following manual steps in addition to the standard Maven release plugin invocations:
<script>
VERSION=x.y.z # Release version number
# Prepare the release directory
mkdir target/$VERSION
# Copy the main release artifacts created in the release:perform stage
cp target/checkout/RELEASE-NOTES.txt target/$VERSION
cp target/checkout/target/jackrabbit-$VERSION-src.zip* target/$VERSION
cp target/checkout/jackrabbit-webapp/target/jackrabbit-webapp-$VERSION.war* target/$VERSION
cp target/checkout/jackrabbit-jca/target/jackrabbit-jca-$VERSION.rar* target/$VERSION
cp target/checkout/jackrabbit-standalone/target/jackrabbit-standalone-$VERSION.jar* target/$VERSION
# Add MD5 and SHA1 checksums
for BINARY in target/$VERSION/*.zip target/$VERSION/*ar; do
openssl md5 < $BINARY > $BINARY.md5
openssl sha1 < $BINARY > $BINARY.sha
done
# Upload the release directory to people.apache.org
scp -r target/$VERSION people.apache.org:public_html/jackrabbit/$VERSION
</script>
I'd like to automate these steps.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (JCR-2455) Automatic staging of the non-Maven
release artefacts
Posted by "Jukka Zitting (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-2455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jukka Zitting resolved JCR-2455.
--------------------------------
Resolution: Fixed
Fix Version/s: 2.0.0
Done in revision 896908.
> Automatic staging of the non-Maven release artefacts
> ----------------------------------------------------
>
> Key: JCR-2455
> URL: https://issues.apache.org/jira/browse/JCR-2455
> Project: Jackrabbit Content Repository
> Issue Type: Improvement
> Components: maven
> Reporter: Jukka Zitting
> Assignee: Jukka Zitting
> Priority: Minor
> Fix For: 2.0.0
>
>
> Currently the Jackrabbit release process includes the following manual steps in addition to the standard Maven release plugin invocations:
> <script>
> VERSION=x.y.z # Release version number
> # Prepare the release directory
> mkdir target/$VERSION
> # Copy the main release artifacts created in the release:perform stage
> cp target/checkout/RELEASE-NOTES.txt target/$VERSION
> cp target/checkout/target/jackrabbit-$VERSION-src.zip* target/$VERSION
> cp target/checkout/jackrabbit-webapp/target/jackrabbit-webapp-$VERSION.war* target/$VERSION
> cp target/checkout/jackrabbit-jca/target/jackrabbit-jca-$VERSION.rar* target/$VERSION
> cp target/checkout/jackrabbit-standalone/target/jackrabbit-standalone-$VERSION.jar* target/$VERSION
> # Add MD5 and SHA1 checksums
> for BINARY in target/$VERSION/*.zip target/$VERSION/*ar; do
> openssl md5 < $BINARY > $BINARY.md5
> openssl sha1 < $BINARY > $BINARY.sha
> done
> # Upload the release directory to people.apache.org
> scp -r target/$VERSION people.apache.org:public_html/jackrabbit/$VERSION
> </script>
> I'd like to automate these steps.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.