From: Stefan F. <ste...@we...> - 2012-03-06 22:19:12
|
From the above communication and missing error reports it seems that others were able to start 1.7.0 from the released packages? Due to a last second change of the build script I changed accidentally a "." into a "-" inside the jar manifest. As I thought I only changed the section that relates to the automated transfer to sourceforge i did not check if it still starts. This causes the released package to stop with an error (a NoClassDefFoundError) before rails can display anything. At least this happens on my Linux openJDK system. Other experiences on other systems? If all others are happy I will still wait for further bugs. Thanks, Stefan |