DependencyVerificationsXmlWriterTest.groovy

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Fix use of schema location

The code was using `xmlns` instead of `xsi`

    • -1
    • +1
    ./DependencyVerificationsXmlWriterTest.groovy
  1. … 5 more files in changeset.
Fix use of schema location

The code was using `xmlns` instead of `xsi`

    • -1
    • +1
    ./DependencyVerificationsXmlWriterTest.groovy
  1. … 5 more files in changeset.
Make dependency verification XSD more explicit

By using `dependency-verification` in the URL and file

name.

    • -1
    • +1
    ./DependencyVerificationsXmlWriterTest.groovy
  1. … 4 more files in changeset.
Make dependency verification XSD more explicit

By using `dependency-verification` in the URL and file

name.

    • -1
    • +1
    ./DependencyVerificationsXmlWriterTest.groovy
  1. … 4 more files in changeset.
Make dependency verification XSD more explicit

By using `dependency-verification` in the URL and file

name.

    • -1
    • +1
    ./DependencyVerificationsXmlWriterTest.groovy
  1. … 4 more files in changeset.
Add an XML schema for the verification file

    • -1
    • +10
    ./DependencyVerificationsXmlWriterTest.groovy
  1. … 4 more files in changeset.
Add an XML schema for the verification file

    • -1
    • +10
    ./DependencyVerificationsXmlWriterTest.groovy
  1. … 4 more files in changeset.
Add an XML schema for the verification file

    • -1
    • +10
    ./DependencyVerificationsXmlWriterTest.groovy
  1. … 4 more files in changeset.
Regroup trusted keys for readability

If a single key is trusted multiple times for different artifacts, we

now regroup the artifact coordinates under the `trusted-key` tag.

    • -2
    • +6
    ./DependencyVerificationsXmlWriterTest.groovy
  1. … 4 more files in changeset.
Regroup trusted keys for readability

If a single key is trusted multiple times for different artifacts, we

now regroup the artifact coordinates under the `trusted-key` tag.

    • -2
    • +6
    ./DependencyVerificationsXmlWriterTest.groovy
  1. … 4 more files in changeset.
Regroup trusted keys for readability

If a single key is trusted multiple times for different artifacts, we

now regroup the artifact coordinates under the `trusted-key` tag.

    • -2
    • +6
    ./DependencyVerificationsXmlWriterTest.groovy
  1. … 4 more files in changeset.
Add ability to ignore keys for a specific artifact

The use case for this is whenever signature for an artifact fails, but

for some reason the user still trusts the artifact. For example, a POM

file is different between different repositories because it happened

to be published twice with different timestamps.

In this case it is recommended to ignore the signature, however we

_will_ fallback on checksum verification.

    • -5
    • +52
    ./DependencyVerificationsXmlWriterTest.groovy
  1. … 13 more files in changeset.
Add ability to ignore keys for a specific artifact

The use case for this is whenever signature for an artifact fails, but

for some reason the user still trusts the artifact. For example, a POM

file is different between different repositories because it happened

to be published twice with different timestamps.

In this case it is recommended to ignore the signature, however we

_will_ fallback on checksum verification.

    • -5
    • +52
    ./DependencyVerificationsXmlWriterTest.groovy
  1. … 13 more files in changeset.
Add ability to ignore keys for a specific artifact

The use case for this is whenever signature for an artifact fails, but

for some reason the user still trusts the artifact. For example, a POM

file is different between different repositories because it happened

to be published twice with different timestamps.

In this case it is recommended to ignore the signature, however we

_will_ fallback on checksum verification.

    • -5
    • +52
    ./DependencyVerificationsXmlWriterTest.groovy
  1. … 13 more files in changeset.
Add ability to ignore keys for a specific artifact

The use case for this is whenever signature for an artifact fails, but

for some reason the user still trusts the artifact. For example, a POM

file is different between different repositories because it happened

to be published twice with different timestamps.

In this case it is recommended to ignore the signature, however we

_will_ fallback on checksum verification.

    • -5
    • +52
    ./DependencyVerificationsXmlWriterTest.groovy
  1. … 13 more files in changeset.
Add ability to ignore keys for a specific artifact

The use case for this is whenever signature for an artifact fails, but

for some reason the user still trusts the artifact. For example, a POM

file is different between different repositories because it happened

to be published twice with different timestamps.

In this case it is recommended to ignore the signature, however we

_will_ fallback on checksum verification.

    • -5
    • +52
    ./DependencyVerificationsXmlWriterTest.groovy
  1. … 13 more files in changeset.
Add ability to ignore keys for a specific artifact

The use case for this is whenever signature for an artifact fails, but

for some reason the user still trusts the artifact. For example, a POM

file is different between different repositories because it happened

to be published twice with different timestamps.

In this case it is recommended to ignore the signature, however we

_will_ fallback on checksum verification.

    • -5
    • +52
    ./DependencyVerificationsXmlWriterTest.groovy
  1. … 13 more files in changeset.
Sort entries when building the verification map

This is from user feedback: it seems to be easier to read/update the

contents of the verification file if entries are sorted. If it's done

correctly, then a new version of a module would be written close to

the existing one, making it easier to do manual cleanup of the file.

    • -21
    • +15
    ./DependencyVerificationsXmlWriterTest.groovy
  1. … 2 more files in changeset.
Sort entries when building the verification map

This is from user feedback: it seems to be easier to read/update the

contents of the verification file if entries are sorted. If it's done

correctly, then a new version of a module would be written close to

the existing one, making it easier to do manual cleanup of the file.

    • -21
    • +15
    ./DependencyVerificationsXmlWriterTest.groovy
  1. … 3 more files in changeset.
Sort entries when building the verification map

This is from user feedback: it seems to be easier to read/update the

contents of the verification file if entries are sorted. If it's done

correctly, then a new version of a module would be written close to

the existing one, making it easier to do manual cleanup of the file.

    • -21
    • +15
    ./DependencyVerificationsXmlWriterTest.groovy
  1. … 3 more files in changeset.
Sort entries when building the verification map

This is from user feedback: it seems to be easier to read/update the

contents of the verification file if entries are sorted. If it's done

correctly, then a new version of a module would be written close to

the existing one, making it easier to do manual cleanup of the file.

    • -21
    • +15
    ./DependencyVerificationsXmlWriterTest.groovy
  1. … 3 more files in changeset.
Sort entries when building the verification map

This is from user feedback: it seems to be easier to read/update the

contents of the verification file if entries are sorted. If it's done

correctly, then a new version of a module would be written close to

the existing one, making it easier to do manual cleanup of the file.

    • -21
    • +15
    ./DependencyVerificationsXmlWriterTest.groovy
  1. … 2 more files in changeset.
Sort entries when building the verification map

This is from user feedback: it seems to be easier to read/update the

contents of the verification file if entries are sorted. If it's done

correctly, then a new version of a module would be written close to

the existing one, making it easier to do manual cleanup of the file.

    • -21
    • +15
    ./DependencyVerificationsXmlWriterTest.groovy
  1. … 3 more files in changeset.
Sort entries when building the verification map

This is from user feedback: it seems to be easier to read/update the

contents of the verification file if entries are sorted. If it's done

correctly, then a new version of a module would be written close to

the existing one, making it easier to do manual cleanup of the file.

    • -21
    • +15
    ./DependencyVerificationsXmlWriterTest.groovy
  1. … 3 more files in changeset.
Sort entries when building the verification map

This is from user feedback: it seems to be easier to read/update the

contents of the verification file if entries are sorted. If it's done

correctly, then a new version of a module would be written close to

the existing one, making it easier to do manual cleanup of the file.

    • -21
    • +15
    ./DependencyVerificationsXmlWriterTest.groovy
  1. … 3 more files in changeset.
Add support for globally trusted keys

A globally trusted key can be used to trust a number of

modules and greatly simplifies configuration: instead of

having to specify checksums for all modules, a user can

declare the keys they trust and use a similar syntax to

trusted artifacts to say to what group/name/version the

key applies.

It's often the case that the same keys are used for

several artifacts of the same group or same company, so

this makes it possible to avoid a lot of boilerplate as

long as the artifacts are signed by the same keys.

    • -0
    • +25
    ./DependencyVerificationsXmlWriterTest.groovy
  1. … 9 more files in changeset.
Add support for globally trusted keys

A globally trusted key can be used to trust a number of

modules and greatly simplifies configuration: instead of

having to specify checksums for all modules, a user can

declare the keys they trust and use a similar syntax to

trusted artifacts to say to what group/name/version the

key applies.

It's often the case that the same keys are used for

several artifacts of the same group or same company, so

this makes it possible to avoid a lot of boilerplate as

long as the artifacts are signed by the same keys.

    • -0
    • +25
    ./DependencyVerificationsXmlWriterTest.groovy
  1. … 9 more files in changeset.
Add support for globally trusted keys

A globally trusted key can be used to trust a number of

modules and greatly simplifies configuration: instead of

having to specify checksums for all modules, a user can

declare the keys they trust and use a similar syntax to

trusted artifacts to say to what group/name/version the

key applies.

It's often the case that the same keys are used for

several artifacts of the same group or same company, so

this makes it possible to avoid a lot of boilerplate as

long as the artifacts are signed by the same keys.

    • -0
    • +25
    ./DependencyVerificationsXmlWriterTest.groovy
  1. … 9 more files in changeset.
Add support for globally trusted keys

A globally trusted key can be used to trust a number of

modules and greatly simplifies configuration: instead of

having to specify checksums for all modules, a user can

declare the keys they trust and use a similar syntax to

trusted artifacts to say to what group/name/version the

key applies.

It's often the case that the same keys are used for

several artifacts of the same group or same company, so

this makes it possible to avoid a lot of boilerplate as

long as the artifacts are signed by the same keys.

    • -0
    • +25
    ./DependencyVerificationsXmlWriterTest.groovy
  1. … 9 more files in changeset.
Add support for globally trusted keys

A globally trusted key can be used to trust a number of

modules and greatly simplifies configuration: instead of

having to specify checksums for all modules, a user can

declare the keys they trust and use a similar syntax to

trusted artifacts to say to what group/name/version the

key applies.

It's often the case that the same keys are used for

several artifacts of the same group or same company, so

this makes it possible to avoid a lot of boilerplate as

long as the artifacts are signed by the same keys.

    • -0
    • +25
    ./DependencyVerificationsXmlWriterTest.groovy
  1. … 9 more files in changeset.