There are no available Samebug tips for this exception. Do you have an idea how to solve this issue? A short tip would help users who saw this issue last week.

  • Can't start Frostwire - FrostWire Community Forums
    via by Unknown author,
  • XML Deserializing java XSTream issue
    via by Unknown author,
  • NetBeans IDE nicht zu starten -
    via by Unknown author,
  • How to configure JspTest?
    via by Unknown author,
  • Regs record & submit
    via jvoicexml by jagath_kumara
  • Project is created using spring-osgi-bundle archetype 1.2.0 with some fixes Doing mvn clean package works alright After the first package, the second package always fails with this error So I have to mvn clean each time I want to build without error Switching to maven-bundle-plugin works fine The obvious question: Why SpringSource created Bundlor, why not just extend/collaborate/improve on maven-bundle-plugin? :-( open source fragmentation... Complete error: [INFO] [com.springsource.bundlor.:transform {execution: bundle-manifest}] [Fatal Error] :1:1: Content is not allowed in prolog. [INFO] ------------------------------------------------------------------------ [ERROR] FATAL ERROR [INFO] ------------------------------------------------------------------------ [INFO] org.xml.sax.SAXParseException: Content is not allowed in prolog. [INFO] ------------------------------------------------------------------------ [INFO] Trace java.lang.RuntimeException: org.xml.sax.SAXParseException: Content is not allowed in prolog. at at at$2.analyse( at at at at at com.springsource.bundlor.maven.plugin.AbstractBundlorMojo.execute( at org.apache.maven.plugin.DefaultPluginManager.executeMojo( at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals( at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle( at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal( at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures( at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments( at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute( at org.apache.maven.DefaultMaven.doExecute( at org.apache.maven.DefaultMaven.execute( at org.apache.maven.cli.MavenCli.main( at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke( at sun.reflect.DelegatingMethodAccessorImpl.invoke( at java.lang.reflect.Method.invoke( at org.codehaus.classworlds.Launcher.launchEnhanced( at org.codehaus.classworlds.Launcher.launch( at org.codehaus.classworlds.Launcher.mainWithExitCode( at org.codehaus.classworlds.Launcher.main( Caused by: org.xml.sax.SAXParseException: Content is not allowed in prolog. at at at ... 25 more
    via by Hendy Irawan,
    • org.cybergarage.xml.ParserException: org.xml.sax.SAXParseException: Content is not allowed in trailing section. at org.cybergarage.xml.parser.XercesParser.parse( at org.cybergarage.soap.SOAPRequest.postMessage( at at org.cybergarage.upnp.Action.postControlAction( at com.limegroup.gnutella.UPnPManager.addMapping( at com.limegroup.gnutella.UPnPManager.mapPort( at com.limegroup.gnutella.Acceptor.init( at com.limegroup.gnutella.RouterService$ at com.limegroup.gnutella.util.ThreadFactory$ at com.limegroup.gnutella.util.DefaultThreadPool$ at Caused by: org.xml.sax.SAXParseException: Content is not allowed in trailing section. at at at org.cybergarage.xml.parser.XercesParser.parse( ... 10 more

    Users with the same issue

    1 times, last one,
    Andreas Häber
    19 times, last one,
    1 times, last one,
    Unknown visitor1 times, last one,
    4 times, last one,
    11 more bugmates