geode-issues mailing list archives

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

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

ASF subversion and git services commented on GEODE-27:
------------------------------------------------------

Commit dc94a890d94381e9fec1b55f3523aa5c2ab379e0 in incubator-geode's branch refs/heads/feature/GEODE-1050
from [~upthewaterspout]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=dc94a89 ]

GEODE-27: Enabling transitive dependencies in the build

Removing the code from the build that disabled transitive dependencies.
Adding excludes and forcing some versions to clean up the list of jars
we are pulling in to match what it was before I enabled transitive
dependencies.

A couple of versions don't match because the versions we were pulling in
before were not consistent across submodules for commons logging and
commons-beanutils.

Some of these excludes, and all of the forced versions look suspect.
They need to be reviewed to see if we really need them.


> 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: 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,
geode-core-1.0.0-incubating.M2-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)

Mime
View raw message