java.io.IOException

Not a valid class file (no CAFEBABE header)

Samebug tips0

There are no available Samebug tips for this exception. If you know how to solve this issue, help other users by writing a short tip.

Don't give up yet. Paste your full stack trace to get a solution.

Solutions on the web17489

  • via Google Groups by Ben Szekely, 6 months ago
    Not a valid class file (no CAFEBABE header)
  • via Google Groups by leonhard...@googlemail.com, 6 months ago
    Not a valid class file (no CAFEBABE header)
  • via Stack Overflow by Unknown author, 1 year ago
    Invalid header signature; read 0x04090000002DA5DB, expected 0xE11AB1A1E011CFD0 - Your file appears not to be a valid OLE2 document
  • Stack trace

    • java.io.IOException: Not a valid class file (no CAFEBABE header) at aQute.lib.osgi.Clazz.parseClassFile(Clazz.java:77) at aQute.lib.osgi.Clazz.<init>(Clazz.java:65) at aQute.lib.osgi.Processor.analyzeJar(Processor.java:159) at aQute.lib.osgi.Processor.analyzeBundleClasspath(Processor.java:97) at aQute.lib.osgi.Verifier.verify(Verifier.java:354) at aQute.lib.osgi.Builder.doVerify(Builder.java:216) at aQute.lib.osgi.Builder.build(Builder.java:52) at org.apache.felix.bundleplugin.BundlePlugin.buildOSGiBundle(BundlePlugin.java:391) at org.apache.felix.bundleplugin.BundlePlugin.execute(BundlePlugin.java:273) at org.apache.felix.bundleplugin.BundlePlugin.execute(BundlePlugin.java:227) at org.apache.felix.bundleplugin.BundlePlugin.execute(BundlePlugin.java:218) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:453) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:559) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:500) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:479) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:331) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:292) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) at org.apache.maven.cli.MavenCli.main(MavenCli.java:301) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375)[ERROR]

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    You’re the first here who have seen this exception.