jclouds-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ignasi Barrera (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (JCLOUDS-1030) Ignore synthetic members in serialization strategies
Date Wed, 28 Oct 2015 13:42:28 GMT

     [ https://issues.apache.org/jira/browse/JCLOUDS-1030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Ignasi Barrera reassigned JCLOUDS-1030:

    Assignee: Ignasi Barrera

> Ignore synthetic members in serialization strategies
> ----------------------------------------------------
>                 Key: JCLOUDS-1030
>                 URL: https://issues.apache.org/jira/browse/JCLOUDS-1030
>             Project: jclouds
>          Issue Type: Bug
>          Components: jclouds-core
>    Affects Versions: 1.9.1
>            Reporter: Ignasi Barrera
>            Assignee: Ignasi Barrera
> jclouds relies on the consistency between the number of fields in a class, their order,
and the parameters in the constructors and factory methods. This  is specially relevant when
using reflection with classes auto-generated by Google Auto.
> Libraries that instrument the classes may introduce conflicts with this assumptions.
For example, JaCoCo adds two members to the classes: A private static field $jacocoData and
a private static method $jacocoInit(). Both members are marked as synthetic.
> The jclouds serialization strategies that use reflection, should ignore all synthetic
members, as they won't be part of the source code and never expected to be used to map the
fields with the serialized values.

This message was sent by Atlassian JIRA

View raw message