This is the Java implementation of ua-parser. The implementation uses the shared regex patterns and overrides from regexes.yaml.
uap-java depends on the uap-core project therefore it uses a Git submodule to represent that dependency.
Before building uap-java, a copy of the uap-core project must be checked out within the local uap-java repository.
In order to do this, execute the following command (from the base uap-java
folder) to initialize and checkout the submodule.
git submodule update --init --remote --checkout --recursive
you will then have the following folder uap-java/uap-core
which contains the child repository.
To build the project, execute
mvn package
import ua_parser.Parser;
import ua_parser.Client;
...
String uaString = "Mozilla/5.0 (iPhone; CPU iPhone OS 5_1_1 like Mac OS X) AppleWebKit/534.46 (KHTML, like Gecko) Version/5.1 Mobile/9B206 Safari/7534.48.3";
Parser uaParser = new Parser();
Client c = uaParser.parse(uaString);
System.out.println(c.userAgent.family); // => "Mobile Safari"
System.out.println(c.userAgent.major); // => "5"
System.out.println(c.userAgent.minor); // => "1"
System.out.println(c.os.family); // => "iOS"
System.out.println(c.os.major); // => "5"
System.out.println(c.os.minor); // => "1"
System.out.println(c.device.family); // => "iPhone"
Create a ~/.m2/settings.xml file with the following contents:
<settings>
<servers>
<server>
<id>ossrh</id>
<username>YOUR_OSSRH_USERNAME</username>
<password>YOUR_OSSRH_PASSWORD</password>
</server>
</servers>
<profiles>
<profile>
<id>ossrh</id>
<properties>
<gpg.keyname>YOUR_GPG_KEY_ID</gpg.keyname>
<gpg.executable>GPG_EXECUTABLE</gpg.executable>
<gpg.passphrase>YOUR_KEY_PASSPHRASE</gpg.passphrase>
</properties>
</profile>
</profiles>
</settings>
On Mac OS X, the gpg.executable
property should be gpg2
.
- bump pom.xml version to non-snapshot version
- commit and push to github
mvn clean deploy -P ossrh
- log in to Sonatype OSSRH
- click Staging Repositories
- find the release
comgithubua-parser-*
- verify the contents are ok
- click Close (wait for validation steps under the Activity tab to complete)
- click Release
- bump pom.xml version to next snapshot version
- commit and push to GitHub
- update changelog wiki page
Deploying to Sonatype OSSRH using Maven
Releasing the artifact in Sonatype OSSRH
Sonatype OSSRH is synced with Maven Central Repository so the artifacts will appear in Maven Central Repo automatically shortly after releasing.
Changelog can be found here.
- Steve Jiang @sjiang
Based on the python implementation by Lindsey Simon and using agent data from BrowserScope