We are running GeoServer 2.7.2 on Jetty 9.2 and Java 8 in a production capacity, so far without issue (RHEL 6.6).
Just thought I'd throw that in there. Jason Newmoyer Newmoyer Geospatial Solutions 843.606.0424 ja...@newmoyergeospatial.com On Mon, Oct 26, 2015 at 3:14 PM, Justin Deoliveira <jdeol...@gmail.com> wrote: > I did, as it was there before. So I just updated the copy. That said we > could probably change that and depend on it as a maven artifact. That is > what the mac installer does. It just requires we make some updates to the > assembly scripts. If you feel strongly about that I suggest we open up a > separate jira for that. > > > > On Mon, Oct 26, 2015 at 1:07 PM, Jody Garnett <jody.garn...@gmail.com> > wrote: > >> Thanks Justin, quick review left me with one question. Not sure if you >> intended to commit src/release/jetty/start.jar as a binary file. >> >> -- >> Jody Garnett >> >> On 26 October 2015 at 11:23, Justin Deoliveira <jdeol...@gmail.com> >> wrote: >> >>> Hey folks, >>> >>> Pull request ready. >>> >>> https://github.com/geoserver/geoserver/pull/1301 >>> >>> I’ve updated and tested the mac/win/bin installers. Also took the war >>> for a spin just for the sake of it and no issues there. >>> >>> -Justin >>> >>> >>> On Sun, Oct 25, 2015 at 4:54 PM, Justin Deoliveira <jdeol...@gmail.com> >>> wrote: >>> >>>> Thanks Jody. Nope, I’m not blocked on anything, as soon as I verify >>>> that there are no issues with the other release artifacts I’ll submit the >>>> pull request for review. >>>> >>>> I decided not to make this change contingent on the java 8 upgrade. >>>> Although once the upgrade happens if we want to jump to jetty 9.3 that >>>> should be trivial because as far as I can see there aren’t any api changes >>>> going from 9.2 to 9.3. >>>> >>>> On Sun, Oct 25, 2015 at 4:51 PM, Jody Garnett <jody.garn...@gmail.com> >>>> wrote: >>>> >>>>> Thanks Justin, epic work pulling all the threads together. >>>>> >>>>> I need to catch up on what is needed where - can I confirm your work >>>>> is not blocked on anything? >>>>> On Sun, Oct 25, 2015 at 3:40 PM Justin Deoliveira <jdeol...@gmail.com> >>>>> wrote: >>>>> >>>>>> Great, thanks for the info guys. Good to know Jukka has had success. >>>>>> At the moment I’ve been working on updating the build time dependency, >>>>>> since as you know we have a bunch of test scoped dependencies on jetty, >>>>>> and >>>>>> we depend on it to build the release artifacts. >>>>>> >>>>>> The first hitch I hit was the servlet-api dependency. Jetty 9.x >>>>>> requires the 3.1 version of the dependency. So my first inclination was >>>>>> to >>>>>> upgrade everything to use that version, but unfortunately that doesn’t >>>>>> look >>>>>> all that easy. The issue is the mockrunner library we use for tests, it >>>>>> requires the 2.5. I looked for a newer version that implemented the 3.1 >>>>>> version and allI found was an open github ticket from last year. I think >>>>>> the best long term solution here is to ditch mockrunner and use the mock >>>>>> http classes from spring. Unfortunately that is a bit of a bigger job. >>>>>> Possibly something to be tackled during a code sprint with many hands on >>>>>> deck. >>>>>> >>>>>> So for now I’ve decided to keep the dependency at 2.4 and instead >>>>>> just update the test scope dependency from web/app that is used in the >>>>>> test >>>>>> runner. That works, however it required use to use “provided” scope for >>>>>> the >>>>>> upstream modules that depend on servlet-api. Which actually is what is >>>>>> recommended for maven projects with that dependency. >>>>>> >>>>>> Here is the upgrade patch: >>>>>> >>>>>> >>>>>> https://github.com/geoserver/geoserver/compare/master...jdeolive:jetty-upgrade >>>>>> >>>>>> I’ve run all the unit tests for core modules, extensions, and >>>>>> community release modules. No issues there. I’ve also tested that the bin >>>>>> artifact runs without an issue. Haven’t yet verified any of the other >>>>>> artifacts. I was going to verify no issues with the other artifacts and >>>>>> then probably call this one good to go unless anyone has any concerns. >>>>>> >>>>>> Thanks! >>>>>> >>>>>> -Justin >>>>>> >>>>>> >>>>>> On Sun, Oct 25, 2015 at 3:26 AM, Rahkonen Jukka (MML) < >>>>>> jukka.rahko...@maanmittauslaitos.fi> wrote: >>>>>> >>>>>>> Hi, >>>>>>> >>>>>>> >>>>>>> >>>>>>> I made a test and I could run Geoserver 2.8 on Jetty 9.3.3 on >>>>>>> Windows. >>>>>>> >>>>>>> >>>>>>> http://osgeo-org.1560.x6.nabble.com/Re-Geoserver-devel-changing-data-directory-using-geoserver-war-with-jetty-td5230039.html >>>>>>> >>>>>>> >>>>>>> >>>>>>> I also asked in another mail about how could I help with updating >>>>>>> the Jetty version that we ship with Geoserver. I can have a try with >>>>>>> making the startup.bat to work with the new Jetty but I can’t help with >>>>>>> making the .exe installer etc. I am willing to test when someone makes >>>>>>> such >>>>>>> installer. >>>>>>> >>>>>>> >>>>>>> >>>>>>> -Jukka Rahkonen- >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> Andrea Aime wrote: >>>>>>> >>>>>>> >>>>>>> >>>>>>> On Sun, Oct 25, 2015 at 2:55 AM, Justin Deoliveira < >>>>>>> jdeol...@gmail.com> wrote: >>>>>>> >>>>>>> Since it seems like now is a good time for upgrades how do people >>>>>>> feel about a jetty upgrade? The 6.x version we are using is far past >>>>>>> unmaintained at this point. I was thinking if we can jump straight to >>>>>>> version 9? It looks like 9.3+ requires java 8 so I was going to see how >>>>>>> it >>>>>>> looked upgrading to the latest 9.2. >>>>>>> >>>>>>> >>>>>>> >>>>>>> Yep... the switch to Java 8 is currently blocked by the main repo >>>>>>> failure, the subsequent change to cloud based repo and >>>>>>> >>>>>>> redirection issues, and I believe also by the planned switch of Ares >>>>>>> onto a cloud machine. >>>>>>> >>>>>>> >>>>>>> >>>>>>> I believe Jukka was also looking into a jetty upgrade, there was a >>>>>>> bit of discussion, but don't know >>>>>>> >>>>>>> if he started working on it, or not (it's been some time ago, >>>>>>> haven't heard back, so maybe not). >>>>>>> >>>>>>> I've cc'ed him in this conversation. >>>>>>> >>>>>>> >>>>>>> >>>>>>> Cheers >>>>>>> >>>>>>> Andrea >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> >>>>>>> == >>>>>>> >>>>>>> GeoServer Professional Services from the experts! Visit >>>>>>> >>>>>>> http://goo.gl/it488V for more information. >>>>>>> >>>>>>> == >>>>>>> >>>>>>> >>>>>>> >>>>>>> Ing. Andrea Aime >>>>>>> >>>>>>> @geowolf >>>>>>> >>>>>>> Technical Lead >>>>>>> >>>>>>> >>>>>>> >>>>>>> GeoSolutions S.A.S. >>>>>>> >>>>>>> Via Poggio alle Viti 1187 >>>>>>> >>>>>>> 55054 Massarosa (LU) >>>>>>> >>>>>>> Italy >>>>>>> >>>>>>> phone: +39 0584 962313 >>>>>>> >>>>>>> fax: +39 0584 1660272 >>>>>>> >>>>>>> mob: +39 339 8844549 >>>>>>> >>>>>>> >>>>>>> >>>>>>> http://www.geo-solutions.it >>>>>>> >>>>>>> http://twitter.com/geosolutions_it >>>>>>> >>>>>>> >>>>>>> >>>>>>> *AVVERTENZE AI SENSI DEL D.Lgs. 196/2003* >>>>>>> >>>>>>> Le informazioni contenute in questo messaggio di posta elettronica >>>>>>> e/o nel/i file/s allegato/i sono da considerarsi strettamente >>>>>>> riservate. Il >>>>>>> loro utilizzo è consentito esclusivamente al destinatario del messaggio, >>>>>>> per le finalità indicate nel messaggio stesso. Qualora riceviate questo >>>>>>> messaggio senza esserne il destinatario, Vi preghiamo cortesemente di >>>>>>> darcene notizia via e-mail e di procedere alla distruzione del messaggio >>>>>>> stesso, cancellandolo dal Vostro sistema. Conservare il messaggio >>>>>>> stesso, >>>>>>> divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od >>>>>>> utilizzarlo per finalità diverse, costituisce comportamento contrario ai >>>>>>> principi dettati dal D.Lgs. 196/2003. >>>>>>> >>>>>>> >>>>>>> >>>>>>> The information in this message and/or attachments, is intended >>>>>>> solely for the attention and use of the named addressee(s) and may be >>>>>>> confidential or proprietary in nature or covered by the provisions of >>>>>>> privacy act (Legislative Decree June, 30 2003, no.196 - Italy's New Data >>>>>>> Protection Code).Any use not in accord with its purpose, any disclosure, >>>>>>> reproduction, copying, distribution, or either dissemination, either >>>>>>> whole >>>>>>> or partial, is strictly forbidden except previous formal approval of the >>>>>>> named addressee(s). If you are not the intended recipient, please >>>>>>> contact >>>>>>> immediately the sender by telephone, fax or e-mail and delete the >>>>>>> information in this message that has been received in error. The sender >>>>>>> does not give any warranty or accept liability as the content, accuracy >>>>>>> or >>>>>>> completeness of sent messages and accepts no responsibility for changes >>>>>>> made after they were sent or for other risks which arise as a result of >>>>>>> e-mail transmission, viruses, etc. >>>>>>> >>>>>>> >>>>>>> >>>>>>> ------------------------------------------------------- >>>>>>> >>>>>> >>>>>> >>>>>> ------------------------------------------------------------------------------ >>>>>> _______________________________________________ >>>>>> Geoserver-devel mailing list >>>>>> Geoserver-devel@lists.sourceforge.net >>>>>> https://lists.sourceforge.net/lists/listinfo/geoserver-devel >>>>>> >>>>> -- >>>>> -- >>>>> Jody Garnett >>>>> >>>> >>>> >>> >> > > > ------------------------------------------------------------------------------ > > _______________________________________________ > Geoserver-devel mailing list > Geoserver-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/geoserver-devel > >
------------------------------------------------------------------------------
_______________________________________________ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
