2016-06-28 25 views
1

使用Jbpm的從這裏6.4.0完整安裝程序:http://www.jbpm.org/download/download.html項目生成錯誤:未知包裝:kjar

1)開始演示:使用eclipse螞蟻start.demo

2),創建一個新的jBPM項目jBPM的操場6.3和選擇的翻譯項目

enter image description here

3)行家性質添加到項目

4)嘗試安裝/編譯就可以看到問題的選項卡上以下錯誤:

enter image description here

Project build error: Unknown packaging: kjar

問題是:什麼是kjar包裝?項目如何在演示環境中工作?

我的Eclipse是:

enter image description here

編輯:

我發現什麼是kjar,尤其是這個零件的官方文檔定義:

Version 6, on the other hand moves away from proprietary packages in favor of, well known and mature, Apache Maven based packaging - known as knowledge archives - kjar. Processes, rules etc (aka business assets) are now part of a simple jar file built and managed by Maven. Along the business assets, java classes and other file types are stored in the jar file too. Moreover, as any other maven artifact, kjar can have defined dependencies on other artifacts including other kjars. What makes the kjar special when compared with regular jars is a single descriptor file kept inside META-INF directory of the kjar - kmodule.xml. That descriptor allows to define:

  • knowledge bases and their properties

  • knowledge sessions and their properties

  • work item handlers

  • event listeners

By default, this descriptor is empty (just kmodule root element) and is considered as marker file. Whenever a runtime component (such as jbpm console) is about to process kjar it looks up kmodule.xml to build its runtime representation. In addition to kmodule.xml a deployment descriptor (that provides fine graind control over deployment) is available (since 6.1).

後讀這個不清楚如何建立這些kjar,以及爲什麼jbpm的官方在線示例包含kjar作爲包裝價值e

回答

0

¿您是否測試註釋該行是否有效? 只是註釋行8: 更改此:

<packaging>kjar</packaging> 

到這一點:

<!-- <packaging>kjar</packaging> --> 

林不知道,但我認爲有代碼和文檔之間的版本不匹配。我認爲默認包裝是jar,所以從配置中刪除第8行將起作用。

+0

我試過了,但我的問題更多的是瞭解什麼是kjar,爲什麼演示環境不工作 – Vokail