Maven 2 将非OSGI jar依赖项添加到Liferay 7 CE中基于maven的MVC portlet中
我已经为Liferay 7 CE创建了一个MVC Portlet,它具有相应的maven原型(如所述)。我在项目的POM文件中添加了一些额外的非OSGI jar文件作为项目依赖项。当我在liferay portal server上部署该项目时,OSGI容器无法解析所创建模块的依赖关系,捆绑包仍处于安装阶段。我想以自动方式将非OSGI jar文件及其可传递依赖项添加到to包中。我该怎么办?本模块的内容如下: 项目结构: pom.xml:Maven 2 将非OSGI jar依赖项添加到Liferay 7 CE中基于maven的MVC portlet中,maven-2,liferay,osgi,osgi-bundle,liferay-7,Maven 2,Liferay,Osgi,Osgi Bundle,Liferay 7,我已经为Liferay 7 CE创建了一个MVC Portlet,它具有相应的maven原型(如所述)。我在项目的POM文件中添加了一些额外的非OSGI jar文件作为项目依赖项。当我在liferay portal server上部署该项目时,OSGI容器无法解析所创建模块的依赖关系,捆绑包仍处于安装阶段。我想以自动方式将非OSGI jar文件及其可传递依赖项添加到to包中。我该怎么办?本模块的内容如下: 项目结构: pom.xml: <?xml version="1.0" en
<?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/xsd/maven-4.0.0.xsd"
>
<modelVersion>4.0.0</modelVersion>
<groupId>org.ranginkaman</groupId>
<artifactId>second-maven-portlet</artifactId>
<version>1.0.0</version>
<packaging>jar</packaging>
<properties>
<project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
</properties>
<dependencies>
<dependency>
<groupId>com.liferay.portal</groupId>
<artifactId>com.liferay.portal.kernel</artifactId>
<version>2.0.0</version>
<scope>provided</scope>
</dependency>
<dependency>
<groupId>com.liferay.portal</groupId>
<artifactId>com.liferay.util.taglib</artifactId>
<version>2.0.0</version>
<scope>provided</scope>
</dependency>
<dependency>
<groupId>javax.portlet</groupId>
<artifactId>portlet-api</artifactId>
<version>2.0</version>
<scope>provided</scope>
</dependency>
<dependency>
<groupId>javax.servlet</groupId>
<artifactId>javax.servlet-api</artifactId>
<version>3.0.1</version>
<scope>provided</scope>
</dependency>
<dependency>
<groupId>jstl</groupId>
<artifactId>jstl</artifactId>
<version>1.2</version>
<scope>provided</scope>
</dependency>
<dependency>
<groupId>org.osgi</groupId>
<artifactId>org.osgi.compendium</artifactId>
<version>5.0.0</version>
<scope>provided</scope>
</dependency>
<!-- https://mvnrepository.com/artifact/com.vividsolutions/jts -->
<dependency>
<groupId>com.vividsolutions</groupId>
<artifactId>jts</artifactId>
<version>1.13</version>
</dependency>
</dependencies>
<build>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-compiler-plugin</artifactId>
<version>3.1</version>
<configuration>
<source>1.8</source>
<target>1.8</target>
</configuration>
</plugin>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-jar-plugin</artifactId>
<version>2.6</version>
<configuration>
<archive>
<manifestFile>${project.build.outputDirectory}/META-INF/MANIFEST.MF</manifestFile>
</archive>
<excludes>
<exclude>**/META-INF/resources/**/.sass-cache/</exclude>
</excludes>
</configuration>
</plugin>
<plugin>
<groupId>biz.aQute.bnd</groupId>
<artifactId>bnd-maven-plugin</artifactId>
<version>3.2.0</version>
<executions>
<execution>
<id>default-bnd-process</id>
<goals>
<goal>bnd-process</goal>
</goals>
</execution>
</executions>
<dependencies>
<dependency>
<groupId>biz.aQute.bnd</groupId>
<artifactId>biz.aQute.bndlib</artifactId>
<version>3.2.0</version>
</dependency>
<dependency>
<groupId>com.liferay</groupId>
<artifactId>com.liferay.ant.bnd</artifactId>
<version>2.0.28</version>
</dependency>
</dependencies>
</plugin>
<plugin>
<groupId>com.liferay</groupId>
<artifactId>com.liferay.css.builder</artifactId>
<version>1.0.20</version>
<executions>
<execution>
<id>default-build-css</id>
<phase>generate-sources</phase>
<goals>
<goal>build-css</goal>
</goals>
</execution>
</executions>
<configuration>
<portalCommonPath>/</portalCommonPath>
<docrootDirName>src/main/resources</docrootDirName>
</configuration>
</plugin>
</plugins>
</build>
</project>
build.gradle:
buildscript {
dependencies {
classpath group: "com.liferay", name: "com.liferay.gradle.plugins", version: "3.0.23"
}
repositories {
mavenLocal()
maven {
url "https://cdn.lfrs.sl/repository.liferay.com/nexus/content/groups/public"
}
}
}
apply plugin: "com.liferay.plugin"
dependencies {
compileOnly group: "com.liferay.portal", name: "com.liferay.portal.kernel", version: "2.0.0"
compileOnly group: "com.liferay.portal", name: "com.liferay.util.taglib", version: "2.0.0"
compileOnly group: "javax.portlet", name: "portlet-api", version: "2.0"
compileOnly group: "javax.servlet", name: "javax.servlet-api", version: "3.0.1"
compileOnly group: "jstl", name: "jstl", version: "1.2"
compileOnly group: "org.osgi", name: "org.osgi.compendium", version: "5.0.0"
}
repositories {
mavenLocal()
maven {
url "https://cdn.lfrs.sl/repository.liferay.com/nexus/content/groups/public"
}
}
SecondMavenPortletPortlet.java:
package org.ranginkaman.portlet;
import com.liferay.portal.kernel.portlet.bridges.mvc.MVCPortlet;
import com.vividsolutions.jts.geom.Coordinate;
import com.vividsolutions.jts.geom.GeometryFactory;
import com.vividsolutions.jts.geom.Point;
import java.io.IOException;
import javax.portlet.Portlet;
import javax.portlet.PortletException;
import javax.portlet.RenderRequest;
import javax.portlet.RenderResponse;
import org.osgi.service.component.annotations.Component;
@Component(
immediate = true,
property = {
"com.liferay.portlet.display-category=category.sample",
"com.liferay.portlet.instanceable=true",
"javax.portlet.display-name=second-maven-portlet Portlet",
"javax.portlet.init-param.template-path=/",
"javax.portlet.init-param.view-template=/view.jsp",
"javax.portlet.resource-bundle=content.Language",
"javax.portlet.security-role-ref=power-user,user"
},
service = Portlet.class
)
public class SecondMavenPortletPortlet extends MVCPortlet {
@Override
public void doView(RenderRequest renderRequest, RenderResponse renderResponse)
throws IOException, PortletException {
GeometryFactory geometryFactory = new GeometryFactory();
Point point = geometryFactory.createPoint(new Coordinate(1.0, 2.0));
System.out.println(point);
super.doView(renderRequest, renderResponse);
}
}
如果com.livitSolutions.jts未准备好OSGi,您可以通过或SpringRoo将其包装起来,这里是Liferay社区博客,用于添加对OSGi模块的依赖关系:
看看这些选项是否符合您的要求。你应该选择这个博客中提到的第三个或第四个选项。这在我的情况下是有效的。在我们的一个项目中,我们也遇到了类似的问题。我注意到最后一个答案是从1月15日开始的,我认为最好在Liferay的博客文章中加入一个有用的回复。这让我们意识到,我们必须从博客中选择选项3或4,如前一个答案所述 因此,这实际上是一个常见的误解——使用依赖关系管理器在gradle中构建与没有类似依赖关系管理器的OSGi运行时环境之间存在差异 OSGi故意不下载依赖项,特别是可传递依赖项,因为这会导致环境不稳定 编译代码时,构建过程将包含可传递的依赖项,但BND不是编译器,它只是构建jar文件并包含您告诉它的内容 所以,是的,在正常情况下,您必须自己包含所有依赖项和可传递依赖项。这就是说,一些项目在其可传递依赖项中不使用“可选”标记,因此OSGi将其视为必须使用的标记。您必须在BND文件中添加classpath声明,以强制排除那些您确实不想要的包 这绝对是一个皮塔,但这样做是有原因的。OSGi环境是您的运行时环境,您希望主动管理并了解它。作为管理员,您希望了解您的模块正在使用什么,并适当地管理部署。从管理的角度来看,您不希望环境自己下载东西(通常情况下,这在生产环境中是不可能的)
谢谢,我读了那篇文章。但我想将Maven依赖项及其可传递依赖项自动添加到最终jar文件包的Manifest.MF中。你有什么建议吗?对不起,我现在还不知道。如果我遇到任何与你的要求有关的事情,我会告诉你的。
package org.ranginkaman.portlet;
import com.liferay.portal.kernel.portlet.bridges.mvc.MVCPortlet;
import com.vividsolutions.jts.geom.Coordinate;
import com.vividsolutions.jts.geom.GeometryFactory;
import com.vividsolutions.jts.geom.Point;
import java.io.IOException;
import javax.portlet.Portlet;
import javax.portlet.PortletException;
import javax.portlet.RenderRequest;
import javax.portlet.RenderResponse;
import org.osgi.service.component.annotations.Component;
@Component(
immediate = true,
property = {
"com.liferay.portlet.display-category=category.sample",
"com.liferay.portlet.instanceable=true",
"javax.portlet.display-name=second-maven-portlet Portlet",
"javax.portlet.init-param.template-path=/",
"javax.portlet.init-param.view-template=/view.jsp",
"javax.portlet.resource-bundle=content.Language",
"javax.portlet.security-role-ref=power-user,user"
},
service = Portlet.class
)
public class SecondMavenPortletPortlet extends MVCPortlet {
@Override
public void doView(RenderRequest renderRequest, RenderResponse renderResponse)
throws IOException, PortletException {
GeometryFactory geometryFactory = new GeometryFactory();
Point point = geometryFactory.createPoint(new Coordinate(1.0, 2.0));
System.out.println(point);
super.doView(renderRequest, renderResponse);
}
}