You are indeed correct. I didn't actually look at the script before mentioning 
it as I just presumed it was the Git addition that did it hehe. Oh well, still 
needs fixing :) 

I'll look at it tomorrow, shouldn't take long to add a property check. I'll 
probably standardise the different areas that doo it too as I think they do it 
independently and slightly differently, and I recall there being an issue 
whereby if you dont actually have the svnversion command on your path Ant 
encounters an infinite loop property definition and refuses to build a second 
time ;)

Robbie

> -----Original Message-----
> From: Andrew Stitcher [mailto:astitc...@redhat.com]
> Sent: 09 December 2009 22:24
> To: dev@qpid.apache.org
> Subject: RE: First Qpid 0.6 Beta Release available for download and
> testing
> 
> On Wed, 2009-12-09 at 22:01 +0000, Robbie Gemmell wrote:
> > No that explains it, it's just the same effect as using git would
> have caused, I just assumed since you added that... :)
> >
> > By using svn export you don't get the .svn/ metadata directories
> within each directory, and so svnversion cant detect the version when
> run and assumes it was exported (which in this case, it actually was).
> >
> > I will have a look at updating the Ant scripting to allow specifying
> the revision to handle this.
> 
> FWIW in that case this isn't a regression as I believe previous
> releases
> were produced using svn export also.
> 
> A
> 
> 
> 
> ---------------------------------------------------------------------
> Apache Qpid - AMQP Messaging Implementation
> Project:      http://qpid.apache.org
> Use/Interact: mailto:dev-subscr...@qpid.apache.org



---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

Reply via email to