FishEye LoC chart not supoorted for Mercurial repositories

[Herbert Hotz]

I'm using the JIRA 5.1 bundled FishEye plugin.

We have installed standalone FishEye fecru-2.7.15.

We use Mercurial repositories.

Unfortunately the chart LoC for Mercurial repositories is not supported in the above versions,

see https://confluence.atlassian.com/display/FISHEYE/Cannot+View+Lines+of+Code+Information+in+FishEye.

Any idea when theis feature will be available. Thx!

[jhinch (Atlassian) · Accepted solution]

Currently there are no active plans to implement LoC charts for Mercurial. There is a feature request raise at https://jira.atlassian.com/browse/FE-3236.

The main reason why this feature isn't supported for DVCSes (Git and Mercurial) is the complexity of tracking line of code back through all the anonymous branches. In tranditional VCSes, commits are linear and thus it is easier to track the origin of a line of code and attribute it to particularly authors. Commits are also chronological which means you can plot them against time. In DVCSes commits do not have to be chronological and they are definitely not linear (due to merges being part of the repositories history).

[mark Sisson]

Jason,

I'm interested in this same question. We have Hg and I'd really like to have LOC. I had a few questions on the difficulties that you proposed:

1. Why are commits not chronological? You know when a changeset was posted to a repository, even if things are happening on different branches by different posters.

2. Non-DVCSes have merges so why are DVCS merges more problematic to track ownership?

Can you provide an updated URL for the feature request? The one you provided above does not work.

Thanks, Mark

[Craig Oliver]

https://jira.atlassian.com/browse/FE-3236 works for me. The URL posted above has a decimal place on the end. Remove it and voilà...