Skip to content

Conversation

@dependabot
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Dec 12, 2025

Bumps org.apache.axis2:axis2-transport-http from 1.7.0-SNAPSHOT to 1.8.0.

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
    You can disable automated security fix PRs for this repo from the Security Alerts page.

@dependabot dependabot bot added dependencies Pull requests that update a dependency file java Pull requests that update Java code labels Dec 12, 2025
@cortlepp
Copy link
Member

@robertlazarski regarding this PR (and also #1076) I have been wondering how we should treat our "samples": Some of them we build with maven, some we don't (like for example the ones mentioned in this or the other PR).

  1. Should we not build the samples? Doing so would in my mind ensure that the samples still work (at least on a basic level) and then we probably also wouldn't have had this specific versioning problem here, because I guess the version updates would then work like they do everywhere else. Is it intentional that we don't build all of the samples?
  2. If we don't want to build the samples, maybe it does make more sense to then refer to stable versions (of our own releases) instead of snapshots.

@robertlazarski
Copy link
Contributor

robertlazarski commented Dec 16, 2025

@dependabot rebase

@robertlazarski
Copy link
Contributor

robertlazarski commented Dec 16, 2025

@cortlepp I had no idea this sample even existed. Anyways, we should keep the samples updated so that they are not distributed with known security violations.

Yet this case shows that some of these samples probably have limited usefulness in 2025 and beyond. Best we can do is merge the PR and move on.

@robertlazarski
Copy link
Contributor

@cortlepp forgot to mention, I did a dependabot rebase to 2.0.0, obviously the PR from 1.7.0 to 1.8.0 was wrong anyways

Bumps org.apache.axis2:axis2-transport-http from 1.7.0-SNAPSHOT to 1.8.0.

---
updated-dependencies:
- dependency-name: org.apache.axis2:axis2-transport-http
  dependency-version: 1.8.0
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot force-pushed the dependabot/maven/modules/samples/dynamicclient/client/org.apache.axis2-axis2-transport-http-1.8.0 branch from 3a426e9 to 209d1d4 Compare December 16, 2025 17:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file java Pull requests that update Java code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants