| #!/bin/bash | |
| set -e | |
| STAMP=`date +%y%m%d_%H-%M-%S` | |
| pm3 -c 'hf 14a sniff' | |
| pm3 -c 'trace list -t 14a -x' 2>/dev/null \ | |
| | text2pcap -t "%S." -l 264 - - 2>/dev/null \ | |
| | tshark -r - -T json \ |
Most of my projects get frequently released to https://mvn.javacard.pro/maven/. To use it, add this to your pom.xml:
<repositories>
<repository>
<id>javacard-pro</id>
<url>https://mvn.javacard.pro/maven/</url>
</repository>
</repositories>
Most of my projects relate to either smart cards (preferably JavaCard-s) or web and are written in Java, JavaScript or C++.
Versioning is arbitrary, "X > Y". If I could, I would use content based versioning for integrity and simplicity. But I can't, thus simple date based versions YY.MM.DD.
Fall 2017 is when I finally accepted Maven as a build and dependency tool and Maven Central as the "App Store" for Java code. Most of my time is spent in the terminal, so I tend to create standalone CLI tools as well, trimmed for distribution with ProGuard.
Availability of Library means that there is an artefact available from Maven Central. Availability of Tool means that a trimmed down, UNIX DWIM tool is downloadable from Github.
I hereby claim:
To claim this, I am signing this object:
| ### Keybase proof | |
| I hereby claim: | |
| * I am martinpaljak on github. | |
| * I am martinpaljak (https://keybase.io/martinpaljak) on keybase. | |
| * I have a public key ASB0JRz-TmzwOoS0Ym00Gha3y7iK3Uzus5vhEPcNBhJIUQo | |
| To claim this, I am signing this object: |
| #!/bin/bash | |
| # This script configures .deb based Linux repositories | |
| # License: public domain | |
| set -e | |
| # Key used for signing releases | |
| RIA_KEY="""-----BEGIN PGP PUBLIC KEY BLOCK----- | |
| Version: GnuPG v1.4.9 (GNU/Linux) | |
| mQGiBEzGeRYRBAD6h9dnYIjEWCTFdnWGLeXXTHArs4uRcN74UjrmlH230lvjjdjb |
I hereby claim:
To claim this, I am signing this object: