[ 
https://issues.apache.org/jira/browse/CXF-7893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16679484#comment-16679484
 ] 

ASF GitHub Bot commented on CXF-7893:
-------------------------------------

ffang closed pull request #472: CXF-7893 Add guava entry to cxf-parent
URL: https://github.com/apache/cxf/pull/472
 
 
   

This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:

As this is a foreign pull request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):

diff --git a/parent/pom.xml b/parent/pom.xml
index b0bffbb29ca..ae76c246dfb 100644
--- a/parent/pom.xml
+++ b/parent/pom.xml
@@ -1314,6 +1314,11 @@
                     </exclusion>
                 </exclusions>
             </dependency>
+            <dependency>
+                <groupId>com.google.guava</groupId>
+                <artifactId>guava</artifactId>
+                <version>${cxf.guava.version}</version>
+            </dependency>
             <dependency>
                 <groupId>org.apache.hbase</groupId>
                 <artifactId>hbase-client</artifactId>


 

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[email protected]


> cxf-parent should have guava entry
> ----------------------------------
>
>                 Key: CXF-7893
>                 URL: https://issues.apache.org/jira/browse/CXF-7893
>             Project: CXF
>          Issue Type: Improvement
>          Components: Configuration
>            Reporter: Tom Cunningham
>            Assignee: Freeman Fang
>            Priority: Major
>
> cxf-java2-swagger plugin requires guava 20, and I've found a couple of edge 
> cases where guava 18 slips in.    cxf-parent should have a guava 
> dependencyManagement entry to prevent this - there's already a guava.version 
> specified there, so I don't think adding the dependencyManagement entry is a 
> big deal.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to