[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Two questions related to SVNLOOK

From: Merten, Alexander (External) <Alexander.Merten.External_at_eads.com>
Date: Tue, 12 Feb 2008 17:04:29 +0100

Dear Subversion users,

we are at the moment attempting an integration between subversion and an Change Management / Reporting Tool.
To achieve our reporting aims, we need to relate changes made inside subversion to change object in the reporting tool.

The solution we have chosen, is to keep an object-relational layer in the reporting tool that is kept up-to-date with each change in the subversion repository. So when someone changes a file or creates a folder, etc. in subversion a hook script will send an XML message to the reporting tool informing it about those changes. There objects are created/modified according to the information in the xml message.

For implementing the hook scripts, we have chosen Java.
For accessing commit information, we call SVNLOOK from java and parse its output into our XSD transaction schema.

Since changes are primarly made in branches, those folders are of specific interest for our reporting. However, when creating a branch, the revision information (svnlook changed) only reports one line of action, namly the creation of the branch folder. It is therefore not possible to create respective objects in the reporting tool's representation.

Now for the first question: is there a simple way (rather than accessing the branch folder with SVNLOOK tree), to access the content of a branch folder?
The second questions is: how can I access the history of a single file? SVNLOOK only allows me to access the history of a folder. This information would be beneficial to create

Help on the second challenge would be especially helpful :-)

Greetings,
Alexander Merten

HOOD-Group
Center of Competence - Change, Configuration and Version Management.
Received on 2008-02-12 17:05:27 CET

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.