ASM is not up-to-date
Maintainers usually reply within 1 day
A pull request for this has already been merged.
- #1768 by @dependabot — merged
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 88/100
- Issue type
- Refactor
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- java
- Domain
- build-system
Research direction
Start with commit a0640ffa3ea5806c4fbab0dfbd29e363646d0fa3 and the dependency-update report to find where org.ow2.asm:asm is declared. Update ASM from 9.11 to 9.11.1, then run the project’s dependency-check workflow to confirm that this change is resolved and the relevant checks pass.
Written by the indexing model from the issue text.
Description
Check dependencies found that org.ow2.asm:asm can be updated from version 9.11 to 9.11.1 at a0640ff.
dependency updates report
------------------------------------------------------------
: Project Dependency Updates (report to plain text file)
------------------------------------------------------------
The following dependencies are using the latest milestone version:
- com.diffplug.spotless:com.diffplug.spotless.gradle.plugin:8.10.4
- com.google.guava:guava:33.7.2-jre
- com.google.guava:guava-parent:33.7.2-jre
declared in the 'thirdpartyGuava' configuration
- com.gradleup.shadow:com.gradleup.shadow.gradle.plugin:9.6.1
- io.github.gradle-nexus.publish-plugin:io.github.gradle-nexus.publish-plugin.gradle.plugin:2.0.0
- jakarta.inject:jakarta.inject-api:2.0.1
- javax.annotation:javax.annotation-api:1.3.2
- junit:junit:4.13.2
- org.apache.geronimo.specs:geronimo-ejb_3.1_spec:1.0.2
- org.apache.geronimo.specs:geronimo-jpa_2.0_spec:1.1
- org.asciidoctor:asciidoctorj:2.5.11
- org.asciidoctor:asciidoctorj-diagram:2.2.14
- org.asciidoctor.jvm.convert:org.asciidoctor.jvm.convert.gradle.plugin:4.0.5
- org.javamodularity.moduleplugin:org.javamodularity.moduleplugin.gradle.plugin:2.1.0
- org.junit.jupiter:junit-jupiter:6.1.3
declared in :archunit-integration-test:junit6
- org.junit.platform:junit-platform-commons:6.1.3
declared in :archunit-junit6-api
- org.junit.platform:junit-platform-engine:6.1.3
declared in :archunit-junit6-engine-api
- org.junit.platform:junit-platform-launcher:6.1.3
declared in :archunit-example:example-junit6, :archunit-integration-test:junit6, :archunit-junit6-api, :archunit-junit6-engine, :archunit-junit6-engine-api
- org.junit.platform:junit-platform-runner:1.14.4
- org.junit.vintage:junit-vintage-engine:6.1.3
declared in :archunit-integration-test:junit6
The following dependencies have later milestone versions:
- com.github.spotbugs:com.github.spotbugs.gradle.plugin [6.5.12 -> 6.5.13]
- com.github.spotbugs:spotbugs [4.10.4 -> 4.10.5]
https://spotbugs.github.io/
contributed by a plugin into the 'spotbugs' configuration
- com.google.inject:guice [6.0.0 -> 7.0.0]
https://github.com/google/guice
- io.github.ben-manes.versions:io.github.ben-manes.versions.gradle.plugin [0.65.0 -> 0.66.0]
- jakarta.annotation:jakarta.annotation-api [2.1.1 -> 3.0.0]
https://projects.eclipse.org/projects/ee4j.ca
- joda-time:joda-time [2.14.2 -> 2.14.4 -> 2.15.0]
https://www.joda.org/joda-time/
- org.apache.logging.log4j:log4j-api [2.26.1 -> 3.0.0-beta2]
https://logging.apache.org/log4j/2.x/
- org.apache.logging.log4j:log4j-core [2.26.1 -> 3.0.0-beta3]
https://logging.apache.org/log4j/2.x/
- org.apache.logging.log4j:log4j-slf4j2-impl [2.26.1 -> 3.0.0-beta2]
https://logging.apache.org/log4j/2.x/
- org.assertj:assertj-core [3.27.7 -> 4.0.0-M1]
https://assertj.github.io/doc/#assertj-core
- org.assertj:assertj-guava [3.27.7 -> 4.0.0-M1]
https://assertj.github.io/doc/#assertj-guava
- org.junit.jupiter:junit-jupiter [5.14.4 -> 6.1.3]
https://junit.org/
declared in :archunit, :archunit-3rd-party-test, :archunit-example:example-junit4, :archunit-example:example-junit5, :archunit-example:example-junit6 and 10 others
- org.junit.platform:junit-platform-commons [1.14.4 -> 6.1.3]
https://junit.org/
declared in :archunit-junit5-api
- org.junit.platform:junit-platform-engine [1.14.4 -> 6.1.3]
https://junit.org/
declared in :archunit-junit5-engine-api
- org.junit.platform:junit-platform-launcher [1.14.4 -> 6.1.3]
https://junit.org/
declared in :archunit, :archunit-3rd-party-test, :archunit-example:example-junit4, :archunit-example:example-junit5, :archunit-example:example-junit6 and 10 others
- org.junit.vintage:junit-vintage-engine [5.14.4 -> 6.1.3]
https://junit.org/
declared in :archunit, :archunit-3rd-party-test, :archunit-example:example-junit4, :archunit-example:example-junit5, :archunit-example:example-junit6 and 9 others
- org.mockito:mockito-core [4.11.0 -> 5.24.0]
https://github.com/mockito/mockito
- org.mockito:mockito-junit-jupiter [4.11.0 -> 5.24.0]
https://github.com/mockito/mockito
- org.ow2.asm:asm [9.11 -> 9.11.1]
http://asm.ow2.io/
- org.slf4j:slf4j-api [2.0.20 -> 2.1.0-alpha1]
http://www.slf4j.org
- org.slf4j:slf4j-simple [2.0.17 -> 2.0.20 -> 2.1.0-alpha1]
http://www.slf4j.org
contributed by a plugin into the 'spotbugsSlf4j' configuration
- org.springframework:spring-beans [5.3.39 -> 7.0.9 -> 7.1.0-M2]
https://github.com/spring-projects/spring-framework
- org.springframework.boot:spring-boot-loader [2.7.18 -> 4.1.1 -> 4.2.0-M2]
https://spring.io/projects/spring-boot
Gradle release-candidate updates:
- Gradle: [9.8.1: UP-TO-DATE]
- Dominant language
- Java
- Stars
- 3.9k
- Forks
- 350
- Avg merge
- 1d 16h
- Merged PRs (30d)
- 18
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from TNG/ArchUnit
-
breaking change
Difficulty 5/5 Over a week Newbie friendliness 18/100
TNG/ArchUnit#1756 · 1 comment ·
Maintainers usually reply within 1 day
-
breaking change
Difficulty 4/5 3-5 days Newbie friendliness 30/100
Maintainers usually reply within 1 day
-
breaking change
Difficulty 4/5 3-5 days Newbie friendliness 22/100
Maintainers usually reply within 1 day
-
breaking change
Difficulty 3/5 Half a day Newbie friendliness 62/100
Maintainers usually reply within 1 day
-
breaking change
Difficulty 5/5 Over a week Newbie friendliness 12/100
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
-
DogFooding
Difficulty 1/5 Under an hour Newbie friendliness 88/100
OpenAEV-Platform/openaev#8768 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
federicoiosue/Omni-Notes#1039 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Dans-Plugins/Medieval-Roleplay-Engine#384 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day