CLONE -Line break in DSL isnot generated anymore since Drools 5.0.0 CR1 ----------------------------------------------------------------------- Key: JBRULES-2173 URL: https://jira.jboss.org/jira/browse/JBRULES-2173 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-compiler Affects Versions: 5.0.0.CR1 Environment: jre6u12 eclipse 3.4 win xp Reporter: Neil Wallace Assignee: Edson Tirelli Fix For: 5.0.1.FINAL In Drools 4.0.7 and 5.0.0M5 it was possible to generate linebreaks using \n in an dsl-File. Since 5.0.0 CR1 this is no longer possible: the \n is simply converted to the letter n which leads to compile-errors concerning the replaced code. Example DSL: # Test linebreak-bug since 5.0.0 CR1 [*][]only a simple test = System.out.println \n ("Did it generate a line break?"); Example DSLR: #created on: 12.03.2009 package linebreak expander linebreakbug.dsl rule "line break bugtest" when #conditions then only a simple test end This leads to the line System.out.println n ("Did it generate a line break?"); Maybe this bug is related to https://jira.jboss.org/jira/browse/JBRULES-1970 where the handling of #-Characters in DSL-Files had been fixed. In my special case I'v got an workaround, but that's no workaround for anyone: Using one DSLR I generate 2 Outputs: a) using DSLR with dsl-file-A leads to "DLR"-Code: I don't need line breaks here (today, but maybe next month?) I don't care if the generated Code is nice or not and if the line is long or not. The code works and is executed by the rules-engine. Everything fine here. b) using DSLR with dsl-file-B leads to programming-code in another programming-language. This Code is never executed in Drools, it is simply generated. The result is taken an copied into the target-system. For that task I have written an own plugin that does that stuff and works like a little post-processor. So my workaround is to use my own "keyword" $CRLF in an DSL-File and - after the generation that Drools does - replaced that with "\n". Not where nice but simple... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira