Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Handle Internal annotation in TypeAnnotationMetadataStore

    • -3
    • +12
    ./impl/DefaultTypeAnnotationMetadataStore.java
  1. … 8 more files in changeset.
Handle Internal annotation in TypeAnnotationMetadataStore

    • -3
    • +12
    ./impl/DefaultTypeAnnotationMetadataStore.java
  1. … 8 more files in changeset.
Merge annotations from is- and get-getter

Previously we didn't do this, and we just accidentally got the right annotation for RunTestExecutable.ignoreFailures.

    • -2
    • +5
    ./impl/DefaultTypeAnnotationMetadataStore.java
  1. … 1 more file in changeset.
Merge annotations from is- and get-getter

Previously we didn't do this, and we just accidentally got the right annotation for RunTestExecutable.ignoreFailures.

    • -2
    • +5
    ./impl/DefaultTypeAnnotationMetadataStore.java
  1. … 1 more file in changeset.
Merge annotations from is- and get-getter

Previously we didn't do this, and we just accidentally got the right annotation for RunTestExecutable.ignoreFailures.

    • -2
    • +5
    ./impl/DefaultTypeAnnotationMetadataStore.java
  1. … 1 more file in changeset.
Merge annotations from is- and get-getter

Previously we didn't do this, and we just accidentally got the right annotation for RunTestExecutable.ignoreFailures.

    • -2
    • +5
    ./impl/DefaultTypeAnnotationMetadataStore.java
  1. … 1 more file in changeset.
Merge annotations from is- and get-getter

Previously we didn't do this, and we just accidentally got the right annotation for RunTestExecutable.ignoreFailures.

    • -2
    • +5
    ./impl/DefaultTypeAnnotationMetadataStore.java
  1. … 1 more file in changeset.
Merge annotations from is- and get-getter

Previously we didn't do this, and we just accidentally got the right annotation for RunTestExecutable.ignoreFailures.

    • -2
    • +5
    ./impl/DefaultTypeAnnotationMetadataStore.java
  1. … 1 more file in changeset.
Fix class cycle

    • -1
    • +1
    ./impl/DefaultPropertyAnnotationMetadata.java
    • -1
    • +1
    ./impl/DefaultTypeAnnotationMetadataStore.java
  1. … 5 more files in changeset.
Fix class cycle

    • -1
    • +1
    ./impl/DefaultPropertyAnnotationMetadata.java
    • -1
    • +1
    ./impl/DefaultTypeAnnotationMetadataStore.java
  1. … 5 more files in changeset.
Fix class cycle

    • -1
    • +1
    ./impl/DefaultPropertyAnnotationMetadata.java
    • -1
    • +1
    ./impl/DefaultTypeAnnotationMetadataStore.java
  1. … 5 more files in changeset.
Fix class cycle

    • -1
    • +1
    ./impl/DefaultPropertyAnnotationMetadata.java
    • -1
    • +1
    ./impl/DefaultTypeAnnotationMetadataStore.java
  1. … 5 more files in changeset.
Fix class cycle

    • -1
    • +1
    ./impl/DefaultPropertyAnnotationMetadata.java
    • -1
    • +1
    ./impl/DefaultTypeAnnotationMetadataStore.java
  1. … 5 more files in changeset.
Fix class cycle

    • -1
    • +1
    ./impl/DefaultPropertyAnnotationMetadata.java
    • -1
    • +1
    ./impl/DefaultTypeAnnotationMetadataStore.java
  1. … 5 more files in changeset.
Fix tests

    • -0
    • +5
    ./impl/DefaultTypeAnnotationMetadataStore.java
  1. … 1 more file in changeset.
Fix tests

    • -0
    • +5
    ./impl/DefaultTypeAnnotationMetadataStore.java
  1. … 1 more file in changeset.
Fix tests

    • -0
    • +5
    ./impl/DefaultTypeAnnotationMetadataStore.java
  1. … 1 more file in changeset.
Fix tests

    • -0
    • +5
    ./impl/DefaultTypeAnnotationMetadataStore.java
  1. … 1 more file in changeset.
Fix tests

    • -0
    • +5
    ./impl/DefaultTypeAnnotationMetadataStore.java
  1. … 1 more file in changeset.
Fix tests

    • -0
    • +5
    ./impl/DefaultTypeAnnotationMetadataStore.java
  1. … 1 more file in changeset.
Change order of supertype visiting to restore old behavior

In the past when a supertype and an implemented interface conflicted wrt the type of a property, we picked the interface. This change restores that behavior, and thus fixes a bunch of tests.

However, this is not a proper fix for the problem. We should instead have the following behavior:

- if supertype and subtype disagree in the annotation used for a property, subtype should always win

- if supertypes (superclass and implemented interfaces) disagree, we should decide which annotation wins by observing an ordering between them, e.g. @Internal having lower priority than other type annotations

- if supertypes disagree, and they all have the same priority/ordering, it should be reported as a conflict the same way we report multiple annotations on the same property in the same class

    • -3
    • +3
    ./impl/DefaultTypeAnnotationMetadataStore.java
Change order of supertype visiting to restore old behavior

In the past when a supertype and an implemented interface conflicted wrt the type of a property, we picked the interface. This change restores that behavior, and thus fixes a bunch of tests.

However, this is not a proper fix for the problem. We should instead have the following behavior:

- if supertype and subtype disagree in the annotation used for a property, subtype should always win

- if supertypes (superclass and implemented interfaces) disagree, we should decide which annotation wins by observing an ordering between them, e.g. @Internal having lower priority than other type annotations

- if supertypes disagree, and they all have the same priority/ordering, it should be reported as a conflict the same way we report multiple annotations on the same property in the same class

    • -3
    • +3
    ./impl/DefaultTypeAnnotationMetadataStore.java
Change order of supertype visiting to restore old behavior

In the past when a supertype and an implemented interface conflicted wrt the type of a property, we picked the interface. This change restores that behavior, and thus fixes a bunch of tests.

However, this is not a proper fix for the problem. We should instead have the following behavior:

- if supertype and subtype disagree in the annotation used for a property, subtype should always win

- if supertypes (superclass and implemented interfaces) disagree, we should decide which annotation wins by observing an ordering between them, e.g. @Internal having lower priority than other type annotations

- if supertypes disagree, and they all have the same priority/ordering, it should be reported as a conflict the same way we report multiple annotations on the same property in the same class

    • -3
    • +3
    ./impl/DefaultTypeAnnotationMetadataStore.java
Change order of supertype visiting to restore old behavior

In the past when a supertype and an implemented interface conflicted wrt the type of a property, we picked the interface. This change restores that behavior, and thus fixes a bunch of tests.

However, this is not a proper fix for the problem. We should instead have the following behavior:

- if supertype and subtype disagree in the annotation used for a property, subtype should always win

- if supertypes (superclass and implemented interfaces) disagree, we should decide which annotation wins by observing an ordering between them, e.g. @Internal having lower priority than other type annotations

- if supertypes disagree, and they all have the same priority/ordering, it should be reported as a conflict the same way we report multiple annotations on the same property in the same class

    • -3
    • +3
    ./impl/DefaultTypeAnnotationMetadataStore.java
Change order of supertype visiting to restore old behavior

In the past when a supertype and an implemented interface conflicted wrt the type of a property, we picked the interface. This change restores that behavior, and thus fixes a bunch of tests.

However, this is not a proper fix for the problem. We should instead have the following behavior:

- if supertype and subtype disagree in the annotation used for a property, subtype should always win

- if supertypes (superclass and implemented interfaces) disagree, we should decide which annotation wins by observing an ordering between them, e.g. @Internal having lower priority than other type annotations

- if supertypes disagree, and they all have the same priority/ordering, it should be reported as a conflict the same way we report multiple annotations on the same property in the same class

    • -3
    • +3
    ./impl/DefaultTypeAnnotationMetadataStore.java
Change order of supertype visiting to restore old behavior

In the past when a supertype and an implemented interface conflicted wrt the type of a property, we picked the interface. This change restores that behavior, and thus fixes a bunch of tests.

However, this is not a proper fix for the problem. We should instead have the following behavior:

- if supertype and subtype disagree in the annotation used for a property, subtype should always win

- if supertypes (superclass and implemented interfaces) disagree, we should decide which annotation wins by observing an ordering between them, e.g. @Internal having lower priority than other type annotations

- if supertypes disagree, and they all have the same priority/ordering, it should be reported as a conflict the same way we report multiple annotations on the same property in the same class

    • -3
    • +3
    ./impl/DefaultTypeAnnotationMetadataStore.java
Fix several tests

    • -1
    • +1
    ./impl/DefaultTypeAnnotationMetadataStore.java
  1. … 19 more files in changeset.
Fix several tests

    • -1
    • +1
    ./impl/DefaultTypeAnnotationMetadataStore.java
  1. … 19 more files in changeset.
Fix several tests

    • -1
    • +1
    ./impl/DefaultTypeAnnotationMetadataStore.java
  1. … 19 more files in changeset.
Fix several tests

    • -1
    • +1
    ./impl/DefaultTypeAnnotationMetadataStore.java
  1. … 19 more files in changeset.