[
https://issues.apache.org/jira/browse/HCATALOG-619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alan Gates reopened HCATALOG-619:
---------------------------------
I backed this change out and re-opened the issue because it caused the builds
to fail. I think the failures are because somehow the versions in the pom.xml
files got set to 1.0-gates instead of 0.6.0-SNAPSHOT. I'm not sure how that
happened or if that's the only issue. For now I'm justing backing it out so I
can move the code to Hive. Then we can sort out what I did wrong here.
> Update HCatalog test/release script with post-release improvements
> ------------------------------------------------------------------
>
> Key: HCATALOG-619
> URL: https://issues.apache.org/jira/browse/HCATALOG-619
> Project: HCatalog
> Issue Type: Bug
> Components: documentation
> Reporter: Travis Crawford
> Assignee: Travis Crawford
> Attachments: HCATALOG-619.1.patch,
> HCATALOG-619_release_script_update.2.patch
>
>
> [test.sh|http://svn.apache.org/repos/asf/incubator/hcatalog/trunk/build-support/scripts/test.sh]
> is a script that contains all test commands one should run on a regular
> basis, such as before posting a patch, and before committing. Currently we
> require users to set FORREST_HOME, but do not actually generate the site. As
> the primary purpose of {{test.sh}} is comprehensively generating our
> artifacts & running tests, I think we should generate the site too. This
> hopefully encourages people to update documentation along with their code
> changes (I'm definitely guilty of not doing this) and makes sure we do not
> break the site generation.
> Prior to HCATALOG-184, running the {{package}} Ant target would trigger
> generating the website. That's quite a useful change as its optimized for the
> developer workflow which often requires building a package for testing. We
> still have this developer-focused optimization in place as "ant clean
> package" and "ant clean test" will not generate the site.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
