[ http://issues.apache.org/jira/browse/BEEHIVE-393?page=comments#action_63445 ] Bryan Che commented on BEEHIVE-393: -----------------------------------
For point 1, I added in revision 164120 the ability to build a distribution without updating the controls from controlhaus. To do this, pass in a "update.controlhaus=false" property to build.dist. e.g. ant build.dist -Dupdate.controlhaus=false > Need finer-grained control over what controls go in archives > ------------------------------------------------------------ > > Key: BEEHIVE-393 > URL: http://issues.apache.org/jira/browse/BEEHIVE-393 > Project: Beehive > Type: Bug > Components: Controls, Build > Versions: V1Beta > Environment: any > Reporter: Heather Stephens > Fix For: V1 > > We need finer-grained control over what controls end up in the archives we > post, especially for bits we officially ship (as opposed to snapshots). > 1. I build and run DRTs. This gets me a new version of controls from > controlhaus. When I run the build.dist.* targets, I also get new versions of > controls ... yet I ran tests on something different than what ends up in my > archives and what eventually ships. We will want to test exactly what ships > rather than a slightly outdated combination of Apache and Controlhaus bits. > (Even if we don't yet have tests for the controls on Beehive, the principle > remains the same.) > 2. We probably should put information in a README in the appropriate > archives stating what version of the controlhaus controls are in that version > of the distribution. Even if we don't put this information there or on the > website or somewhere else, we obviously should know what is "in the box" for > our own info. > Since we don't currently plan to checkin the control jars and since we aren't > grabbing a "locked-down and shipped version" of each control, I wonder if we > should have the ability to specify the changelist number(s) to sync to at > controlhaus.org ... default grabs the latest ... or something along those > lines. -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira
