Closed cdietrich closed 1 year ago
saxexception("done") produded at
EcorePlugin$1Handler.startElement(String, String, String, Attributes) line: 383
SAXParserImpl$JAXPSAXParser(AbstractSAXParser).startElement(QName, XMLAttributes, Augmentations) line: 518
XMLNSDocumentScannerImpl.scanStartElement() line: 374
XMLNSDocumentScannerImpl$NSContentDriver.scanRootElementHook() line: 613
XMLNSDocumentScannerImpl$NSContentDriver(XMLDocumentFragmentScannerImpl$FragmentContentDriver).next() line: 3079
XMLDocumentScannerImpl$PrologDriver.next() line: 836
XMLNSDocumentScannerImpl(XMLDocumentScannerImpl).next() line: 605
XMLNSDocumentScannerImpl.next() line: 112
XMLNSDocumentScannerImpl(XMLDocumentFragmentScannerImpl).scanDocument(boolean) line: 542
XIncludeAwareParserConfiguration(XML11Configuration).parse(boolean) line: 889
XIncludeAwareParserConfiguration(XML11Configuration).parse(XMLInputSource) line: 825
SAXParserImpl$JAXPSAXParser(XMLParser).parse(XMLInputSource) line: 141
SAXParserImpl$JAXPSAXParser(AbstractSAXParser).parse(InputSource) line: 1224
SAXParserImpl$JAXPSAXParser.parse(InputSource) line: 637
SAXParserImpl.parse(InputSource, DefaultHandler) line: 326
EcorePlugin.computePlatformPluginToPlatformResourceMap() line: 460
we have a project that has a plugin.xml with no id and no manifest
Is it a "broken" project? Of course we expect every bundle to have an ID...
I'm not sure I understand why there would be no manifest?
it is cause this is not a plugin project. the question is why it has the plugin.xml but no manifest need to find out with @lorenzobettini
As I said in our bug: Yes: that is a JAR packaging type project, with no PDE nature, whose tests are meant to be executed with maven surefire, NOT with tycho surefire, so the missing MANIFEST is intentional. I can't say anything about the plugin.xml file because it's always been there, and I left it as it is.
FYI, I just ripped the support for processing the plugin.xml. Surely no one in the world has such pre-OSGi bundles anymore.
in our Xtext dev IDE the log is spammed with following exception it would be nice to also log the offending plugin.xml file
in this case remote debugging revealed https://github.com/eclipse/xtext/issues/2189 as cause but the question is what is bad. aint it normal there is no pluginId?
no it seems to be logged for all plugin.xml