geode-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John Blum (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (GEODE-23) POM file is incorrect
Date Mon, 11 May 2015 22:01:00 GMT

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

John Blum edited comment on GEODE-23 at 5/11/15 10:00 PM:
----------------------------------------------------------

2 things...

1. The {{spring-data-gemfire}} dependency either needs to have a '{{scope}}' of '{{provided}}'
or be removed all together.  I am leaning towards the later and will provide *Mark B.* with
an updated Maven POM (based on the original, template-based {{../Gemfire/release/scripts/gemfire.pom}}
file) that the new Gradle build will need to generate to +match+.

Note, this is absolutely required for [Spring Boot|https://github.com/spring-projects/spring-boot/issues/2884].


2. Concerning the *jline* dependency...

2.a. Ideally, _Gfsh_ would/could be upgraded to the latest version of [Spring Shell|http://repo.spring.io/libs-release/org/springframework/shell/spring-shell/1.1.0.RELEASE/spring-shell-1.1.0.RELEASE.pom]
(*v1.1.0.RELEASE*), as {{spring-shell-1.1.0.RELEASE}} depends on {{jline-2.11}}.

2.b. Given the technical limitations of why _Gfsh_ cannot be upgraded to the latest {{spring-shell}}
release, the obscure, unsupported and non-available {{jline-1.0.S2-B.jar}} dependency must
be resolved from the [Spring 'ext-release-local' Maven Repository|http://repo.spring.io/ext-release-local/net/sourceforge/jline/jline/1.0.S2-B/jline-1.0.S2-B.jar].

You will not find this dependency in any other public Maven Repo, hence another reason why
_Gfsh_ should be upgraded to the latest version of {{spring-shell}} (v1.1.0.RELEASE) using
a more recent, available version of [jline|http://search.maven.org/#artifactdetails%7Cjline%7Cjline%7C2.12.1%7Cjar].


was (Author: jblum):
2 things...

1. The {{spring-data-gemfire}} dependency either needs to have a '{{scope}}' of '{{provided}}'
or be removed all together.  I am leaning towards the later and will provide *Mark B.* with
an updated Maven POM (based on the original, template-based {{../Gemfire/release/scripts/gemfire.pom}}
file) that the new Gradle build will need to generate to +match+.

Note, this is absolutely required for [Spring Boot|https://github.com/spring-projects/spring-boot/issues/2884].

2. Concerning the *jline* dependency...

2.a. Ideally, _Gfsh_ would/could be upgraded to the latest version of [Spring Shell|http://repo.spring.io/libs-release/org/springframework/shell/spring-shell/1.1.0.RELEASE/spring-shell-1.1.0.RELEASE.pom]
(*v1.1.0.RELEASE*), as {{spring-shell-1.1.0.RELEASE}} depends on {{jline-2.11}}.

2.b. Given the technical limitations of why _Gfsh_ cannot be upgraded to the latest {{spring-shell}}
release, the obscure, unsupported and non-available {{jline-1.0.S2-B.jar}} dependency must
be resolved from the [Spring 'ext-release-local' Maven Repository|http://repo.spring.io/ext-release-local/net/sourceforge/jline/jline/1.0.S2-B/jline-1.0.S2-B.jar].

You will not find this dependency in any other public Maven Repo, hence another reason why
_Gfsh_ should be upgraded to the latest version of {{spring-shell}} (v1.1.0.RELEASE) using
a more recent, available version of [jline|http://search.maven.org/#artifactdetails%7Cjline%7Cjline%7C2.12.1%7Cjar].

> POM file is incorrect
> ---------------------
>
>                 Key: GEODE-23
>                 URL: https://issues.apache.org/jira/browse/GEODE-23
>             Project: Geode
>          Issue Type: Improvement
>          Components: build
>    Affects Versions: 1.0.0.0-incubating
>            Reporter: Anthony Baker
>            Assignee: Mark Bretl
>         Attachments: test.tgz
>
>
> The POM file is missing the repository location for jline.  In addition the spring-data-gemfire
dependency needs an exclusion so it does not pull in gemfire-7.0.2.
> See attached test case.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message