MavenPublishWarProjectIntegTest.groovy

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Remove `@ToBeFixedForInstantExecution` from fixed publishing tests

    • -3
    • +0
    ./MavenPublishWarProjectIntegTest.groovy
  1. … 9 more files in changeset.
Upgrade JUnit version (#12924)

Upgrade JUnit to 4.13, JUnit platform to 5.6.2

    • -1
    • +1
    ./MavenPublishWarProjectIntegTest.groovy
  1. … 331 more files in changeset.
Rename @FailsWithInstantExecution to @ToBeFixedForInstantExecution

Signed-off-by: Paul Merlin <paul@gradle.com>

    • -3
    • +3
    ./MavenPublishWarProjectIntegTest.groovy
  1. … 872 more files in changeset.
Annotate integ tests failing with instant execution in :maven

Signed-off-by: Paul Merlin <paul@gradle.com>

    • -0
    • +3
    ./MavenPublishWarProjectIntegTest.groovy
  1. … 39 more files in changeset.
Let maven-publish tests not use deprecated configurations

    • -5
    • +5
    ./MavenPublishWarProjectIntegTest.groovy
  1. … 8 more files in changeset.
Migrate the Maven publish integration tests to use the same test fixtures as Ivy

This makes things much easier to understand, and explicits some expectations.

    • -4
    • +4
    ./MavenPublishWarProjectIntegTest.groovy
  1. … 12 more files in changeset.
Provide opt-in to publish _all_ software components with module metadata

    • -1
    • +2
    ./MavenPublishWarProjectIntegTest.groovy
  1. … 5 more files in changeset.
Publish war component to module metadata

- Don't publish a usage attribute, as there is only a single variant

    • -1
    • +2
    ./MavenPublishWarProjectIntegTest.groovy
  1. … 5 more files in changeset.
Enable Gradle metadata publishing for all maven-publish tests

- Several tests are still failing

- Most of these seem related to the fact that we don't respect the modified publication coordinates

- Some required verifications are missing

- Dependency excludes are not yet supported, so we do not verify these for module metadata

    • -3
    • +2
    ./MavenPublishWarProjectIntegTest.groovy
  1. … 19 more files in changeset.
On CI redirect maven central queries to local repo for integration tests

    • -3
    • +1
    ./MavenPublishWarProjectIntegTest.groovy
  1. … 108 more files in changeset.
Upgrade Apache Commons Collections to v3.2.2

Version 3.2.1 has a CVSS 10.0 vulnerability. That's the worst kind of

vulnerability that exists. By merely existing on the classpath, this

library causes the Java serialization parser for the entire JVM process

to go from being a state machine to a turing machine. A turing machine

with an exec() function!

https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2015-8103

https://commons.apache.org/proper/commons-collections/security-reports.html

http://foxglovesecurity.com/2015/11/06/what-do-weblogic-websphere-jboss-jenkins-opennms-and-your-application-have-in-common-this-vulnerability/

    • -1
    • +1
    ./MavenPublishWarProjectIntegTest.groovy
  1. … 54 more files in changeset.
moved all s3 related resources, fixtures, tests and integration tests into resourceS3 subproject

- required to add maven/ivy testfixtures (only compiling one class each atm)

+review REVIEW-5361

    • -0
    • +2
    ./MavenPublishWarProjectIntegTest.groovy
  1. … 69 more files in changeset.
Changed some more int tests to use junit 4.12

    • -1
    • +1
    ./MavenPublishWarProjectIntegTest.groovy
  1. … 7 more files in changeset.
Test the resolution of Maven projects published with the maven-publish plugin - Added resolve verification to many integ tests for Maven publishing

    • -3
    • +7
    ./MavenPublishWarProjectIntegTest.groovy
  1. … 8 more files in changeset.
Use instantiator to construct SoftwareComponentsContainer so it plays nicely in the DSL

    • -4
    • +4
    ./MavenPublishWarProjectIntegTest.groovy
  1. … 6 more files in changeset.
Added GroovyPublicationContainer that extends DefaultPublicationContainer and adds support for publication DSL - Need to review if this is the right way to implement this, and if this should be made into a more generic feature on NamedDomainObjectContainer

    • -4
    • +4
    ./MavenPublishWarProjectIntegTest.groovy
  1. … 37 more files in changeset.
Prevent adding multiple publications of same name to PublicationContainer - More tests for maven-publish sad-day scenarios

    • -2
    • +8
    ./MavenPublishWarProjectIntegTest.groovy
  1. … 6 more files in changeset.
WarPlugin now adds 'web' component, which can be published to maven repository.

    • -0
    • +134
    ./MavenPublishWarProjectIntegTest.groovy
  1. … 5 more files in changeset.