[ 
https://issues.apache.org/jira/browse/BEAM-6981?focusedWorklogId=222218&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-222218
 ]

ASF GitHub Bot logged work on BEAM-6981:
----------------------------------------

                Author: ASF GitHub Bot
            Created on: 03/Apr/19 09:05
            Start Date: 03/Apr/19 09:05
    Worklog Time Spent: 10m 
      Work Description: adude3141 commented on issue #8207: [BEAM-6981] use 
beam module global configuration for javadoc creation
URL: https://github.com/apache/beam/pull/8207#issuecomment-479404673
 
 
   @udim
   As your comments on PR https://github.com/apache/beam/pull/8200 made me look 
into that again I realised above problem. Of course we might add an additional 
reviewer if you think it is more appropriate.
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[email protected]


Issue Time Tracking
-------------------

    Worklog Id:     (was: 222218)
    Time Spent: 20m  (was: 10m)

> :beam-sdks-java-javadoc:aggregateJavadoc has no encoding set
> ------------------------------------------------------------
>
>                 Key: BEAM-6981
>                 URL: https://issues.apache.org/jira/browse/BEAM-6981
>             Project: Beam
>          Issue Type: Bug
>          Components: build-system
>            Reporter: Michael Luckey
>            Assignee: Michael Luckey
>            Priority: Major
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> Beams javadoc project does not apply beam module plugin.
> As rhe aggregateJavadoc tasks configuration does not set
> {noformat}
> options.encoding = 'UTF-8'
> {noformat}
> and the option is also not inherited from beam modules applyJavaNature 
> current javadoc creation relies on systems default file encoding (or whatever 
> happens to be active for the jvm)
> So we either need to set it explicitly, or apply our plugin. The latter is 
> probably better, as it ensures all configuration globally set for java 
> projects will be used.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to