[ 
https://jira.codehaus.org/browse/MJAVADOC-333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Herve Boutemy updated MJAVADOC-333:
-----------------------------------

    Comment: was deleted

(was: ONLINE STORE :

http://Mlink.in/6H


n2012 comes, in order to thank everyone, characteristic, novel style, 
varieties, low price and good quality, and the low sale price. Thank everyone


free shipping

competitive price

any size available

accept the paypal

jordan shoes $32

nike shox $32

Christan Audigier bikini $23

Ed Hardy Bikini $23

Smful short_t-shirt_woman $15

ed hardy short_tank_woman $16

Sandal $32

christian louboutin $80

Sunglass $15

COACH_Necklace $27

handbag $33

AF tank woman $17


puma slipper woman $30

http://Mlink.in/6H
)
    
> 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


Reply via email to