[GEODE-7241] Artifacts for geode-web and geode-web-api are jars instead of wars in maven central

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.8.0, 1.9.0, 1.9.1, 1.10.0
• Fix Version/s: 1.9.2, 1.11.0
• Component/s: build
• Assignee: Robert Houghton
• Reporter: Udo Kohlmeyer
• Created: 24/Sep/19 21:14
• Updated: 30/Dec/19 18:49
• Resolved: 04/Oct/19 17:22

Description

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.

Issue Links

• relates to: GEODE-7412 Artifacts for geode-pulse is a jars instead of war in maven central
• links to: GitHub Pull Request #4091