[ http://issues.apache.org/jira/browse/BEEHIVE-29?page=history ]
Jim Cummings updated BEEHIVE-29:
--------------------------------
Attachment: patch.txt
rev-readme-trailer.txt
toplvl-readme-trailer.txt
Eddie,
Could you review and apply this patch (the 2 new separately attached files go
into docs/dist-docs)?
NOTE - build.dist.archives no longer has dependencies - it is able to be
chained with other targets without redoing work. To do a full build of
everything from scratch into archives, use the new target build.dist.full (does
a clean, deploy, build.dist, build.dist.lib, build.dist.src and
build.dist.archives).
This helps better automate bundling distributions for nightly builds and other
similar rollups. You should be able to run this with the nighly cronjob
scripts I gave you to do nightly builds now.
- Added a new top-level target build.dist.full to do a clean build all the way
into archives.
- Added a source distribution build (via build.dist.src target)
- The target build.dist.archives now verifies the archives are all basically ok
(not corrupt and have Apache Licenses and Notices, and READMEs as appropriate)
- Added a top-level README outside the binary and source distribution archives
- Put SVN revision numbers into the appropriate READMEs (part of Jira issue 393)
- Automated running Julie's dist tests so we can run the DRTs/BVTs against the
dist archives via the target run.test.dist.
> Apache infrastructure for regular builds, serving distributions (gump/maven
> integration)
> ----------------------------------------------------------------------------------------
>
> Key: BEEHIVE-29
> URL: http://issues.apache.org/jira/browse/BEEHIVE-29
> Project: Beehive
> Type: Task
> Versions: V1Alpha
> Reporter: Kenneth Tam
> Assignee: Eddie O'Neil
> Fix For: V1
> Attachments: patch.txt, rev-readme-trailer.txt, toplvl-readme-trailer.txt
>
> Beehive needs some Apache infrastructure work to expose regular (nightly?)
> builds/distributions. At first glance, this seems like it'll involve
> Gump/Maven, but details are unclear.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
