[arquillian-issues] [JBoss JIRA] (ARQ-1607) Please avoid using arquillian.launch files, it makes Eclipse generate error logs

Please avoid using arquillian.launch files, it makes Eclipse generate error logs -------------------------------------------------------------------------------- Key: ARQ-1607 URL: https://issues.jboss.org/browse/ARQ-1607 Project: Arquillian Issue Type: Feature Request Security Level: Public(Everyone can see) Environment: Eclipse Reporter: Fred Bricon Assignee: Aslak Knutsen Priority: Minor Fix For: 1.1.5.Final When imported in Eclipse, projects containing arquillian.launch files make Eclipse barf as it expects a valid Eclipse Launch configuration xml file. It's just an error in the .metadata/.log, but the sight of such ugly stacktraces could be frightening/annoying for some {noformat} !MESSAGE org.xml.sax.SAXParseException; lineNumber: 1; columnNumber: 1; Contenu non autorisé dans le prologue. occurred while reading launch configuration file: D:\tmp\arquillian-examples\arquillian-persistence-tutorial\target\test-classes\arquillian.launch. !STACK 0 org.xml.sax.SAXParseException; lineNumber: 1; columnNumber: 1; Contenu non autorisé dans le prologue. at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:198) at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.fatalError(ErrorHandlerWrapper.java:177) at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:441) at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:368) at com.sun.org.apache.xerces.internal.impl.XMLScanner.reportFatalError(XMLScanner.java:1388) at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$PrologDriver.next(XMLDocumentScannerImpl.java:998) at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:607) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:489) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:835) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:764) at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:123) at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:237) at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:300) at org.eclipse.debug.internal.core.LaunchManager.createInfoFromXML(LaunchManager.java:929) at org.eclipse.debug.internal.core.LaunchManager.getInfo(LaunchManager.java:1353) at org.eclipse.debug.internal.core.LaunchConfiguration.getInfo(LaunchConfiguration.java:453) at org.eclipse.debug.internal.core.LaunchConfiguration.getType(LaunchConfiguration.java:617) at org.eclipse.debug.internal.core.LaunchManager.isValid(LaunchManager.java:2081) at org.eclipse.debug.internal.core.LaunchManager.launchConfigurationAdded(LaunchManager.java:2104) at org.eclipse.debug.internal.core.LaunchManager$LaunchManagerVisitor.visit(LaunchManager.java:382) {noformat} From IRC {quote} (15:46:37) fbricon: hey aslak, I'm looking at a some maven projects containing some arquillian.launch files (15:47:18) fbricon: eclipse treats these as Launch configuration files and complains they're malformed xml (15:47:38) fbricon: do the files need to be .launch? 15:47:58) aslak: fbricon hehe yea.. noticed that as well.. (15:48:22) aslak: it ended up being called arquillian.launch because that's the name of the -D property that does the same (15:48:50) aslak: fbricon could you file an issue on this.. I'll add support for arquillian.launch.properties or arquillian-launch or similar {quote}