Martin,

Please make all changes on the branch as well.
We are making the release from the branch.

Regards,

Rajith

On 11/16/06, Martin Ritchie <[EMAIL PROTECTED]> wrote:

The updated build.xml is now in the trunk and should address both
points 1 and 5 of Brian's email.

On 16/11/06, Martin Ritchie <[EMAIL PROTECTED]> wrote:
> Thanks Gordon I just realised that was what Brian was referring to.
>
> I also realised that windows has been creating the initial directory
> for me. I thought the files were all included in a directory so I have
> adjusted that aswell.
>
> On 16/11/06, Gordon Sim <[EMAIL PROTECTED]> wrote:
> > Martin Ritchie wrote:
> > > Brian,
> > >
> > > What version of ant were you using? I just checked out M1 and did
> > > ant
> > > ant std-release
> > > and everything worked fine.
> > > I'm using ant 1.6.5 with java 1.5.0_08 on XP.
> > > I don't believe I have any local peculiarities that would impact the
> > > builds.
> > >
> > > My only thoughts are that the systests where not checked out for
some
> > > reason. Can you do an svn update and try again for us.
> >
> > I believe the point is that the released source tarball doesn't build
> > (i.e. it is not an issue of building from svn). I get the same error.
> >
> > It looks like the systests aren't part of the released source, but
they
> > are still referred to by the build file (i.e. the 'preparereleasesrc'
> > copies only broker, client, common & cluster, but the build target
> > iterates over all the listed modules of which systests is one).
> >
> > I'm not sure whether the intention is to ship systests, or whether we
> > need to ensure that the shipped build file can cope without it being
there.
> >
>
>
> --
> Martin Ritchie
>


--
Martin Ritchie

Reply via email to