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

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

                Author: ASF GitHub Bot
            Created on: 30/Jan/20 03:43
            Start Date: 30/Jan/20 03:43
    Worklog Time Spent: 10m 
      Work Description: suztomo commented on issue #10643: [BEAM-9162] Upgrade 
Jackson to version 2.10.2
URL: https://github.com/apache/beam/pull/10643#issuecomment-580070010
 
 
   I wouldn't rely on the result of the linkage check for an artifact list. 
`LinkageCheck(artifactA,artifactB)` is not the same as `LinkageCheck(artifactA) 
+ LinkageCheck(artifactB)`, where I define `LinkageCheck(artifact...)` as a 
function that takes list of Maven artifacts and returns list of linkage errors 
for a Java project that has dependencies of the artifacts. This is because 
linkage errors in one artifact may be hidden by classes in another artifact. 
For example, the missing `javax.annotation.Nullable` problem 
([BEAM-8917](https://issues.apache.org/jira/projects/BEAM/issues/BEAM-8917)) 
would be undetected if we run Linkage Check on the beam-sdks-java-core artifact 
and another artifact that happens to depend on jsr305 (which contains 
`javax.annotation.Nullable`).
   
   
   To ensure each Beam artifact is checked independently, I created a shell 
script that run "checkJavaLinkage" for each artifact:
   https://gist.github.com/suztomo/ec4834151a81f8e1d26aa0afb278818b
   What do you think about making this part of the Beam Jenkins jobs? 
([BEAM-9206](https://issues.apache.org/jira/projects/BEAM/issues/BEAM-9206))
   
   
   > an issue with beam-sdks-java-extensions-sql-zetasql
   
   For this issue, today I made a release of Linkage Checker 1.1.3 and I just 
raised a PR https://github.com/apache/beam/pull/10721 . 
   
   
 
----------------------------------------------------------------
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: 379138)
    Time Spent: 3h 10m  (was: 3h)

> Upgrade Jackson to version 2.10.2
> ---------------------------------
>
>                 Key: BEAM-9162
>                 URL: https://issues.apache.org/jira/browse/BEAM-9162
>             Project: Beam
>          Issue Type: Improvement
>          Components: build-system, sdk-java-core
>            Reporter: Ismaël Mejía
>            Assignee: Ismaël Mejía
>            Priority: Minor
>          Time Spent: 3h 10m
>  Remaining Estimate: 0h
>
> Jackson has a new way to deal with [deserialization security 
> issues|https://github.com/FasterXML/jackson/wiki/Jackson-Release-2.10] in 
> 2.10.x so worth the upgrade.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to