On Tue, Nov 18, 2008 at 4:15 PM, Ian Boston <[EMAIL PROTECTED]> wrote:
> > I can do a maven assembly plugin to generate the artifacts (including the > php tarball) and check that the release plugin works. > > I assume that the php tarball just need to be the source tree, excluding > the java subtree... or is it more complex than that ? > The least-effort solution is to gather shindig/* -java the java dir, this way everything would work without any moving or reconfiguring. I might take a quick look tomorrow to see if it would be 'easier' for the end-users if in the release tarbal everything is moved around a bit, but due to the confusion this is bound to cause if people then switch to svn or read svn based docs, I don't think this is likely to be the best solution. So yeah, your solution sounds good :)
