首页
学习
活动
专区
圈层
工具
发布
社区首页 >问答首页 >BitBucket服务器Maven错误:默认包“.”不允许导入包语法。

BitBucket服务器Maven错误:默认包“.”不允许导入包语法。
EN

Stack Overflow用户
提问于 2019-04-04 12:00:31
回答 2查看 525关注 0票数 1

我正在为BitBucket服务器开发一个插件。今天,在更改了一个依赖项的范围后,Maven实例开始抛出以下错误:

代码语言:javascript
复制
[ERROR] Manifest com.my-plugin:integrationPlugin:atlassian-plugin:0.1-DEV : The default package '.' is not permitted by the Import-Package syntax.
 This can be caused by compile errors in Eclipse because Eclipse creates
valid class files regardless of compile errors.
The following package(s) import from the default package null
[ERROR] Error(s) found in manifest configuration

在我恢复更改后,错误并没有消失。

我尝试过在其他StackOverflow帖子中描述的解决方案,但它们并没有帮助我,因为:

  • 我不使用Eclipse
  • 我在所有的类文件中声明了所有的包。
  • 捆绑工具已经修复了这个错误。

我从Maven调试输出中获得的清单是:

代码语言:javascript
复制
[DEBUG] Final Manifest:
#-----------------------------------------------------------------------
Manifest-Version: 1.0
Atlassian-Build-Date: 2019-04-04T11:44:27+0000
Atlassian-Plugin-Key: com.my-plugin.integrationPlugin
Bnd-LastModified: 1554378274635
Build-Jdk: 1.8.0_191
Built-By: egta136
Bundle-ClassPath: .,META-INF/lib/commons-logging-1.2.jar,META-INF/lib/pd
 fbox-2.0.14.jar,META-INF/lib/fontbox-2.0.14.jar,META-INF/lib/ij-1.52n.j
 ar
Bundle-Description: This is the com.my-plugin:integrationPlugin plu
 gin for Atlassian Bitbucket Server.
Bundle-DocURL: https://example.com
Bundle-ManifestVersion: 2
Bundle-Name: integrationPlugin
Bundle-SymbolicName: com.my-plugin.integrationPlugin
Bundle-Vendor: Example
Bundle-Version: 0.1.0.DEV
Created-By: Apache Maven Bundle Plugin
Export-Package: com.my-plugin.integrationPlugin.api;version="0.1.0"
Import-Package:
 com.apple.eawt;version=0;resolution:=optional,
 com.atlassian.bitbucket.auth;version=0;resolution:=optional,
 com.atlassian.bitbucket.commit;version=0;resolution:=optional,
 com.atlassian.bitbucket.project;version=0;resolution:=optional,
 com.atlassian.bitbucket.user;version=0;resolution:=optional,
 com.atlassian.plugin.spring.scanner.annotation.export;version=0;resolut
 ion:=optional,
 com.atlassian.plugin.spring.scanner.annotation.imports;version=0;resolu
 tion:=optional,
 com.atlassian.sal.api;version=0;resolution:=optional,
 com.atlassian.sal.api.pluginsettings;version=0;resolution:=optional,
 com.atlassian.soy.renderer;version=0;resolution:=optional,
 com.dizainsync.ddm.integrationPlugin.api;version=0;resolution:=optional
 ,
 com.fasterxml.jackson.databind;version=0;resolution:=optional,
 com.google.common.collect;version=0;resolution:=optional,
 javax.crypto;version=0;resolution:=optional,
 javax.crypto.spec;version=0;resolution:=optional,
 javax.imageio;version=0;resolution:=optional,
 javax.imageio.metadata;version=0;resolution:=optional,
 javax.imageio.plugins.jpeg;version=0;resolution:=optional,
 javax.imageio.stream;version=0;resolution:=optional,
 javax.inject;version=0;resolution:=optional,
 javax.script;version=0;resolution:=optional,
 javax.servlet;version=0;resolution:=optional,
 javax.servlet.http;version=0;resolution:=optional,
 javax.swing;version=0;resolution:=optional,
 javax.swing.event;version=0;resolution:=optional,
 javax.swing.table;version=0;resolution:=optional,
 javax.swing.text;version=0;resolution:=optional,
 javax.swing.text.html;version=0;resolution:=optional,
 javax.swing.tree;version=0;resolution:=optional,
 javax.tools;version=0;resolution:=optional,
 javax.xml.namespace;version=0;resolution:=optional,
 javax.xml.parsers;version=0;resolution:=optional,
 javax.xml.xpath;version=0;resolution:=optional,
 org.apache.avalon.framework.logger;version=0;resolution:=optional,
 org.apache.commons.fileupload;version=0;resolution:=optional,
 org.apache.commons.fileupload.disk;version=0;resolution:=optional,
 org.apache.commons.fileupload.servlet;version=0;resolution:=optional,
 org.apache.commons.io;version=0;resolution:=optional,
 org.apache.commons.lang3;version=0;resolution:=optional,
 org.apache.log;version=0;resolution:=optional,
 org.apache.log4j;version=0;resolution:=optional,
 org.bouncycastle.asn1;version=0;resolution:=optional,
 org.bouncycastle.asn1.cms;version=0;resolution:=optional,
 org.bouncycastle.asn1.pkcs;version=0;resolution:=optional,
 org.bouncycastle.asn1.x500;version=0;resolution:=optional,
 org.bouncycastle.asn1.x509;version=0;resolution:=optional,
 org.bouncycastle.cert;version=0;resolution:=optional,
 org.bouncycastle.cms;version=0;resolution:=optional,
 org.bouncycastle.cms.jcajce;version=0;resolution:=optional,
 org.slf4j;version=0;resolution:=optional,
 org.w3c.dom;version=0;resolution:=optional,
 org.xml.sax;version=0;resolution:=optional,
 com.atlassian.plugin.osgi.bridge.external
Require-Capability: osgi.ee;filter:="(&(osgi.ee=JavaSE)(version=1.8))"
Spring-Context: *
Tool: Bnd-3.5.0.201709291849
#-----------------------------------------------------------------------

是什么导致了这一切?特别奇怪的是,将更改还原到pom.xml并没有消除错误。

EN

回答 2

Stack Overflow用户

回答已采纳

发布于 2019-04-04 14:20:02

错误是由我所拥有的ImageJ依赖引起的。显然,他们的一些类使用默认的包,这个包不能很好地处理maven。删除依赖项修复了问题。

票数 1
EN

Stack Overflow用户

发布于 2019-10-08 11:35:55

我也有过类似的问题。要找出哪些依赖项可能会阻止OSGi打包工作,请查看Classes found in the wrong directory: {META-INF/versions/9/module-info.class=module-info}之类的错误消息。

使用jcfind来识别其起源,例如:

代码语言:javascript
复制
./target/classes/META-INF/lib/classgraph-4.8.43.jar META-INF/versions/9/module-info.class

我是联系家长POM供应商,以获得这一解决办法。

票数 0
EN
页面原文内容由Stack Overflow提供。腾讯云小微IT领域专用引擎提供翻译支持
原文链接:

https://stackoverflow.com/questions/55515518

复制
相关文章

相似问题

领券
问题归档专栏文章快讯文章归档关键词归档开发者手册归档开发者手册 Section 归档