work on resolving comments
This commit is contained in:
		
							parent
							
								
									719bcb4f94
								
							
						
					
					
						commit
						4d656d0138
					
				| @ -88,9 +88,9 @@ jobs: | |||||||
| 
 | 
 | ||||||
| ### Extra setup for pom.xml: | ### Extra setup for pom.xml: | ||||||
| 
 | 
 | ||||||
| Maven GPG Plugin configuration in pom.xml file should contain the following structure to avoid possible issues like `Inappropriate ioctl for device` or `gpg: signing failed: No such file or directory`: | The Maven GPG Plugin configuration in the pom.xml file should contain the following structure to avoid possible issues like `Inappropriate ioctl for device` or `gpg: signing failed: No such file or directory`: | ||||||
| 
 | 
 | ||||||
| ``` | ```xml | ||||||
| <configuration> | <configuration> | ||||||
|   <!-- Prevent gpg from using pinentry programs --> |   <!-- Prevent gpg from using pinentry programs --> | ||||||
|   <gpgArguments> |   <gpgArguments> | ||||||
| @ -99,7 +99,7 @@ Maven GPG Plugin configuration in pom.xml file should contain the following stru | |||||||
|   </gpgArguments> |   </gpgArguments> | ||||||
| </configuration> | </configuration> | ||||||
| ``` | ``` | ||||||
| GPG 2.1 requires `--pinentry-mode` to be set to `loopback` in order to pick up `gpg.passphrase` value defined in Maven `settings.xml` | GPG 2.1 requires `--pinentry-mode` to be set to `loopback` in order to pick up the `gpg.passphrase` value defined in Maven `settings.xml`. | ||||||
| 
 | 
 | ||||||
| ### Yaml example: | ### Yaml example: | ||||||
| ```yaml | ```yaml | ||||||
|  | |||||||
		Loading…
	
	
			
			x
			
			
		
	
		Reference in New Issue
	
	Block a user