Re: Trying to release maven-dependency-plugin

2020-03-04 Thread Karl Heinz Marbaise 

Hi Enrico,


On 04.03.20 20:40, Enrico Olivelli wrote:

Usually I put the gpg key system property in my settings.xml file.


Yeah that would work too ..



Do you have some odd profile enabled by your settings.xml file that
disables gpg plugin? Or the apache-release profile?


None of them...see the maven-dependency-plugin ...I've tried to release ..?

I bet I oversight something ? ...


Kind regards
Karl Heinz Marbaise



Enrico

Il Mer 4 Mar 2020, 18:41 Karl Heinz Marbaise mailto:khmarba...@gmx.de>> ha scritto:

Hi,

unfortunately I can't see that the artifacts are being signed
somehow ? :..

Can someone enlighten me? ..


Kind regards
Karl Heinz Marbaise
On 03.03.20 23:45, Hervé BOUTEMY wrote:
 > Hi,
 >
 > My last releases were done as usual with success.
 > The only difference I see with you is that I don't need the
"-Darguments=..."
 > part: perhaps there is an unexpected change at that level
 >
 > Regards,
 >
 > Hervé
 >
 > Le mardi 3 mars 2020, 19:50:28 CET Karl Heinz Marbaise a écrit :
 >> Hi,
 >>
 >> currently I'm trying to release a new version of
maven-dependency-plugin
 >> but unfortunately the release process has failed cause the artifacts
 >> have not been signed...
 >>
 >>
 >> I've used the following call:
 >>
 >> mvn -Darguments='-Dgpg.keyname=KEYNAME' release:prepare
release:perform
 >>
 >>
 >> I've realized that based on the update of our parents we are using
 >> maven-release-plugin 3.0.0-M1 which means we are using this
version...
 >>
 >> I don't see any call to maven-gpg-plugin to sign the artifacts
which of
 >> caused a fail in repository.apache.org
 ?
 >>
 >> Had there been a change which I haven't seen? Did we change the
release
 >> procedure? Maybe I missed just the information?
 >>
 >>
 >> Kind regards
 >> Karl Heinz Marbaise
 >>
 >>
 >>
 >>
 >>
 >>
 >>
 >>
-
 >> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org

 >> For additional commands, e-mail: dev-h...@maven.apache.org

 >
 >
 >
 >
 >
 > -
 > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org

 > For additional commands, e-mail: dev-h...@maven.apache.org

 >


Mit freundlichem Gruß
Karl-Heinz Marbaise
--
SoftwareEntwicklung Beratung Schulung    Tel.: +49 (0) 2405 / 415 893
Dipl.Ing.(FH) Karl-Heinz Marbaise        USt.IdNr: DE191347579
Hauptstrasse 177
52146 Würselen https://www.soebes.de

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org

For additional commands, e-mail: dev-h...@maven.apache.org





Mit freundlichem Gruß
Karl-Heinz Marbaise
--
SoftwareEntwicklung Beratung SchulungTel.: +49 (0) 2405 / 415 893
Dipl.Ing.(FH) Karl-Heinz MarbaiseUSt.IdNr: DE191347579
Hauptstrasse 177
52146 Würselen   https://www.soebes.de

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: Trying to release maven-dependency-plugin

2020-03-04 Thread Enrico Olivelli 
Usually I put the gpg key system property in my settings.xml file.

Do you have some odd profile enabled by your settings.xml file that
disables gpg plugin? Or the apache-release profile?

Enrico

Il Mer 4 Mar 2020, 18:41 Karl Heinz Marbaise  ha scritto:

> Hi,
>
> unfortunately I can't see that the artifacts are being signed somehow ? :..
>
> Can someone enlighten me? ..
>
>
> Kind regards
> Karl Heinz Marbaise
> On 03.03.20 23:45, Hervé BOUTEMY wrote:
> > Hi,
> >
> > My last releases were done as usual with success.
> > The only difference I see with you is that I don't need the
> "-Darguments=..."
> > part: perhaps there is an unexpected change at that level
> >
> > Regards,
> >
> > Hervé
> >
> > Le mardi 3 mars 2020, 19:50:28 CET Karl Heinz Marbaise a écrit :
> >> Hi,
> >>
> >> currently I'm trying to release a new version of maven-dependency-plugin
> >> but unfortunately the release process has failed cause the artifacts
> >> have not been signed...
> >>
> >>
> >> I've used the following call:
> >>
> >> mvn -Darguments='-Dgpg.keyname=KEYNAME' release:prepare release:perform
> >>
> >>
> >> I've realized that based on the update of our parents we are using
> >> maven-release-plugin 3.0.0-M1 which means we are using this version...
> >>
> >> I don't see any call to maven-gpg-plugin to sign the artifacts which of
> >> caused a fail in repository.apache.org ?
> >>
> >> Had there been a change which I haven't seen? Did we change the release
> >> procedure? Maybe I missed just the information?
> >>
> >>
> >> Kind regards
> >> Karl Heinz Marbaise
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >> -
> >> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> >> For additional commands, e-mail: dev-h...@maven.apache.org
> >
> >
> >
> >
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> > For additional commands, e-mail: dev-h...@maven.apache.org
> >
>
>
> Mit freundlichem Gruß
> Karl-Heinz Marbaise
> --
> SoftwareEntwicklung Beratung SchulungTel.: +49 (0) 2405 / 415 893
> Dipl.Ing.(FH) Karl-Heinz MarbaiseUSt.IdNr: DE191347579
> Hauptstrasse 177
> 52146 Würselen   https://www.soebes.de
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>

Re: Trying to release maven-dependency-plugin

2020-03-04 Thread Karl Heinz Marbaise 

Hi,

unfortunately I can't see that the artifacts are being signed somehow ? :..

Can someone enlighten me? ..


Kind regards
Karl Heinz Marbaise
On 03.03.20 23:45, Hervé BOUTEMY wrote:

Hi,

My last releases were done as usual with success.
The only difference I see with you is that I don't need the "-Darguments=..."
part: perhaps there is an unexpected change at that level

Regards,

Hervé

Le mardi 3 mars 2020, 19:50:28 CET Karl Heinz Marbaise a écrit :

Hi,

currently I'm trying to release a new version of maven-dependency-plugin
but unfortunately the release process has failed cause the artifacts
have not been signed...


I've used the following call:

mvn -Darguments='-Dgpg.keyname=KEYNAME' release:prepare release:perform


I've realized that based on the update of our parents we are using
maven-release-plugin 3.0.0-M1 which means we are using this version...

I don't see any call to maven-gpg-plugin to sign the artifacts which of
caused a fail in repository.apache.org ?

Had there been a change which I haven't seen? Did we change the release
procedure? Maybe I missed just the information?


Kind regards
Karl Heinz Marbaise







-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org






-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org




Mit freundlichem Gruß
Karl-Heinz Marbaise
--
SoftwareEntwicklung Beratung SchulungTel.: +49 (0) 2405 / 415 893
Dipl.Ing.(FH) Karl-Heinz MarbaiseUSt.IdNr: DE191347579
Hauptstrasse 177
52146 Würselen   https://www.soebes.de

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

This project has been banned from the build due to previous failures

2020-03-04 Thread Vladimir Sitnikov 
Hi,

Do you think $subj message can be more user-friendly?
Can it include the reasons for the failure and steps to resolve the issue
rather than merely "This project has been banned"?

The message is extremely confusing :((

In case you wonder, here's a sample build log:
https://download.copr.fedorainfracloud.org/results/@pgjdbc/pgjdbc-travis/fedora-rawhide-x86_64/01282986-postgresql-jdbc/builder-live.log.gz

The build is a Fedora Copr =that calls=> Python =that calls=> Maven, and
the wording of "This project has been banned" sounds to me more like
"Fedora banned the project" rather than "oh, you are just trying to execute
a non-existing goal".


PS. Frankly speaking, I have no idea which version of Maven is running,
however, as far as I see, master branch contains the same message:
https://github.com/apache/maven/blob/f2e9afd788de919646717532d26eca38826e9924/maven-embedder/src/main/java/org/apache/maven/cli/event/ExecutionEventLogger.java#L300

Vladimir