[
https://issues.apache.org/jira/browse/GEODE-27?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15202122#comment-15202122
]
ASF subversion and git services commented on GEODE-27:
------------------------------------------------------
Commit 5839e4d2a741dd0b84ce0ed20588fb5bb2d62565 in incubator-geode's branch
refs/heads/develop from [~upthewaterspout]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=5839e4d ]
GEODE-27: A couple of tools to dump dependencies
Adding a task to dump all jars in the binary distribution
This makes it easy to see what dependencies we actually end up shipping
with the product. This dumps all jars found in the distribution or
embedded within war files in the distribution.
Adding a task to determine if a dependency is used
This task checks to see if a dependency is used in the source code.
> Apache Geode POM file(s) are incorrect!
> ---------------------------------------
>
> Key: GEODE-27
> URL: https://issues.apache.org/jira/browse/GEODE-27
> Project: Geode
> Issue Type: Bug
> Components: build, general
> Affects Versions: 1.0.0-incubating
> Environment: Apache Geode in Maven or Gradle-based applications.
> Reporter: John Blum
> Assignee: Mark Bretl
> Priority: Critical
> Labels: ApacheGeode, Maven, POM
> Fix For: 1.0.0-incubating.M2
>
> Attachments: gemfire-8.2.0.pom,
> gemfire-core-1.0.0-incubating-SNAPSHOT.pom,
> gemfire-jgroups-1.0.0-incubating-SNAPSHOT.pom,
> gemfire-joptsimple-1.0.0-incubating-SNAPSHOT.pom,
> gemfire-json-1.0.0-incubating-SNAPSHOT.pom
>
>
> This JIRA is a followup to [GEODE-23] to note the additional issues that are
> considered
> ["out-of-scope"|http://mail-archives.apache.org/mod_mbox/incubator-geode-dev/201505.mbox/ajax/%3CCA%2BULb%2Btfm4LyjwMaB_B7j8WaBNoAYj1%2BkeZSW-pqv0Gdbq2T8g%40mail.gmail.com%3E]
> for [GEODE-23], yet need to be fixed, none-the-less.
> Specifically, the changes include...
> 1. The {{<repositories>}} declarations need to be cleaned up (reduced).
> Technically, _Apache Geode_ should only require...
> {code:xml}
> <repositories>
> <repository>
> <id>gemstone-release</id>
> <name>GemStone Maven RELEASE Repository</name>
> <url>http://dist.gemstone.com/maven/release</url>
> <snapshots>
> <enabled>true</enabled>
> <updatePolicy>always</updatePolicy>
> </snapshots>
> </repository>
> <repository>
> <id>libs-release</id>
> <name>Spring Maven libs-release Repository</name>
> <url>http://repo.spring.io/libs-release</url>
> </repository>
> </repositories>
> {code}
> For instance, the "obscure" *jline-1.0.S2-B.jar* dependency is "resolvable"
> from, for instance...
> http://repo.spring.io/libs-release/net/sourceforge/jline/jline/1.0.S2-B/jline-1.0.S2-B.jar
> NOTE: by default, and unlike Gradle, Maven searches "Maven Central".
> 2. Add proper "scopes", "optional" settings and "exclusions" to the
> dependencies declared in the POM.
> 3. Many of the "explicitly" declared dependencies (e.g. spring-beans) need
> to be removed; Maven will resolve dependencies transitively.
> As an example, _Apache Geode's_ Maven POM file should be very similar to the
> {{Pivotal GemFire}} Maven POM file, as recently updated and validated for
> *GemFire 8.2* (see attached {{gemfire-8.2.0.pom}} file for further details
> and reference). This is particularly important where _Apache Geode_ and
> _Pivotal GemFire_ intersect.
> There maybe other issues with the POM file that need to be included within
> the "scope" of this +bug+ as well and should be included as such, otherwise
> this JIRA should *+not+* be marked "complete".
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
