You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@tapestry.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2021/04/08 18:20:00 UTC

[jira] [Commented] (TAP5-2673) Guava generics resolver not used when added in the classpath

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

ASF subversion and git services commented on TAP5-2673:
-------------------------------------------------------

Commit ae95b7d598a1eec133be8feea79f24ba0962d1aa in tapestry-5's branch refs/heads/master from Thiago H. de Paula Figueiredo
[ https://gitbox.apache.org/repos/asf?p=tapestry-5.git;h=ae95b7d ]

TAP5-2673: Guava generics resolver not used when added in the classpath


> Guava generics resolver not used when added in the classpath
> ------------------------------------------------------------
>
>                 Key: TAP5-2673
>                 URL: https://issues.apache.org/jira/browse/TAP5-2673
>             Project: Tapestry 5
>          Issue Type: Bug
>    Affects Versions: 5.7.0, 5.7.1
>            Reporter: Thiago Henrique De Paula Figueiredo
>            Priority: Major
>
> The default generics resolver ends up being used. This was caused by the change of package for the Guava generics resolver project, but the service loader file name wasn't updated.



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