...
Maven it picks the wagon implementation based on the repository protocol URL.
If you call your wagon "myw" and the URL is myw://superfast.com/my.jar, then if desired wagon has a role hint = myw, it will be selected for transport
Mercury wagon provider progress tracking
Is in this jira
Mercury wagon provider - how to configure PGP signatures
Configuration: in order to:
- generate PGP signatures, set all writer properties
- for signature verification. Use reader configuration
To wake up PGP functionality in Mercury wagon, specify -Dmaven.mercury.wagon.pgp.config=property file on the command line. Property file, pointed by this system property, has the following structure:
Code Block | ||
---|---|---|
| ||
###########################################
# Mercury wagon provider PGP configuration
###########################################
# path to the file - public keyring with all the public keys that are authorized to sign artifacts
#reader.keyring=/my/home/.gnupg/pubring.gpg
# path to the file - secret keyring with the signer key
writer.keyring=/my/home/.gnupg/secring.gpg
# keyId in the keyring - should be *16 hex digits* !
writer.key.id=0EDB5D91141BC4F2
# secret key password
writer.key.pass=mySecretKeyPassword
|
Please note that reader.keyring and writer.keyring point to an actual keyring file. I used GNUpg tools for Mac for key maintenance - http://www.gnupg.org/
Panel | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||
If repository does not have .asc pgp signatures and Maven tries to read from it, now it may create problems. In this case there is an undocumented facility to sign entire repository. Please comment here if that is needed. |
...