GNOME Bugzilla – Bug 567774
EXTENSION_MAPPING for Java not working
Last modified: 2010-10-09 08:19:56 UTC
I am trying to map .ejb files to Java and cannot get this to work. Here is a simple Doxyfile which shows the problem OUTPUT_DIRECTORY = doxygen_doc GENERATE_LATEX = NO INPUT = src RECURSIVE = YES EXTENSION_MAPPING = ejb=Java FILE_PATTERNS = *.java *.ejb OPTIMIZE_OUTPUT_JAVA = YES EXTRACT_ALL = YES Any *.ejb files seem to still be treated as C++ . I noticed that the extension mapping does seem to work for other languages, for example if I put EXTENSION_MAPPING = ejb=Fortran then the output changes. I have also tried "java" and "JAVA" as I was unclear what should be specified from the documentation. Thanks, Allan
Created attachment 126439 [details] sample project illustrating the problem Test project used to validate the problem. TestA.java and TestB.java are identical except for the class name.
Created attachment 126440 [details] sample project illustrating the problem Test project used to validate the problem. TestA.java and TestB.java are identical except for the class name.
Looking into it a bit more, there seems to be something a bit odd going on here. After having a look at doxygen.cpp and util.cpp, I tried putting EXTENSION_MAPPING = .ejb=Java and it seems to work ok. This is a bit surprising as if I put Fortran rather than Java, it seems fine with or without the '.' . It might be worth updating the docs at http://www.stack.nl/~dimitri/doxygen/config.html#cfg_extension_mapping and the generated Doxyfile to include a '.' in the examples.
We are experiencing the same problem. Some of our C++ header files have the extension ".inc", which is assigned for PHP files by default. The configuration EXTENSION_MAPPING = inc=C++ doesn't work, despite the fact that doxygen reports that inc files will be parsed as C++. I have changed the config to EXTENSION_MAPPING = .inc=C++ and now it works correctly. P.S. We are using the version 1.5.8 on Windows platform. I can run the tests on other platforms (Linux, Solaris) if it helps...
Confirmed, the dot should not be needed. Should be fixed in the next subversion update.
*** Bug 626033 has been marked as a duplicate of this bug. ***
*** Bug 629197 has been marked as a duplicate of this bug. ***
This bug was previously marked ASSIGNED, which means it should be fixed in doxygen version 1.7.2. Please verify if this is indeed the case. Reopen the bug if you think it is not fixed and please include any additional information that you think can be relevant.