[ https://issues.jboss.org/browse/JBIDE-11806?page=com.atlassian.jira.plugi... ] Radim Hopp updated JBIDE-11806: ------------------------------- Attachment: CentralWithoutInternet.png Sorry... forgot to upload... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-11806?page=com.atlassian.jira.plugi... ] Radim Hopp commented on JBIDE-11806: ------------------------------------ {quote}What message would you like to see?{quote} On second thought, I think the message is appropriate. {quote} When trying to create example/quickstart which is not cached (so it won't create), there is still offered readme.md to be opened (which of course doesn't exist) -> errors in Error Log{quote} Readme isn't shown, but there are still errors in Error Log: Three errors {noformat}org.xml.sax.SAXParseException; Premature end of file. at org.apache.xerces.parsers.DOMParser.parse(Unknown Source) at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(Unknown Source) at javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:205) at org.jboss.tools.project.examples.model.ProjectExampleUtil$FetchProjectExampleDocumentTask.call(ProjectExampleUtil.java:937) at org.jboss.tools.project.examples.model.ProjectExampleUtil$FetchProjectExampleDocumentTask.call(ProjectExampleUtil.java:1) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:722) {noformat} And two "Premature end of file." warnings. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-11806?page=com.atlassian.jira.plugi... ] Snjezana Peco commented on JBIDE-11806: --------------------------------------- This error means that some project example xml file isn't valid. However, I can't reproduce the issue using the trunk. What version of JBT/JBDS are you using? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-11806?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-11806: --------------------------------------------- sounds like a different bug - open a new jira on that. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-11806?page=com.atlassian.jira.plugi... ] Snjezana Peco resolved JBIDE-11806. ----------------------------------- Resolution: Cannot Reproduce Bug I have tested JBDS 6.0.0 Alpha2d. When starting JBDS the first time without any internet connection, there are the following errors in the error log: Invalid URL xxx UnknownHostException xxx Once, when you start JBDS with a correct internet connection, the errors disappear no matter if you start JBDS with or without a connection the next time. This is expected behavior. The error you have got is caused by an invalid project xml file in the workspace. The error will also disappear if you start JBDS with a valid connection. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira