Dear Open Hub Users,
We’re excited to announce that we will be moving the Open Hub Forum to
https://community.synopsys.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]
Our project, like many others, suffers from a lot of misidentified code.
What about the ability to specify extension->type preferences for each project?
I created the following ohcount topics:
However creating (what some may construe as) project specific extensions to a generic tool is obviously not gonna fly - so hence this suggestion.
Hi Charles,
There's a general feature idea brewing to allow a file somewhat like robots.txt
to give directives to the Ohloh parser.
Initially, the most-requested feature is to ignore certain directories. However, I think we could generalize the feature to allow you to tell the Ohloh which languages are in use.
For instance, you might have a directive in the file that says to ignore everything in the 3rd_party
directory, and to treat all of the *.jpp
files as Java.
This is a pretty popular feature request, so it's on our radar, but I can't promise any timeline.
I look forward to future announcements relating to this issue.
Thanks! =)