Forums : Feedback Forum
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
info@openhub.net
Projects which have alternatively named source files
I work on several projects using a lesser known platform called Vexi. These projects have their source mostly contained in .t files (which contain a mixture of Xml and Javascript) and from the reports on Ohloh it is obvious these .t files are not being considered.
Vexi itself has a lot of source in .jpp files (Java which is processed) which are also not considered by Ohloh.
Is there anyway to allow or even specify custom source file extensions?
Charles,
I had never really thought of enabling 'per-project' directives for code recognition - although we have thought or 'directory directives' (eg: /test is testing code, don't count stuff in /lib, etc...). More specifically, I suspect the feature would center on enlistments
rather than projects - to enable finer grain.
This falls in the reasonable, but not urgent
category of feature work for us. If more projects pipe in and clamor for this type of functionality it would push it up in priority. Otherwise I don't see it being done in the foreseeable future.
