Forums : Technical Issue Help

Dear Open Hub Users,

We’re excited to announce that we will be moving the Open Hub Forum to https://community.blackduck.com/s/black-duck-open-hub. Beginning immediately, users can head over, register, get technical help and discuss issue pertinent to the Open Hub. Registered users can also subscribe to Open Hub announcements here.

On May 1, 2020, we will be freezing https://www.openhub.net/forums and users will not be able to create new discussions. If you have any questions and concerns, please email us at [email protected]

Best way to update the SVN URL for Apache Tuscany Project?

Hi,

The Apache Tuscany project has recently graduated from incubation to become a top level Apache project.

As a result, the SVN URLs have changed. I was wondering what the best way to update the enlistments? Ideally, I don't want to reload the whole source tree if I don't have to do so.

The old URLs are:

http://svn.apache.org/repos/asf/incubator/tuscany/cpp

http://svn.apache.org/repos/asf/incubator/tuscany/java

The new URLs are:

http://svn.apache.org/repos/asf/tuscany/cpp

http://svn.apache.org/repos/asf/tuscany/java

Thanks,

Mark

mcombellack almost 18 years ago

Hi Mark,

I'm afraid I have a fairly unsatisfying answer for you.

Ohloh's Subversion importer cannot follow project history across directory moves.

If you add the new URLs to Ohloh, we will only be able to process their histories as far back as the revision in which the new URLs were created. Everything before then will be invisible to Ohloh.

If you keep both the new and old URLs on Ohloh, we will be able to show the entire commit history, but unfortunately the total size of the code will be overcounted by a factor of two, because Ohloh will not be aware that the old and new URLs are at all related.

Also, our system will stubbornly continue to try to update the old URLs, which of course will fail because they no longer exist, and this will cause the Tuscany reports to require manual intervention for successful updates.

Given both options, I'd go with keeping both the old and new URLs on Ohloh. It's conceivable that we could write some new code to mark the old URLs as retired to prevent future updates and avoid double-counting the code. This feature doesn't seem terribly difficult for us to implement.

Let me know if I can answer any more questions,

Robin

Robin Luckey almost 18 years ago

Hi Robin,

Thanks for the reply. I've added the new enlistments as you suggested. It will be interesting to see what we wend up with once the download is completed.

Thanks,

Mark

mcombellack almost 18 years ago

Hi Robin,

The import from the new enlistments has now completed.

It appears as though it has not updated the project summaries and commit lists. I am presuming that this is because two of the enlistments failed.

I've been looking at the new SVN URLs. They appear to have the old SVN history in them too. For example, if you have a look at:

http://svn.apache.org/viewvc/tuscany/java/sca/modules/binding-ws/src/main/java/org/apache/tuscany/sca/binding/ws/DefaultWebServiceBindingFactory.java?sortby=date&view=log

The directory move can be seen as the most recent commit. The previous commits that were done to the old repository location are still listed. Will the Ohloh importer cope with this and still index the old SVN history?

If so, does this mean that I could just remove the old enlistments and just leave the new ones?

Thanks,

Mark

mcombellack almost 18 years ago

Hi Robin,

Shameless bump for this thread - sorry.

I was wondering if anyone had any comment on the above post and removing the old URLs.

Thanks,

Mark

mcombellack almost 18 years ago