geode-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <>
Subject [jira] [Commented] (GEODE-27) Apache Geode POM file(s) are incorrect!
Date Fri, 18 Mar 2016 21:43:33 GMT


ASF subversion and git services commented on GEODE-27:

Commit e2695a5b5ec0f244a091746108898bb6b4069d69 in incubator-geode's branch refs/heads/feature/GEODE-1050
from [~upthewaterspout]
[;h=e2695a5 ]

GEODE-27: Removing a bogus include of a jetty class

This include was not actually used

> Apache Geode POM file(s) are incorrect!
> ---------------------------------------
>                 Key: GEODE-27
>                 URL:
>             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: Dan Smith
>            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
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></url>
>       <snapshots>
>         <enabled>true</enabled>
>         <updatePolicy>always</updatePolicy>
>       </snapshots>
>     </repository>
>     <repository>
>       <id>libs-release</id>
>       <name>Spring Maven libs-release Repository</name>
>       <url></url>
>     </repository>
>   </repositories>
> {code}
> For instance, the "obscure" *jline-1.0.S2-B.jar* dependency is "resolvable" from, for
> 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

View raw message