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.

Robbie

> -----Original Message-----
> From: Andrew Stitcher [mailto:astitc...@redhat.com]
> Sent: 09 December 2009 21:55
> To: dev@qpid.apache.org
> Subject: RE: First Qpid 0.6 Beta Release available for download and
> testing
> 
> On Wed, 2009-12-09 at 20:36 +0000, Robbie Gemmell wrote:
> > I have updated (r888939) the build process to and release script so
> the QMan package is generated and copied over.
> >
> > Additionally, I have noticed that because you are using Git
> (presumably, since the ability was added recently) to do the checkout
> the Java modules are failing to identify the SVN revision used in the
> build and so are generating property files that contain "exported"
> where the revision should be, since svnversion didnt find the .svn
> folders. As a result, "exported" will show up wherever the revision
> would normally be mentioned, eg broker startup.
> >
> 
> The actual released artifacts were produced from an svn export, not git
> - that was for convenience leading up to a final release as "svn
> export"
> is slow because it needs to go over the internet.
> 
> So that doesn't explain this (unless I've made a mistake).
> 
> Andrew
> 
> > One way to handle this would be to add a property in the ant build
> process that can be set via command line in the release script with the
> value parsed from Git, and modify the build process to only use
> svnversion to figure it out the revision if that hasn't been set.
> 
> That's certainly not in my skill set re java, I'm just about capable of
> running release.sh and seeing whether java built!
> 
> Andrew
> 
> 
> 
> ---------------------------------------------------------------------
> 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