[
https://jira.codehaus.org/browse/MJAVADOC-333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benson Margulies updated MJAVADOC-333:
--------------------------------------
Description:
My project is located in "E:\ProgramovánÃ\Java\beam-3D-data-viewer". Notice
the diacritics in the path.
When launching the javadoc:javadoc goal, the build fails:
.
.
.
[ERROR] javadoc: warning - No source files for package org.esa.beam.util
[ERROR] javadoc: error - No public or protected classes found to document.
I looked on the generated "options" file, and that's the problem. Windows
apparentely don't have their filenames encoded in UTF8 when passing them to the
command line, but the options file is saved in UTF8. That's the reason why the
plugin cannot find the source files. When I manually edit the file and save it
in cp1250 encoding, running javadoc.bat works perfectly.
This should obviously be fixed, but is there a quick workaround? Eg. a way to
alter the generated javadoc.bat to prepend a call to iconv or something else.
Now I can use the generated files, manually edit the options file, and run the
task, but if I want to run the jar goal, this bug makes it impossible.
Thanks for cooperation!
was:
My project is located in "E:\Programování\Java\beam-3D-data-viewer". Notice the
diacritics in the path.
When launching the javadoc:javadoc goal, the build fails:
.
.
.
[ERROR] javadoc: warning - No source files for package org.esa.beam.util
[ERROR] javadoc: error - No public or protected classes found to document.
I looked on the generated "options" file, and that's the problem. Windows
apparentely don't have their filenames encoded in UTF8 when passing them to the
command line, but the options file is saved in UTF8. That's the reason why the
plugin cannot find the source files. When I manually edit the file and save it
in cp1250 encoding, running javadoc.bat works perfectly.
This should obviously be fixed, but is there a quick workaround? Eg. a way to
alter the generated javadoc.bat to prepend a call to iconv or something else.
Now I can use the generated files, manually edit the options file, and run the
task, but if I want to run the jar goal, this bug makes it impossible.
Thanks for cooperation!
Priority: Major (was: Critical)
> Diacritics (accents) in project path prevent the plugin from working on
> Windows.
> --------------------------------------------------------------------------------
>
> Key: MJAVADOC-333
> URL: https://jira.codehaus.org/browse/MJAVADOC-333
> Project: Maven 2.x Javadoc Plugin
> Issue Type: Bug
> Affects Versions: 2.7, 2.8
> Environment: Win7
> Reporter: Martin Pecka
>
> My project is located in "E:\ProgramovánÃ\Java\beam-3D-data-viewer". Notice
> the diacritics in the path.
> When launching the javadoc:javadoc goal, the build fails:
> .
> .
> .
> [ERROR] javadoc: warning - No source files for package org.esa.beam.util
> [ERROR] javadoc: error - No public or protected classes found to document.
> I looked on the generated "options" file, and that's the problem. Windows
> apparentely don't have their filenames encoded in UTF8 when passing them to
> the command line, but the options file is saved in UTF8. That's the reason
> why the plugin cannot find the source files. When I manually edit the file
> and save it in cp1250 encoding, running javadoc.bat works perfectly.
> This should obviously be fixed, but is there a quick workaround? Eg. a way to
> alter the generated javadoc.bat to prepend a call to iconv or something else.
> Now I can use the generated files, manually edit the options file, and run
> the task, but if I want to run the jar goal, this bug makes it impossible.
> Thanks for cooperation!
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
