[
https://issues.apache.org/jira/browse/BEAM-3608?focusedWorklogId=158926&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-158926
]
ASF GitHub Bot logged work on BEAM-3608:
----------------------------------------
Author: ASF GitHub Bot
Created on: 25/Oct/18 22:44
Start Date: 25/Oct/18 22:44
Worklog Time Spent: 10m
Work Description: kennknowles commented on a change in pull request
#6809: [BEAM-3608] Vendor guava 20.0
URL: https://github.com/apache/beam/pull/6809#discussion_r228359029
##########
File path: vendor/guava-20_0/build.gradle
##########
@@ -0,0 +1,32 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one
+ * or more contributor license agreements. See the NOTICE file
+ * distributed with this work for additional information
+ * regarding copyright ownership. The ASF licenses this file
+ * to you under the Apache License, Version 2.0 (the
+ * License); you may not use this file except in compliance
+ * with the License. You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an AS IS BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+
+apply plugin: org.apache.beam.gradle.VendorJavaPlugin
+
+description = "Apache Beam :: Vendored Dependencies :: Guava 20"
+
+vendorJava {
+ dependency = "com.google.guava:guava:20.0"
+ packagesToRelocate = ["com.google.common", "com.google.thirdparty"]
+ intoPackage = "org.apache.beam.guava.v20_0"
+ groupId = "org.apache.beam"
+ artifactId = "beam-vendored-guava-20_0"
+ version = "0.1"
+}
+
+doVendorJava()
Review comment:
One pitfall is that I had to do something like this. Basically my
understanding is that the `VendorJavaPlugin.apply` method runs in the
configuration phase but the actual logic we want has to run after _all_ the
configuration is complete, so the `VendorJavaExtension` object has its fields
written. In all the examples I found, the extension object is only accessed via
tasks and other things that happen at a later phase. I think that basically
plugins causing configuration seems very badly supported.
----------------------------------------------------------------
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]
Issue Time Tracking
-------------------
Worklog Id: (was: 158926)
Time Spent: 3h (was: 2h 50m)
> Vendor Guava
> ------------
>
> Key: BEAM-3608
> URL: https://issues.apache.org/jira/browse/BEAM-3608
> Project: Beam
> Issue Type: Sub-task
> Components: runner-core, sdk-java-core
> Reporter: Kenneth Knowles
> Priority: Major
> Time Spent: 3h
> Remaining Estimate: 0h
>
> Instead of shading as part of our build, we can shade before build so that it
> is apparent when reading code, and in IDEs, that a particular class resides
> in a hidden namespace.
> {{import com.google.common.reflect.TypeToken}}
> becomes something like
> {{import org.apache.beam.private.guava21.com.google.common.reflect.TypeToken}}
> So we can very trivially ban `org.apache.beam.private` from public APIs
> unless they are annotated {{@Internal}}, and it makes sharing between our own
> modules never get broken by shading again.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
