Thanks Peter: I see Andrea already helped you test locally, if you rebase your pull request you should be able to test without error now. At least all the build box jobs are happy.
The release candidate boat has sailed, but you have a successful test finding your packaging was broken so that your extension will be included in the 2.19.0 release. The build server does run the assembly:single jobs nightly so you can double check your plugin is packaged correctly from a nightly build also. Jody On Thu, Mar 4, 2021 at 4:26 AM <[email protected]> wrote: > Hi Jody, > > > > I submitted a PR that should / may take care of getting the mapml jar into > the plugin zip, here: https://github.com/geoserver/geoserver/pull/4810 > > Should I merge it myself? > > > > The mapml plugin zip file doesn’t have the mapml jar in it yet, but I’m > not sure how to test that process (release build process I guess). When > will the release be done? I am concerned I am missing the boat. > > > > Thanks! > > > > Peter > > > > *From:* Jody Garnett <[email protected]> > *Sent:* March 2, 2021 8:17 PM > *To:* GeoServer <[email protected]> > *Subject:* [Geoserver-devel] geoserver 2.19-RC release artifacts to test > > > > Release artifacts are available to test: > https://build.geoserver.org/view/release/job/geoserver-release/22/artifact/distribution/2.19-RC > > > > This is a release candidate so the key thing is to make sure everything is > packaged up correctly (especially for new extensions) for our community to > test. > > > > If there are any testing priorities to include with the blog-post please > reply to this email (or add directly to the website pull request > <https://github.com/geoserver/geoserver.github.io/pull/99>). > > -- > > Jody Garnett > -- -- Jody Garnett
_______________________________________________ Geoserver-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-devel
