[jira] [Commented] (MJAVADOC-333) Diacritics (accents) in project path prevent the plugin from working on Windows.

2016-10-13 Thread Anthony O. (JIRA)

[ 
https://issues.apache.org/jira/browse/MJAVADOC-333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15571609#comment-15571609
 ] 

Anthony O. commented on MJAVADOC-333:
-

As I said 
[before|https://issues.apache.org/jira/browse/MJAVADOC-333?focusedCommentId=15568988&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15568988],
 it happens only when Maven is launched from inside IntelliJ IDEA... so I think 
we could wait for [Jetbrains 
analyses|https://youtrack.jetbrains.com/issue/IDEA-162485#comment=27-1652112]?

> Diacritics (accents) in project path prevent the plugin from working on 
> Windows.
> 
>
> Key: MJAVADOC-333
> URL: https://issues.apache.org/jira/browse/MJAVADOC-333
> Project: Maven Javadoc Plugin
>  Issue Type: Bug
>Affects Versions: 2.7, 2.8
> Environment: Win7
>Reporter: Martin Pecka
> Attachments: FailingProject.zip, options, pom.xml
>
>
> 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 was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (MJAVADOC-333) Diacritics (accents) in project path prevent the plugin from working on Windows.

2016-10-12 Thread Michael Osipov (JIRA)

[ 
https://issues.apache.org/jira/browse/MJAVADOC-333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15569034#comment-15569034
 ] 

Michael Osipov commented on MJAVADOC-333:
-

It works without changes:

{noformat}
D:\Développement\MJAVADOC-333>mvn -V package
Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 
2015-11-10T17:41:47+01:00)
Maven home: D:\Entwicklung\Programme\apache-maven-3.3.9\bin\..
Java version: 1.8.0_92, vendor: Oracle Corporation
Java home: C:\Program Files\Java\jdk1.8.0_92\jre
Default locale: de_DE, platform encoding: Cp1252
OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
[INFO] Scanning for projects...
[INFO]
[INFO] 
[INFO] Building mjavadoc-333 0.1.0-SNAPSHOT
[INFO] 
[INFO]
[INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ 
mjavadoc-333 ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 
D:\Développement\MJAVADOC-333\src\main\resources
[INFO]
[INFO] --- maven-compiler-plugin:3.5.1:compile (default-compile) @ mjavadoc-333 
---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 1 source file to D:\Développement\MJAVADOC-333\target\classes
[INFO]
[INFO] --- maven-resources-plugin:2.6:testResources (default-testResources) @ 
mjavadoc-333 ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 
D:\Développement\MJAVADOC-333\src\test\resources
[INFO]
[INFO] --- maven-compiler-plugin:3.5.1:testCompile (default-testCompile) @ 
mjavadoc-333 ---
[INFO] No sources to compile
[INFO]
[INFO] --- maven-surefire-plugin:2.12.4:test (default-test) @ mjavadoc-333 ---
[INFO] No tests to run.
[INFO]
[INFO] --- maven-jar-plugin:2.4:jar (default-jar) @ mjavadoc-333 ---
[INFO] Building jar: 
D:\Développement\MJAVADOC-333\target\mjavadoc-333-0.1.0-SNAPSHOT.jar
[INFO]
[INFO] --- maven-javadoc-plugin:2.10.4:jar (attach-javadoc) @ mjavadoc-333 ---
[INFO]
Loading source files for package com.mycompany.mjavadoc_333...
Constructing Javadoc information...
Standard Doclet version 1.8.0_92
Building tree for all the packages and classes...
Generating 
D:\Développement\MJAVADOC-333\target\apidocs\com\mycompany\mjavadoc_333\MyClass.html...
Generating 
D:\Développement\MJAVADOC-333\target\apidocs\com\mycompany\mjavadoc_333\package-frame.html...
Generating 
D:\Développement\MJAVADOC-333\target\apidocs\com\mycompany\mjavadoc_333\package-summary.html...
Generating 
D:\Développement\MJAVADOC-333\target\apidocs\com\mycompany\mjavadoc_333\package-tree.html...
Generating D:\Développement\MJAVADOC-333\target\apidocs\constant-values.html...
Generating 
D:\Développement\MJAVADOC-333\target\apidocs\com\mycompany\mjavadoc_333\class-use\MyClass.html...
Generating 
D:\Développement\MJAVADOC-333\target\apidocs\com\mycompany\mjavadoc_333\package-use.html...
Building index for all the packages and classes...
Generating D:\Développement\MJAVADOC-333\target\apidocs\overview-tree.html...
Generating D:\Développement\MJAVADOC-333\target\apidocs\index-all.html...
Generating D:\Développement\MJAVADOC-333\target\apidocs\deprecated-list.html...
Building index for all classes...
Generating D:\Développement\MJAVADOC-333\target\apidocs\allclasses-frame.html...
Generating 
D:\Développement\MJAVADOC-333\target\apidocs\allclasses-noframe.html...
Generating D:\Développement\MJAVADOC-333\target\apidocs\index.html...
Generating D:\Développement\MJAVADOC-333\target\apidocs\help-doc.html...
[INFO] Building jar: 
D:\Développement\MJAVADOC-333\target\mjavadoc-333-0.1.0-SNAPSHOT-javadoc.jar
[INFO] 
[INFO] BUILD SUCCESS
[INFO] 
[INFO] Total time: 2.396 s
[INFO] Finished at: 2016-10-12T17:27:40+02:00
[INFO] Final Memory: 20M/214M
[INFO] 

D:\Développement\MJAVADOC-333>
{noformat}

> Diacritics (accents) in project path prevent the plugin from working on 
> Windows.
> 
>
> Key: MJAVADOC-333
> URL: https://issues.apache.org/jira/browse/MJAVADOC-333
> Project: Maven Javadoc Plugin
>  Issue Type: Bug
>Affects Versions: 2.7, 2.8
> Environment: Win7
>Reporter: Martin Pecka
> Attachments: FailingProject.zip, options, pom.xml
>
>
> 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: 

[jira] [Commented] (MJAVADOC-333) Diacritics (accents) in project path prevent the plugin from working on Windows.

2016-10-11 Thread Anthony O. (JIRA)

[ 
https://issues.apache.org/jira/browse/MJAVADOC-333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15565436#comment-15565436
 ] 

Anthony O. commented on MJAVADOC-333:
-

This issue still exists with current version of maven-javadoc-plugin (2.10.4)...

> Diacritics (accents) in project path prevent the plugin from working on 
> Windows.
> 
>
> Key: MJAVADOC-333
> URL: https://issues.apache.org/jira/browse/MJAVADOC-333
> Project: Maven Javadoc Plugin
>  Issue Type: Bug
>Affects Versions: 2.7, 2.8
> Environment: Win7
>Reporter: Martin Pecka
> Attachments: options, pom.xml
>
>
> 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 was sent by Atlassian JIRA
(v6.3.4#6332)