I look forward to future announcements relating to this issue. Thanks! =)

Our project, like many others, suffers from a lot of misidentified code. What about the ability to specify extension->type preferences for each project? http://www.ohloh.net/p/vexi .jpp not ... [More] identified as Java .t identified as xsl (custom type, although it is just xml/js) I created the following ohcount topics: https://www.ohloh.net/forums/3493/topics/3782 https://www.ohloh.net/forums/3493/topics/3759 However creating (what some may construe as) project specific extensions to a generic tool is obviously not gonna fly - so hence this suggestion. [Less]

We use preprocessed Java - that is, Java that contains macros to be processed. Currently ohcount (like sloccount) ignores these .jpp files. The .jpp files contain our most significant code. ... [More] http://www.ohloh.net/p/vexi This would fix the erroneous "C++ project" conclusion, and given our documentation in Java files being ~24%, the "poorly documented" warning should go away too. [Less]

There are numerous projects now using Vexi. Vexi files are XML/JS. Currently ohcount detects them as Perl files. It is easy to know if it is a Vexi file: All Vexi templates end in .t All are JS ... [More] encapsulated in XML Root tag is always <vexi></vexi> The only vexi-ism that would be worth noting is that not all textual content is JS. Anything inside the tag <meta:doc></meta:doc> should be considered comments - including further XML tags. [Less]

You're welcome. I love Ohloh and the reason I reported this was to try and help you improve it. :-)

Robin, ohloh has since done an update from our svn (as recently as 5 days ago) but still doesn't list the Apache License: http://www.ohloh.net/projects/3923/analyses/latest I fixed most of the ... [More] references to say Apache Software License (although a few still remain as Apache Public Source License). Any idea what's wrong there? [Less]

Thanks for the response :- Issue 1. .jpp is pretty much regular java with macros (//#repeat foo/bar ..., //#define MACRO(args) ...) for a few things Java doesn't cater for. Unless you are compiling ... [More] , it shouldn't matter so much. Issue 3. Ah, ok, I'll fix this. Thanks for pointing it out! Another possible issue: No support for arbitrary files We have our own "filetype", if you will - All *.t files are templates with XML/JavaScript content. Are these picked up by Ohloh? There are a few other projects using this too (Vexi is a UI programming platform) listed on Ohloh. Any tips on how to find all files of a particular type whilst excluding .svn directories? The 'find' command just isn't that intuitive. [Less]

I've listed these in a few other threads but I just wanted to put them all in one for reference: Project: http://www.ohloh.net/projects/3923 Mostly written in C/C++ It is a Java project. There ... [More] are a handful of C++ files compared about 200 Java classes. Approximately half of the Java is in a "preprocessed" form - the extension is .jpp rather than .java - which probably causes this incorrect identification. AFAIK there is no way for Projects to specify arbitrary file associations. Short source control history Ohloh shows the project as starting in August 2007. Our SVN history goes back to April 2006. We reorganised SVN (did I bunch of moves but retained file history) in August 2007. AFAIK Ohloh can not follow this kind of operation yet but it's on the 'to fix' list. Not identifying Apache License A lot of the code is licensed under the Apache license, with the following header: // Copyright 2000-2005 the Contributors, as shown in the revision logs. // Licensed under the Apache Public Source License 2.0 ("the License"). // You may not use this file except in compliance with the License. Ohloh is not picking up this license at all. [Less]

Ok, I tried using file on one of our .t files (XML/JS, but obviously not included in your file extension list) and get the following: org.vexi.widgets/src/vexi/widget$ file button.t button.t: ... [More] exported SGML document text That would imply XML but we have very few XML listings on our project: http://www.ohloh.net/projects/3923/analyses/latest Interestingly we have very little C/C++ (a few files, if that). [Less]

Perhaps ohloh should have a launchpad account or something similar so that we can report bugs and search them conveniently. This forum is not a great system for tracking problems. e.g. I have ... [More] reported a few things in the feedback area and had no official reponse for several days. [Less]