Releases: deepmedia/MavenDeployer
Releases · deepmedia/MavenDeployer
v0.17.0
v0.16.0
v0.15.0
v0.14.0
v0.13.0
With the addition of a new Sonatype-related spec, sonatypeSpec
is now deprecated:
- use
nexusSpec
if you use Nexus repositories and/or you have a OSSRH project that syncs to Maven Central - use
centralPortalSpec
if you are using Sonatype's new entry point for Maven Central, as described here
What's Changed
Full Changelog: v0.12.0...v0.13.0
v0.12.0
- f7fb8f3 Maven Central Sync implementation using Sonatype APIs. Enable with
syncToMavenCentral = true
- 96f261e Prettier repository names
- ad5377b Relax publication requirements for non Maven Central releases
- 4147027 Finalize Property values on read
- 0c35464 Allow sonatype publications without signing (snapshots, private Nexus repos)
- 96331c3 Add Nexus typealiases, e.g.
nexusSpec {}
is the same ofsonatypeSpec {}
Full Changelog: v0.11.0...v0.12.0
v0.11.0
This release contains breaking changes:
- Removed content inference (
Content.infer
,Component.inferred
...). You now need to give deployer some hints about the contents of the current project.
content {
kotlinComponents() // for kotlin-based projects (single platform and multiplatform)
gradlePluginComponents() // for gradle plugin projects
}
- Removed:
Content.autoDocs()
andContent.autoSources()
. Source/docs management moved to the component level. - Added:
Component.emptyDocs()
,Component.emptySources()
,Component.kotlinSources()
,Component.javaSources()
- Added:
Content.inherit = <true|false>
. Whether this spec should inherit content from the root spec. - Added:
Component.fromJava()
, shortcut toComponent.fromSoftwareComponent("java")
- Fixed many issues with duplicated jars in some scenarios
deployer { }
extension now extendsDeploySpec
: no need to usedefaultSpec { ... }
block anymore - replace withthis
.
Full Changelog: v0.10.0...v0.11.0
v0.10.0
What's Changed
- Add hosted docs by @natario1 in #17
- Updates dependencies by @natario1 in #18
- Fix component inference by @natario1 in #18
- Move packaging string (e.g. "jar", "aar") from
Release
toComponent
block by @natario1 in #18 - Ability to create a component out of a
SoftwareComponent
by @natario1 in #18
Full Changelog: v0.9.1...v0.10.0
v0.9.1
v0.9.0
We keep building on the refactoring done on #14 and add some missing features. In v0.9.0:
- New:
autoSources()
,autoDocs()
,emptySources()
andemptyDocs()
utilities for automatically adding JAR files - New:
component.extras
lets you add extra artifacts to the publication - New: option to conditionally disable single components using the
component.enabled
property - Fix: GitHub POM files not respecting
defaultSpec
fallbacks - Fix: release description not used in the final POM file
PRs
Full Changelog: v0.8.0...v0.9.0