Yes please go ahead. But also please create a JIRA ticket and include the svn revision of your commit in the ticket. Karl
On Fri, Feb 8, 2013 at 6:39 AM, Maciej Liżewski <[email protected]> wrote: > I am ok with that. I would suggest also one more little change in > jetty-runner pom.xml file: > instead of <scope>provided</scope> for javax.servlet library I would change > it to <scope>runtime</scope>, to make 'mvn exec:exec' working correctly > (patch attached). Now it says that classess from servlet library are unknown > when run with maven... If there are no cons - I can commit this change to > trunk. > > > 2013/2/8 Karl Wright <[email protected]> >> >> +1, as soon as everyone is happy that the fix is correct. >> >> Since we seem to agree there will be a 1.1.1 release, I'd also like to >> consider including these other fixes: >> >> - fixes needed so that Maven build works >> - ElasticSearch connector fixes, so that the connector functions and >> is not crippled >> >> Thoughts? >> >> Karl >> >> On Fri, Feb 8, 2013 at 4:51 AM, Erlend Garåsen <[email protected]> >> wrote: >> > On 08.02.13 10.31, Maciej Liżewski wrote: >> >> >> >> I would go with patch. It is serious enough because causes problems >> >> with >> >> running crawler jobs... >> > >> > >> > +1. >> > >> > I'm running the job once again and examining the logs. I will report any >> > suspicious deviations continuously. >> > >> > I think it is advisable that I complete this job before I conclude that >> > we >> > have got rid of the problem. This may take some time, probably about 30 >> > hours. >> > >> > Erlend >> > >> > -- >> > Erlend Garåsen >> > Center for Information Technology Services >> > University of Oslo >> > P.O. Box 1086 Blindern, N-0317 OSLO, Norway >> > Ph: (+47) 22840193, Fax: (+47) 22852970, Mobile: (+47) 91380968, VIP: >> > 31050 > >
