Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Maven signing fails for javadocs #51

Closed
mkroetzsch opened this issue Mar 28, 2014 · 1 comment
Closed

Maven signing fails for javadocs #51

mkroetzsch opened this issue Mar 28, 2014 · 1 comment
Assignees
Labels

Comments

@mkroetzsch
Copy link
Member

The signing of jars with Maven -Psign fails for javadoc jars with the current configuration (BAD signature). The apparent reason for this is that the javadoc jar is modified after the signature is created, as can be seen from the time stamps of the files in the target directory. Maven needs to be reconfigured to sign the javadocs only after they are done.

The invalid signatures are the reason why the upload at sonatype does not work yet.

@mkroetzsch mkroetzsch added this to the Wikidata Toolkit 0.1.0 milestone Mar 28, 2014
@mkroetzsch mkroetzsch added the bug label Mar 28, 2014
@mkroetzsch mkroetzsch modified the milestones: Wikidata Toolkit 0.2.0, Wikidata Toolkit 0.1.0 Mar 31, 2014
mkroetzsch added a commit that referenced this issue Jun 3, 2014
The correct command to create signed packages is:
* mvn clean install -Psign
or (if you don't care about typing your passphrase into a command line):
* mvn clean install -Psign -Dgpg.passphrase=x
@mkroetzsch
Copy link
Member Author

Fixed.

The correct command to create signed packages is:

 mvn clean install -Psign

or (if you don't care about typing your passphrase into a command line):

mvn clean install -Psign -Dgpg.passphrase=x

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants