Le 30/04/2018 à 23:29, Emmanuel Lécharny a écrit :
> 
> 
> Le 30/04/2018 à 23:05, Allen Wittenauer a écrit :
>>
>>> On Apr 30, 2018, at 9:02 AM, Emmanuel Lécharny <[email protected]> wrote:
>>>
>>> Missing Signature:
>>> '/org/apache/directory/api/api-asn1-api/1.0.1/api-asn1-api-1.0.1.jar.asc'
>>> does not exist for 'api-asn1-api-1.0.1.jar'.
>>> ...
>>>
>>>
>>> The .md5 and .sha1 signatures are present though.
>>
>>      asc files are PGP signature files.
>>
>>> What could have gone wrong ?
>>
>>      Are the directions missing -Papache-release or gpg:sign?
> 
> I never had to specifically gives such direction : they are implicit.
> 
> The LDAP API project inherits from apache 18 which is used when
> releasing a project, using the apache-release profile.
> 
> gpg:sign is also supposed to be invoked automatically when doing a
> release:perform, it's configured as so in the apache parent pom.
> 
> 
> Now, are you suggesting I run mvn deploy -Papache-release ?

Seems like it's needed when running mvn deploy, otherwise the .asc files
never get created...

Still, that does not explain why the standard mvn release:perform never
pushed the packages into nexus (the previous release, 1.0.0, worked like
a charm following the exact same procedure, and the changes from 1.0.0
to 1.0.1 are really minimalistic, plus the various poms haven't been
changed except the scm tag which has been changed from svn to git.

Quite a mystery...

As a matter of fact, while running a mvn deploy -Papache-release, I just
got this warning :

...
Downloading:
https://repository.apache.org/service/local/staging/deploy/maven2/org/apache/directory/api/api-all/maven-metadata.xml
[WARNING] Could not transfer metadata
org.apache.directory.api:api-all/maven-metadata.xml from/to
apache.releases.https
(https://repository.apache.org/service/local/staging/deploy/maven2):
Connect to repository.apache.org:443
[repository.apache.org/207.244.88.140] failed: Operation timed out
(Connection timed out)
...

and the process stopped with an error. The previous packages were
correctly pushed to nexus, though (except that when I tried to close the
staging repo, it told me that there were 2 missing signature, one md5
and one sha1...)

There is something fishy.



-- 
Emmanuel Lecharny

Symas.com
directory.apache.org

Attachment: pEpkey.asc
Description: application/pgp-keys

Reply via email to