[infinispan-issues] [JBoss JIRA] (ISPN-3503) Upstream server build doesn't include protobuf libraries in client/hotrod/java directory

[Michal Linhard (JIRA)]

    [ https://issues.jboss.org/browse/ISPN-3503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12926330#comment-12926330 ] 

Michal Linhard commented on ISPN-3503:
--------------------------------------

This doesn't seem to be an issue anymore on current master, the protobuf libraries aren't included, but hotrod client can somehow live without them...

I think at the time of reporting this, I couldn't make a hotrod call without the protobuf library.
                
> Upstream server build doesn't include protobuf libraries in client/hotrod/java directory
> ----------------------------------------------------------------------------------------
>
>                 Key: ISPN-3503
>                 URL: https://issues.jboss.org/browse/ISPN-3503
>             Project: Infinispan
>          Issue Type: Bug
>          Components: Server
>    Affects Versions: 6.0.0.Alpha4
>            Reporter: Michal Linhard
>            Assignee: Tristan Tarrant
>
> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/user/mlinhard@REDHAT.COM/my-views/view/jdg-regression-tests/job/jdg-qe-build-infinispan60-snapshot-auto/84/consoleText
> This is the contents of the client/hotrod/java folder:
> {code}
>   adding: infinispan-server-6.0.x/client/hotrod/java/jboss-marshalling-river-1.3.15.GA.jar (deflated 8%)
>   adding: infinispan-server-6.0.x/client/hotrod/java/jboss-marshalling-1.3.15.GA.jar (deflated 12%)
>   adding: infinispan-server-6.0.x/client/hotrod/java/jboss-logging-3.1.1.GA.jar (deflated 10%)
>   adding: infinispan-server-6.0.x/client/hotrod/java/commons-pool-1.6.jar (deflated 8%)
>   adding: infinispan-server-6.0.x/client/hotrod/java/infinispan-commons-6.0.0-SNAPSHOT.jar (deflated 13%)
>   adding: infinispan-server-6.0.x/client/hotrod/java/infinispan-client-hotrod-6.0.0-SNAPSHOT.jar (deflated 12%)
> {code}
> JDG 6.2.0.DR4 doesn't have this problem, but this affects my regression testing where I use builds from latest upstream snapshots

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira