Hi Marc, I just applied your change to the build regarding NSIS installer. Regarding the 2.0.1 release, we are planning to release it next Wednesday, and to create a 2.0 branch to get SVN trunk ready for 2.1 developments.
Best regards, Jerome -- Restlet ~ Founder and Technical Lead ~ http://www.restlet.org Noelios Technologies ~ http://www.noelios.com -----Message d'origine----- De : Marc Portier [mailto:[email protected]] Envoyé : vendredi 3 septembre 2010 16:44 À : [email protected] Objet : Re: stream closed errors On 09/03/2010 10:39 AM, Jerome Louvel wrote: > Hi Marc, > > Thanks for the investigation. I've fixed the regressions in SVN trunk and the > build should pass again. It does on my machine. > Thanks for the fixes, normal (ant) build works indeed. I need the maven artifacts however and am building with a custom.properties file. It yields on my system: > > package: > [move] Moving 1 file to > /home/mpo/Projects/tigris.org/restlet/restlet-r6843/build/dist > > BUILD FAILED > /home/mpo/Projects/tigris.org/restlet/restlet-r6843/build/build.xml:228: The > following error occurred while executing this line: > /home/mpo/Projects/tigris.org/restlet/restlet-r6843/build/build.xml:231: The > following error occurred while executing this line: > /home/mpo/Projects/tigris.org/restlet/restlet-r6843/build/build.xml:157: The > following error occurred while executing this line: > /home/mpo/Projects/tigris.org/restlet/restlet-r6843/build/build.xml:159: The > following error occurred while executing this line: > /home/mpo/Projects/tigris.org/restlet/restlet-r6843/build/temp/jse/build.xml:2261: > Warning: Could not find file > /home/mpo/Projects/tigris.org/restlet/restlet-r6843/build/temp/jse/dist/restlet-jse-2.0snapshot.exe > to copy. Which I avoid silently with the attached patch. (I don't have nsis installed and am not generating the mentioned .exe so I let the move silently go by in that case.) With this I produced a 6843 build and am seeing things working ok. Which is however no big guarantee: the nature of this gc related behavior has been rather unpredictable in our experience. I'm setting up the new restlet dependency in our build and let you know next week if this actually solves things on all our environments: my personal environment never showed the issue, so I need to trigger some colleagues to do further testing in environments that _always_ barfed up on this. Related: this fix seems rather pressing for 2.0.0 in general no? Are you guys foreseeing a 2.0.1 for this shortly? (Or for any other reason) regards, -marc= ------------------------------------------------------ http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2655192 ------------------------------------------------------ http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2655469
