[
https://issues.apache.org/jira/browse/GEODE-7241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Houghton resolved GEODE-7241.
------------------------------------
Fix Version/s: 1.11.0
Resolution: Fixed
> Artifacts for geode-web and geode-web-api are jars instead of wars in maven
> central
> -----------------------------------------------------------------------------------
>
> Key: GEODE-7241
> URL: https://issues.apache.org/jira/browse/GEODE-7241
> Project: Geode
> Issue Type: Bug
> Components: build
> Affects Versions: 1.8.0, 1.9.0, 1.9.1, 1.10.0
> Reporter: Udo Kohlmeyer
> Assignee: Robert Houghton
> Priority: Major
> Fix For: 1.11.0
>
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> In maven central the artifact for `geode-web` and `geode-web-api` are jars
> instead of the expected wars.
> This seems to be problem with the build/publish script that seems to have
> changed in 1.8.
> As this problem started in 1.8
> This has become a problem when running the Spring Data Geode examples and
> tests. The functionality that is now impeded, is the ability to start a
> Server with HTTP enabled using only maven/gradle dependency management. The
> functionality to enable this was enabled by GEODE-5660, the ability to find
> the `geode-web` and `geode-web-api` artifacts on the classpath.
> Removing this ability will hinder users to effectively run any GEODE
> integration tests which might want to use the REST interfaces. Making sure
> that the correct version of the Geode project is installed in order to start
> a server(s) is a little cumbersome.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
