Hi,
I don't see that problem on Windows. It seems to be a bug in Felix
maven-bundle-plugin. There are similar issues found on Google, such as:
http://mail-archives.apache.org/mod_mbox/felix-dev/200809.mbox/%3c725237658.1221218564113.javamail.j...@brutus%3e.
Thanks,
Raymond
--------------------------------------------------
From: "Jean-Sebastien Delfino" <[email protected]>
Sent: Thursday, August 13, 2009 10:40 AM
To: <[email protected]>
Subject: [1.x] Error building java-1.5.1 branch
Building from java/sca or java/sca/modules throws the following error:
------------------------------------------------------------------------
[INFO] Building Apache Tuscany SCA Web JavaScript
[INFO] task-segment: [install]
[INFO] ------------------------------------------------------------------------
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:compile]
[INFO] Nothing to compile - all classes are up to date
[INFO] [bundle:manifest {execution: bundle-manifest}]
java.io.EOFException
at java.io.DataInputStream.readInt(DataInputStream.java:386)
at aQute.lib.osgi.Clazz.parseClassFile(Clazz.java:75)
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:77)
at
org.apache.felix.bundleplugin.PackageVersionAnalyzer.analyzeBundleClasspath(PackageVersionAnalyzer.java:44)
at aQute.lib.osgi.Analyzer.analyze(Analyzer.java:194)
at aQute.lib.osgi.Builder.analyze(Builder.java:95)
at aQute.lib.osgi.Analyzer.calcManifest(Analyzer.java:293)
at
org.apache.felix.bundleplugin.ManifestPlugin.getAnalyzer(ManifestPlugin.java:192)
at
org.apache.felix.bundleplugin.ManifestPlugin.getManifest(ManifestPlugin.java:112)
at
org.apache.felix.bundleplugin.ManifestPlugin.execute(ManifestPlugin.java:66)
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:451)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:478)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291)
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:287)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
at java.lang.reflect.Method.invoke(Method.java:599)
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)
Building the module individually works though.
After I build that module, building from java/sca/modules again just
throws the same error on the next module.
Anybody else seeing this? perhaps the build plugins used to package
bundles don't close handles or cleanup resources? Any idea?
I'm on Ubuntu 9.0.4, J2RE 1.6.0 IBM J9 2.4, Maven 2.0.9
--
Jean-Sebastien
