Publish ua-parser Java lib to Maven Central

Clojure developers would find using this library a lot easier if it were published to Maven Central.

Would this require changing the package name to org.ua-parser?

Please let me know if I can help to achieve this.

+1

+1 as well

+1

+1
I guess maven is the way to go with java in general

👍

+1 as well

If this gets closed, it will be great. Maven will be nice

👍

+1 for such artifact in Maven Central

+1

@jogjayr

@jogjayr I'm not sure this is ever going to happen: this Java language repo, while having been preserved after the split/migration to the ua-parser github org, doesn't seem to be actively maintained since the split (latest commit was about 5 months ago). In the meantime, if you need Clojure functionality for doing useragent parsing, I've just released v1.0.0 of uap-clj:

https://clojars.org/uap-clj

Associated repo: https://github.com/russellwhitaker/uap-clj

Hope you find it useful.

@russellwhitaker

@russellwhitaker Nice! I personally don't need this functionality any more. Since there's now a good alternative for Clojure (thanks for that!), I'll close this issue.

@jogjayr

My pleasure @jogjayr . Feel free to post issues on that Clojure version's repo, I'm happy to consider PRs and issues. I might even consider checking with @elsigh and asking if they'd be interested in forking the now-feature-complete and fully-specification-compliant Clojure implementation to the ua-parser org.

Hang on guys, not so fast! The issue says "Publish the JAVA Library to Maven". That's what I - and I suppose a lot of other commenter - +1-ed this issue for. So please reopen the issue. I am actively using the java version of ua-parser.

The source files says Twitter copyright.
I also found version 1.3.0 in mvnrepository under Twitter Maven repo:
http://mvnrepository.com/artifact/ua_parser/ua-parser/1.3.0

I'll give it a go there.

I've updated uap-clj to v1.3.0; as before, the Java wrapper API is available as well.

We're using this for the past 3-4 weeks and it works flawlessly:
http://mvnrepository.com/artifact/ua_parser/ua-parser/1.3.0

            <dependency>
                <groupId>ua_parser</groupId>
                <artifactId>ua-parser</artifactId>
                <version>1.3.0</version>
            </dependency>

@asafm

@asafm that's an old artifact (a little over a year); does it regress 100% against the current core regexes.yaml? Curious.

@russellwhitaker

@russellwhitaker - The core code hasn't really changed so it's ok that it's over a year old. What we do in our project is pull the latest yaml file and use it, and not the one bundled in the jar. We use the following maven snippet to do it:

            <plugin>
                <groupId>org.apache.maven.plugins</groupId>
                <artifactId>maven-antrun-plugin</artifactId>
                <executions>
                    <execution>
                        <id>download-files</id>
                        <phase>process-classes</phase>
                        <goals>
                            <goal>run</goal>
                        </goals>
                        <configuration>
                            <tasks>
                                <!--User Agent processor regexes file (download from github by commit id)-->
                                <get src="https://raw.githubusercontent.com/ua-parser/uap-core/0dabfd35a465e1c7dd5b07c273d4b693d46ee387/regexes.yaml"
                                     dest="${project.build.outputDirectory}/regexes.yaml" />                                
                            </tasks>
                        </configuration>
                    </execution>
                </executions>
            </plugin>

Once in a while we update the commit ID above to be the latest after we tested it locally.

I downloaded the artifact for twitter. In it the pom.properties says:

#Generated by Maven
#Mon Nov 18 14:49:18 PST 2013
version=1.3.0
groupId=ua_parser
artifactId=ua-parser

The URL in the build in the embedded pom.xml:

  <url>https://github.com/tobie/ua-parser/</url>

Looks like a very old build.

This code works for us in production so far. There isn't any active development on it so I don't expect it to be new. Did you download from the twitter maven repo?

…

On Fri, 27 Jan 2017 at 15:42 Fabrice Bacchella ***@***.***> wrote: I downloaded the artifact for twitter. In it the pom.properties says: #Generated by Maven #Mon Nov 18 14:49:18 PST 2013 version=1.3.0 groupId=ua_parser artifactId=ua-parser The URL in the build in the embedded pom.xml: <url>https://github.com/tobie/ua-parser/</url> Looks like a very old build. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#1 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AA8Y8QhnmJWIqJba6RiPAIdgqemE7nCwks5rWfRfgaJpZM4C51D3> .

Yes it's the twitter maven repo that is too old. There has been some commit since November 2013.

An alternative is to use uap-clj, which is actively maintained. In fact, I wrote it because this Java repo isn't actively maintained. Add this to your pom.xml:

<repository>
  <id>clojars</id>
  <url>http://clojars.org/repo/</url>
</repository>

So you can pull in this dependency:

<dependency>
  <groupId>org.clojure</groupId>
  <artifactId>clojure</artifactId>
  <version>1.8.0</version>
</dependency>
<dependency>
  <groupId>uap-clj</groupId>
  <artifactId>uap-clj</artifactId>
  <version>1.3.1</version>
</dependency>

Example usage:

package useragent;

import java.util.HashMap;

// Java API for uap-clj Clojure implementation of useragent parser
import uap_clj.java.api.*;

public class Parser {
  public Parser() {};

  public static void main(String[] args) {
    String ua = args[0];

    HashMap b = Browser.lookup(ua);
    HashMap o = OS.lookup(ua);
    HashMap d = Device.lookup(ua);

    System.out.println("Browser family: " + b.get("family"));
    System.out.println("Browser major number: " + b.get("major"));
    System.out.println("Browser minor number: " + b.get("minor"));
    System.out.println("Browser patch number: " + b.get("patch"));

    System.out.println("O/S family: " + o.get("family"));
    System.out.println("O/S major number: " + o.get("major"));
    System.out.println("O/S minor number: " + o.get("minor"));
    System.out.println("O/S patch number: " + o.get("patch"));
    System.out.println("O/S patch_minor number: " + o.get("patch_minor"));

    System.out.println("Device family: " + d.get("family"));
    System.out.println("Device brand: " + d.get("brand"));
    System.out.println("Device model: " + d.get("model"));
  }
}

Is this project still maintained? If not, can someone transfer ownership?
I would like to get a new jar with the latest regexes.yaml file published to mvn central and am willing to do it myself if someone can hand it over.

I've requested a namespace on Maven Central repo.

group id: com.github.ua-parser
artifact id: uap-java

@commenthol

Attn. @commenthol

I am pleased to announce that uap-java is now published to Maven Central Repository for the first time ever.

<groupId>com.github.ua-parser</groupId>
<artifactId>uap-java</artifactId>
<version>1.4.0</version>
<packaging>jar</packaging>

This includes the latest regexes.yaml file and I fixed the tests to pass with the new file.

I also bumped the dependencies to the latest versions.

org.yaml.snakeyaml: 1.20
org.apache.commons.commons-collections4: 4.1

Great news !

Navigation Menu

Repository navigation

Publish ua-parser Java lib to Maven Central #1

41 remaining items

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Publish ua-parser Java lib to Maven Central #1

Description

Activity

russellwhitaker commented on Dec 18, 2014

magicknot commented on Jan 31, 2015

sdboer78 commented on Feb 1, 2015

MaximumDamage commented on Feb 10, 2015

kdekooter commented on Mar 10, 2015

OuIChien commented on Mar 23, 2015

vnydvd commented on Apr 22, 2015

elicwhite commented on May 31, 2015

cgi commented on Jun 1, 2015

dennismaassnp commented on Jun 1, 2015

russellwhitaker commented on Jun 3, 2015

jogjayr commented on Jun 3, 2015

russellwhitaker commented on Jun 3, 2015

kdekooter commented on Jun 4, 2015

41 remaining items

asafm commented on Nov 30, 2016

russellwhitaker commented on Dec 26, 2016

asafm commented on Dec 26, 2016

russellwhitaker commented on Dec 26, 2016

asafm commented on Jan 1, 2017

fbacchella commented on Jan 27, 2017

asafm commented on Jan 27, 2017

fbacchella commented on Jan 27, 2017

russellwhitaker commented on Jan 27, 2017

bpossolo commented on May 6, 2018

bpossolo commented on May 9, 2018

russellwhitaker commented on May 9, 2018

bpossolo commented on May 14, 2018

fbaligand commented on May 14, 2018

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions