l logging to --verbose/-X and
>redefine --debug for debugging instead of mvnDebug.
>So if you're only using -B there's no issue.
>And if you are using --debug -B you can switch to -X -B which will behave the
>same for Maven 3 and 4.
>
>Robert
>
>
>On 30-7-2021 22:59:09, Cl
Hello!
I may not understand much of this discussion going on here. But we use the -B
option for having the default behaviour of maven-release in literally thousands
of our Jenkins build jobs. Even only having to wait on a debug timeout would
not be acceptable and would force us to remove this
at 10:22 AM Clemens Quoss wrote:
OK. Found it myself:
https://maven.apache.org/plugins/maven-deploy-plugin/examples/deploying-with-classifiers.html
So classifier for sources, javadoc etc. Got it.
But still: What is the alogorithm to separate version from classifier
when I only have
, right? Or is
there a list of allowed classifiers?
TIA
Clemens
Am 07.01.2020 um 16:16 schrieb Clemens Quoss:
Consider this artifact:
artifactId-1.0-alpha1-classifier.jar
How to separate version (1.0-alpha1) from classifier (classifier), then?
TIA
Clemens
Am 07.01.2020 um 16:12 schrieb
. "alpha1" is not a classifier and neither is
"q".
On Tue, Jan 7, 2020 at 9:57 AM Clemens Quoss wrote:
Is 'q' considered a classifier or not? Classifier like 'alpha1',
'beta2' and even 'SNAPSHOT' denote a pre-production version, IMHO.
With: artifactId-1.0.alpha1 &l
Is 'q' considered a classifier or not? Classifier like 'alpha1',
'beta2' and even 'SNAPSHOT' denote a pre-production version, IMHO.
With: artifactId-1.0.alpha1 < artifactId-1.0.beta2 < ... <
artifactId-1.0.SNAPSHOT < ...
Is there really a difference between putting a hyphen or a dot to
the release next week-end: if anybody wants to update something, you
have one week
here is the current state of the reference documentation:
https://maven.apache.org/maven-release-archives/maven-release-LATEST/
Regards,
Hervé
Le dimanche 24 novembre 2019, 16:16:44 CET Clemens Quoss a écrit :
Hi,
how
Hi,
how about throwing in MRELEASE-229 as well?
Regards
Clemens
Am 24.11.2019 um 15:52 schrieb Hervé BOUTEMY:
Hi,
I fixed MRELEASE-1029 [1] for Reproducible Builds automatic update of
project.build.outputTimestamp property
I'd like to release maven-release-plugin.
But there are a few open
how we do it with our Jenkins script[1], only activate it for
Java 7.
Robert
[1]
https://github.com/apache/maven-jenkins-lib/blob/master/vars/asfMavenTlpPlgnBuild.groovy#L128-L131
On Wed, 24 Jul 2019 23:03:22 +0200, Clemens Quoss
wrote:
Hi Robert,
if TLSv1.2 is needed, then why not put
CDN
thanks,
Robert
On 23-7-2019 00:01:06, Clemens Quoss wrote:
Hi Robert,
thanks for the insight. Shouldn't it fail with JDK 7 Update 80 even
with this parameter since the backport for TLSv1.2 came with Update 95 [0]?
Since when does this requirement exist? Just checked it: I'm using UK
mirror
anymore to explicitly refer to uk, it
is already handled by Central CDN
thanks,
Robert
On 23-7-2019 00:01:06, Clemens Quoss wrote:
Hi Robert,
thanks for the insight. Shouldn't it fail with JDK 7 Update 80 even
with this parameter since the backport for TLSv1.2 came with Update 95 [0]?
Since
introducing
regression or not.
thanks,
Robert
On Sun, 14 Jul 2019 12:06:31 +0200, Clemens Quoss
wrote:
Hello everyone,
one more question regarding the name of the ITs in maven-release (or
maybe generally):
Seeing that the tests are named after the jira issues i am wondering
if that would
.
thanks,
Robert
On Sun, 14 Jul 2019 11:52:15 +0200, Clemens Quoss
wrote:
Hello everyone,
I have provided a PR for MRELEASE-229 [1] and added some JUnit tests
recently.
Now I was wondering if i should provide an IT, too, and had a look
into it:
Running
mvn verify -Prun-its
with Maven
such it which need some scm..
Maybe write a unit at least?
On Tue, 16 Jul 2019 at 05:20, Clemens Quoss wrote:
Hi Olivier,
yeah, could do that. Would be a great idea. But i am stuck on what to
put into this IT:
RemoveScmTag does what the name suggests: it uses maven-scm to remove
the tag during
etc.
See all "Apache Maven" projects https://gitbox.apache.org/repos/asf/ or
list of plugins https://maven.apache.org/plugins/
Cheers
Tibor
On Sun, Jul 14, 2019 at 9:46 PM Clemens Quoss wrote:
Hi Tibor,
with this system property set it works with JDK 7.
Why is it a pre-requisite?
the IT: MRELEASE-229-RemoveScmTagPhase?
On Sun, 14 Jul 2019 at 20:06, Clemens Quoss wrote:
Hello everyone,
one more question regarding the name of the ITs in maven-release (or
maybe generally):
Seeing that the tests are named after the jira issues i am wondering if
that would be the right thing to do
as in previous email?
Cheers
Tibor
On Sun, Jul 14, 2019 at 6:32 PM Clemens Quoss wrote:
Hi Tibor,
by looking further into it I noticed this:
MRELEASE-459/build.log (JDK 7):
...
[DEBUG] Additional arguments: -Dhttps.protocols=null -P custom-release
-DperformRelease=true -f pom.xml
...
MRELEASE
=b0d1d0d2d70172e03754e1666c78aa13d0d38b34;hb=HEAD#l65
Tibor
On Sun, Jul 14, 2019 at 11:52 AM Clemens Quoss wrote:
Hello everyone,
I have provided a PR for MRELEASE-229 [1] and added some JUnit tests
recently.
Now I was wondering if i should provide an IT, too, and had a look into it:
Running
mvn verify -Prun-its
with Maven
Hello everyone,
one more question regarding the name of the ITs in maven-release (or
maybe generally):
Seeing that the tests are named after the jira issues i am wondering if
that would be the right thing to do.
Shouldn't they be named after the functionality they are testing?
I for my
Hello everyone,
I have provided a PR for MRELEASE-229 [1] and added some JUnit tests
recently.
Now I was wondering if i should provide an IT, too, and had a look into it:
Running
mvn verify -Prun-its
with Maven 3.6.1 and JDK 7 Update 80 fails:
...
[INFO] Building:
Hello everyone,
after having taken some looks into maven-scm questions arise:
1. ScmManager API: Looks outdated - is it still good for something?
In maven-release, I found this:
21 matches
Mail list logo
