我正在使用插件org.eclipse.virgo.bundlor从一个模板创建OSGi清单文件。当我使用lambdas时,插件不能正常工作。你能建议对我的maven文件做个修改,或者用一种可以让我使用lambdas的包的替代方法吗?
这是我的pom.xml
<?xml version="1.0" encoding="UTF-8"?>
<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd">
<modelVersion>4.0.0</modelVersion>
<groupId>lamba</groupId>
<artifactId>lamba</artifactId>
<version>0.0.1-SNAPSHOT</version>
<name>lamba</name>
<properties>
<java-source-version>1.8</java-source-version>
<java-target-version>1.8</java-target-version>
</properties>
<build>
<finalName>${project.artifactId}</finalName>
<plugins>
<plugin>
<groupId>org.eclipse.virgo.bundlor</groupId>
<artifactId>org.eclipse.virgo.bundlor.maven</artifactId>
<version>1.1.2.RELEASE</version>
<dependencies>
<dependency>
<groupId>org.eclipse.virgo.bundlor</groupId>
<artifactId>org.eclipse.virgo.bundlor</artifactId>
<version>1.1.2.RELEASE</version>
</dependency>
<dependency>
<groupId>org.eclipse.virgo.bundlor</groupId>
<artifactId>org.eclipse.virgo.bundlor.blint</artifactId>
<version>1.1.2.RELEASE</version>
</dependency>
</dependencies>
<executions>
<execution>
<id>${project.artifactId}-bundle-manifest</id>
<phase>prepare-package</phase>
<goals>
<goal>bundlor</goal>
</goals>
</execution>
</executions>
</plugin>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-compiler-plugin</artifactId>
<version>3.1</version>
<configuration>
<source>${java-source-version}</source>
<target>${java-target-version}</target>
<skip>false</skip>
</configuration>
</plugin>
</plugins>
</build>
</project>造成这个问题的代码很简单:
package lamba.internal;
import java.util.function.Supplier;
/**
*
*/
public class HiImpl {
public Supplier<String> p=()->"hi";
}我的错误是:
[INFO] --- org.eclipse.virgo.bundlor.maven:1.1.2.RELEASE:bundlor (lamba-bundle-manifest) @ lamba ---
java.lang.ArrayIndexOutOfBoundsException: 28712
at org.objectweb.asm.ClassReader.<init>(Unknown Source)
at org.objectweb.asm.ClassReader.<init>(Unknown Source)
at org.objectweb.asm.ClassReader.<init>(Unknown Source)
at org.eclipse.virgo.bundlor.support.asm.AsmTypeArtifactAnalyzer.analyse(AsmTypeArtifactAnalyzer.java:37)
at org.eclipse.virgo.bundlor.support.StandardManifestGenerator.analyzeEntry(StandardManifestGenerator.java:114)
at org.eclipse.virgo.bundlor.support.StandardManifestGenerator.analyzeEntries(StandardManifestGenerator.java:99)
at org.eclipse.virgo.bundlor.support.StandardManifestGenerator.generate(StandardManifestGenerator.java:64)
at org.eclipse.virgo.bundlor.maven.plugin.internal.MavenBundlorExecutor.execute(MavenBundlorExecutor.java:68)
at org.eclipse.virgo.bundlor.maven.plugin.BundlorMojo.execute(BundlorMojo.java:222)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:133)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:108)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:76)
at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:116)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:361)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:155)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:584)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:213)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:157)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:483)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
Manifest written to '/Users/me/proj/lamba/target/classes/META-INF/MANIFEST.MF'Update,我试着使用ASM库的更新版本,但这不起作用:
<?xml version="1.0" encoding="UTF-8"?>
<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd">
<modelVersion>4.0.0</modelVersion>
<groupId>lamba</groupId>
<artifactId>lamba</artifactId>
<version>0.0.1-SNAPSHOT</version>
<name>lamba</name>
<properties>
<java-source-version>1.8</java-source-version>
<java-target-version>1.8</java-target-version>
</properties>
<build>
<finalName>${project.artifactId}</finalName>
<plugins>
<plugin>
<groupId>org.eclipse.virgo.bundlor</groupId>
<artifactId>org.eclipse.virgo.bundlor.maven</artifactId>
<version>1.1.2.RELEASE</version>
<dependencies>
<dependency>
<groupId>org.eclipse.virgo.bundlor</groupId>
<artifactId>org.eclipse.virgo.bundlor</artifactId>
<version>1.1.2.RELEASE</version>
<exclusions>
<exclusion>
<groupId>org.objectweb.asm</groupId>
<artifactId>com.springsource.org.objectweb.asm</artifactId>
</exclusion>
<exclusion>
<groupId>org.objectweb.asm</groupId>
<artifactId>com.springsource.org.objectweb.asm.tree</artifactId>
</exclusion>
<exclusion>
<groupId>org.objectweb.asm</groupId>
<artifactId>com.springsource.org.objectweb.asm.commons</artifactId>
</exclusion>
</exclusions>
</dependency>
<dependency>
<groupId>org.eclipse.virgo.bundlor</groupId>
<artifactId>org.eclipse.virgo.bundlor.blint</artifactId>
<version>1.1.2.RELEASE</version>
<exclusions>
<exclusion>
<groupId>org.objectweb.asm</groupId>
<artifactId>com.springsource.org.objectweb.asm</artifactId>
</exclusion>
<exclusion>
<groupId>org.objectweb.asm</groupId>
<artifactId>com.springsource.org.objectweb.asm.tree</artifactId>
</exclusion>
<exclusion>
<groupId>org.objectweb.asm</groupId>
<artifactId>com.springsource.org.objectweb.asm.commons</artifactId>
</exclusion>
</exclusions>
</dependency>
<dependency>
<groupId>org.objectweb.asm</groupId>
<artifactId>com.springsource.org.objectweb.asm.commons</artifactId>
<version>3.2.0</version>
<scope>compile</scope>
</dependency>
</dependencies>
<executions>
<execution>
<id>${project.artifactId}-bundle-manifest</id>
<phase>prepare-package</phase>
<goals>
<goal>bundlor</goal>
</goals>
</execution>
</executions>
</plugin>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-compiler-plugin</artifactId>
<version>3.1</version>
<configuration>
<source>${java-source-version}</source>
<target>${java-target-version}</target>
<skip>false</skip>
</configuration>
</plugin>
</plugins>
</build>
</project>发布于 2015-08-14 16:23:48
据我所知,包插件已不再更新,因此不太可能对Java 8字节码进行增强。
基于一个名为bnd的工具,很多OSGi项目都使用了bnd,有两种主要的选择。
bnd项目托管了一个名为bnd-maven-plugin的插件。有一个使用这里的示例项目,它可以很容易地添加到pom中,如下所示:
<plugin>
<groupId>biz.aQute.bnd</groupId>
<artifactId>bnd-maven-plugin</artifactId>
<version>2.4.1</version>
<executions>
<execution>
<goals>
<goal>bnd-process</goal>
</goals>
</execution>
</executions>
</plugin>请注意,为了获取bnd生成的清单,您还需要告诉maven-jar-plugin将其取出。通常,您会将类似的内容添加到父pom中:
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-jar-plugin</artifactId>
<configuration>
<useDefaultManifestFile>true</useDefaultManifestFile>
</configuration>
</plugin> bnd-maven-plugin从名为bnd.bnd的文件中提取配置,该文件的文档是可用的这里。
另一个基于bnd的工具叫做maven-bundle-plugin,由Apache托管。文档是可见的这里,并告诉您如何配置pom。
<plugin>
<groupId>org.apache.felix</groupId>
<artifactId>maven-bundle-plugin</artifactId>
<extensions>true</extensions>
<configuration>
<instructions>
<Export-Package>org.foo.myproject.api</Export-Package>
<Private-Package>org.foo.myproject.*</Private-Package>
<Bundle-Activator>org.foo.myproject.impl1.Activator</Bundle-Activator>
</instructions>
</configuration>
</plugin>如您所见,maven-bundle-plugin要求您要么将模块的打包类型更改为bundle,要么扩展默认的生命周期,以便它能够正确地打包东西。因此,它并不总是能很好地处理其他基于maven的工具。不过,它被广泛使用。
我个人的偏好是bnd-maven-plugin (我是bnd/bndtools提交者),但两者都可能适合您。
发布于 2015-08-14 09:50:06
问题是邦德乐的版本使用了一个旧版本的ASM,它不理解Java 8类文件。所以你要么需要更新到邦德,要么改变使用另一个工具。bnd已经被更新,以支持Java8类文件。
https://stackoverflow.com/questions/31997681
复制相似问题