slachiewicz closed pull request #8:
URL: https://github.com/apache/maven-archiver/pull/8
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to
Relates to Trunk-Based Development (I maintain
https://trunkbaseddevelopment.com) . Some of my clients do "branch for
release". Every cherry pick from trunk to the release branch (bug fix)
would wake up Jenkins. By default that'd do a full build and then artifacts
get pushed into artifactory/nexus
Am 2021-01-09 um 18:03 schrieb Paul Hammant:
I can't find where the HTTP-PUT logic is for deployment of Maven artifacts
to remote repos.
I was looking in 'maven-deploy-plugin' and 'maven-artifact-transfer' but
could not see the logic that pushes artifacts up to maven-central (or any
other
I seem to recall that it's already configurable, that someone else has been
here and done this.
On Mon, Jan 11, 2021 at 8:24 AM Dennis Lundberg
wrote:
> Hi all,
>
> When using a CI environments that create a new SemVer-compliant version for
> every build. These could use a qualifier like
Hi all,
When using a CI environments that create a new SemVer-compliant version for
every build. These could use a qualifier like "-build" together with the
build number. Here is an example:
1.2.3-build417
This signifies build number 417 of the not-yet-released version 1.2.3.
The current
elharo merged pull request #52:
URL: https://github.com/apache/maven-doxia/pull/52
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to
