Just a final confirmation from our side. All tests on all environments run properly now, thx for the fix and the wrap up in 2.0.1
By the way: are the artifacts also going to be published on http://maven.restlet.org/org/restlet/jse/org.restlet/ ? -marc= On 09/03/2010 04:43 PM, Marc Portier wrote: > > > 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=2657231
