Billie, I am not trying to change anything for 1.3.5.
I didn't know if the 'I checked out the tag and ...' comment in the email indicated a permanent process or a temporary one. If a permanent process, it would be less work for release managers if the mvn build did the whole thing if possible; other projects manage that with sufficient use of the assembly plugin and the support from the top-level Apache parent POM. If you're already on top of this, send me away. -benson On Mon, Nov 28, 2011 at 9:41 AM, Billie J Rinaldi <[email protected]> wrote: > On Sunday, November 27, 2011 4:03:44 PM, "Benson Margulies" > <[email protected]> wrote: >> Any particular for the manual release bundling instead of using the >> assembly plugin and the release plugin? Or have I misunderstood Eric's >> process? > > Benson, > > Are you referring to the 'tar' portion of the bundling or the 'build.sh' > portion, or both? The 'tar' is being using used to create a source-only > distribution, which we have not been generating until now. It didn't seem > like a good idea to try to change the build process since the 1.3.5 release > was otherwise ready. The 'build.sh' script runs a series of maven commands > as well as building some native c++ libraries. > > Billie >
