Why publish them as WAR files at all? As they are currently packaged they can't be deployed in just any J2EE web container because they lack all the dependencies. Sure they look like WAR files internally but they are really modules that expect to run in and only in the Geode server. Publishing them as a WAR file gives the false impression that they can be consumed by any project as a full fledged WAR.
We should make up our own JAR spec based on WAR, perhaps calling it Geode Web ARchive or GWAR for short. Yes, I just went there… GWAR!!! 🤘🎸🤘🎸🤘🎸🤘🎸 But seriously, unless it can be deployed in any J2EE web container it shouldn’t be considered a WAR. -Jake > On Sep 24, 2019, at 3:34 PM, Robert Houghton <rhough...@pivotal.io> wrote: > > I am working on the change to get the geode-web and geode-web-api war > artifacts published instead of the jars. I have found the > geode-web-management project is also producing a war artifact, in addition > to a jar. Do we want it to be published as well? What is the criterion we > use to decide? > > I think this problem was an oversight from the changes PurelyApplied and I > made to the build when we made the publish plugin 'opt-in' instead of > forced by the root project. Easy to publish one or the other, but I am not > qualified to decide whether a war or jar is more appropriate for these > modules. > > Thank you, > -Robert
