Hmm, I thought this was implicitly fixed by various build refactorings that went into 1.11.0. I see that we're creating local maven artifacts for geode-pulse-1.11.0.war. The next question is then whether we're actually publishing those.
--Jens On Fri, Nov 8, 2019 at 12:56 PM Owen Nichols <onich...@pivotal.io> wrote: > +1 > > > On Nov 8, 2019, at 12:54 PM, Udo Kohlmeyer <u...@apache.com> wrote: > > > > @Owen, > > > > I did not specifically check all web archives for this issue. Yes, I > *should* have been caught in that ticket. > > > > On 11/8/19 11:03 AM, Owen Nichols wrote: > >> I’m curious, how was this missed in > https://issues.apache.org/jira/browse/GEODE-7241 < > https://issues.apache.org/jira/browse/GEODE-7241> ? > >> > >>> On Nov 8, 2019, at 10:56 AM, Udo Kohlmeyer <u...@apache.com> wrote: > >>> > >>> Hi there Geode Dev, > >>> > >>> I would like to request that we add > https://issues.apache.org/jira/browse/GEODE-7412 < > https://issues.apache.org/jira/browse/GEODE-7412> to the 1.11 release. > >>> > >>> This change is a build change that has crept in since 1.8. The issue > that is to be fixed is that the web archive, (geode-pulse) has since 1.8 > been uploaded as a jar file to maven central. > >>> > >>> I would like to fix this by having the WAR artifact being pushed to > maven central again. > >>> > >>> --Udo > >>> > >> > >
