Github user joshelser commented on a diff in the pull request:
https://github.com/apache/accumulo/pull/131#discussion_r71821510
--- Diff: assemble/src/main/scripts/generate-download-script.sh ---
@@ -0,0 +1,56 @@
+#! /usr/bin/env bash
+
+# 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.
+
+# This script will generate a DEPENDENCIES listing of packaged dependencies
+
+in=target/dependencies.raw.txt
+out=target/download-dependencies
+
+cat >"$out" <<'EOF'
+#! /usr/bin/env bash
+# This script downloads the following jars, identified by their maven
+# coordinates, using the maven-dependency-plugin.
+#
+# DISCLAIMER: This is only one possible way to download a set of
dependencies
--- End diff --
Oh, and as a concrete example which hopefully drives home my point. Let's
take Guava.
In Accumulo, we require a specific range of Guava versions, and, given
their liberal deprecation+removal policy, I would guess that over time, the
number of ranges that will work for Accumulo will grow smaller and smaller.
Hypothetically, a user might require Guava 18.0 for their application but
we might need a Guava between 13.0 and 17.0. How does a user/packager find out
that they can't actually use Guava 18.0?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
