-
Notifications
You must be signed in to change notification settings - Fork 135
Comparing changes
Open a pull request
base repository: apache/maven-resolver
base: maven-resolver-1.9.20
head repository: apache/maven-resolver
compare: maven-resolver-1.9.21
- 12 commits
- 19 files changed
- 3 contributors
Commits on Apr 26, 2024
-
Configuration menu - View commit details
-
Copy full SHA for 6e6bf7e - Browse repository at this point
Copy the full SHA 6e6bf7eView commit details
Commits on Jun 21, 2024
-
[Build] Unify bnd-maven-plugin and maven-jar-plugin invocations (#509)
Keep the 'bnd' configuration for the bnd-maven-plugin at plugin level to simplify overwrites in sub-modules (avoid the need to re-specify the execution there). Additionally update to bnd-maven-plugin 6.4.0 Co-authored-by: Hannes Wellmann <hannes.wellmann@iils.de>
Configuration menu - View commit details
-
Copy full SHA for 7466cae - Browse repository at this point
Copy the full SHA 7466caeView commit details
Commits on Jun 25, 2024
-
[Build] Define all MANIFEST.MF entries through the bnd-maven-plugin
and derive 'Bundle-SymbolicName' header from the artifactId. This changes the 'Bundle-SymbolicName' and 'Automatic-Module-Name' for the following modules: - maven-resolver-named-locks from 'org.apache.maven.resolver.named' to 'org.apache.maven.resolver.named.locks' - maven-resolver-test-util from 'org.apache.maven.resolver.testutil' to 'org.apache.maven.resolver.test.util'
Configuration menu - View commit details
-
Copy full SHA for 52b4db3 - Browse repository at this point
Copy the full SHA 52b4db3View commit details
Commits on Jun 27, 2024
-
[MRESOLVER-570] Remove excessive strictness of OSGi dependency metadata
- Mark optional Maven dependencies as optional in OSGi metadata - Widen version range for org.slf4j.spi package to [1.7,3)
Configuration menu - View commit details
-
Copy full SHA for e33cd94 - Browse repository at this point
Copy the full SHA e33cd94View commit details
Commits on Jul 1, 2024
-
[MRESOLVER-572] Export internal packages in OSGi metadata as x-internal
This makes maven-resolver-supplier usable as bundle in an OSGi runtime. At the moment the bundle cannot resolve because the internal.impl packages it uses and imports in its OSGi metadata are not exported by maven-resolver-impl. Simply exporting internal packages fixes that and, although it is discouraged to use internal/impl packages, gives consumers that can accept no API-compatibility guarantees the ability to access these packages. Adding the directive 'x-internal' is a convention that, at least when using Eclipse PDE, shows a corresponding warning at call-sides. Fixes https://issues.apache.org/jira/browse/MRESOLVER-572
Configuration menu - View commit details
-
Copy full SHA for 5b8f47a - Browse repository at this point
Copy the full SHA 5b8f47aView commit details -
[MRESOLVER-571] Import o.e.aether packages with the exact same version
The documentation states that only maven-resolver artifacts of the exact same version should be used together. With this change all org.eclipse.aether* packages are now imported with a strict version range of 'org.eclipse.aether*;version="[@Version,@Version]"' Fixes https://issues.apache.org/jira/browse/MRESOLVER-571
Configuration menu - View commit details
-
Copy full SHA for f14ed82 - Browse repository at this point
Copy the full SHA f14ed82View commit details -
[MRESOLVER-575] Bump org.redisson:redisson to 3.32.0
Bumps [org.redisson:redisson](https://github.com/redisson/redisson) to 3.32.0. - [Release notes](https://github.com/redisson/redisson/releases) - [Changelog](https://github.com/redisson/redisson/blob/master/CHANGELOG.md) - [Commits](redisson/redisson@redisson-parent-3.29.0...redisson-3.32.0) --- updated-dependencies: - dependency-name: org.redisson:redisson dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> --- https://issues.apache.org/jira/browse/MRESOLVER-575
Configuration menu - View commit details
-
Copy full SHA for 6288780 - Browse repository at this point
Copy the full SHA 6288780View commit details -
[MRESOLVER-574] Use standard cookie spec (#523)
As default one is not standard (w00t?) --- https://issues.apache.org/jira/browse/MRESOLVER-574
Configuration menu - View commit details
-
Copy full SHA for ca35d0c - Browse repository at this point
Copy the full SHA ca35d0cView commit details -
[MRESOLVER-576] Make Resolver 1.x site land in LATEST-1.x
To allow co-release of both resolvers. --- https://issues.apache.org/jira/browse/MRESOLVER-576
Configuration menu - View commit details
-
Copy full SHA for 99ddef8 - Browse repository at this point
Copy the full SHA 99ddef8View commit details -
[MRESOLVER-577] Update to Maven 3.9.8
Maven used by supplier and demos. --- https://issues.apache.org/jira/browse/MRESOLVER-577
Configuration menu - View commit details
-
Copy full SHA for c7639bc - Browse repository at this point
Copy the full SHA c7639bcView commit details -
[1.9.x] Tame bnd plugin warnings (#524)
To keep things simple, we config the plugin in one place, but in some modules this config emits warnings. This change just makes it go away. No other source or any alike change, no issue either.
Configuration menu - View commit details
-
Copy full SHA for 6655160 - Browse repository at this point
Copy the full SHA 6655160View commit details
Commits on Jul 2, 2024
-
Configuration menu - View commit details
-
Copy full SHA for f3adea9 - Browse repository at this point
Copy the full SHA f3adea9View commit details
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff maven-resolver-1.9.20...maven-resolver-1.9.21