Solve Maven + jbpm errors

Download the jBPM-4.3 running package, jpdl is also 4.3 version, according to the doc to complete the installation of GPD plug-in, examples is also perfect run, but when you add Maven, the repository of JBoss is also added.CodeWhen a copy is made, the following message is displayed:

Error: no start activity in process [line = 3 column = 61]

At org. jbpm. PVM. Internal. xml. problemlist. getjbpmexception (problemlist. Java: 168)

At org. jbpm. PVM. Internal. xml. problemlist. getjbpmexception (problemlist. Java: 141)

At org. jbpm. PVM. Internal. repository. deployermanager. Deploy (deployermanager. Java: 50)

At org. jbpm. PVM. Internal. repository. repositorysessionimpl. Deploy (repositorysessionimpl. Java: 56)

At org.jbpm.pvm.internal.developer.deploycmd.exe cute (deploycmd. Java: 47)

At org.jbpm.pvm.internal.developer.deploycmd.exe cute (deploycmd. Java: 33)

At org.jbpm.pvm.internal.svc.defacommandcommandservice.exe cute (defacommandcommandservice. Java: 42)

At org.jbpm.pvm.internal.tx.standardtransactioninterceptor.exe cute (standardtransactioninterceptor. Java: 54)

At org.jbpm.pvm.internal.svc.environmentinterceptor.exe cute (environmentinterceptor. Java: 46)

At org.jbpm.pvm.internal.svc.retryinterceptor.exe cute (retryinterceptor. Java: 55)

At org. jbpm. PVM. Internal. repository. deploymentimpl. Deploy (deploymentimpl. Java: 89)

At testcase. Setup (testcase. Java: 16)

At JUnit. Framework. testcase. runbare (testcase. Java: 128)

At JUnit. Framework. testresult $1. Protect (testresult. Java: 106)

At JUnit. Framework. testresult. runprotected (testresult. Java: 124)

At JUnit. Framework. testresult. Run (testresult. Java: 109)

At JUnit. Framework. testcase. Run (testcase. Java: 120)

At JUnit. Framework. testsuite. runtest (testsuite. Java: 230)

At JUnit. Framework. testsuite. Run (testsuite. Java: 225)

At sun. Reflect. nativemethodaccessorimpl. invoke0 (native method)

At sun. Reflect. nativemethodaccessorimpl. Invoke (nativemethodaccessorimpl. Java: 39)

At sun. Reflect. delegatingmethodaccessorimpl. Invoke (delegatingmethodaccessorimpl. Java: 25)

At java. Lang. Reflect. method. Invoke (method. Java: 597)

At org.apache.maven.surefire.junit.junittestset.exe cute (junittestset. Java: 213)

At org.apache.maven.surefire.suite.?actdirectorytestsuite.exe cutetestset (abstractdirectorytestsuite. Java: 140)

At org.apache.maven.surefire.suite.w.actdirectorytestsuite.exe cute (abstractdirectorytestsuite. Java: 127)

At org. Apache. Maven. surefire. surefire. Run (surefire. Java: 177)

At sun. Reflect. nativemethodaccessorimpl. invoke0 (native method)

At sun. Reflect. nativemethodaccessorimpl. Invoke (nativemethodaccessorimpl. Java: 39)

At sun. Reflect. delegatingmethodaccessorimpl. Invoke (delegatingmethodaccessorimpl. Java: 25)

At java. Lang. Reflect. method. Invoke (method. Java: 597)

At org. Apache. Maven. surefire. booter. surefirebooter. runsuitesinprocess (surefirebooter. Java: 345)

At org. Apache. Maven. surefire. booter. surefirebooter. Main (surefirebooter. Java: 1009)

The reason is this, JBoss's repossitories (address is here: http://repository.jboss.com/maven2) on jbpm Max version is 4.1, while jpdl. the XML version is 4.3. If you look at the namespace, this error is always prompted during Maven development. There are two solutions:

Method 1:

Modify the namespace in the jpdl. xml file, that is, the string behind xmlns, and change the version number to 4.0. Note that it is 4.0, not 4.1. Before the modification, it looks like this:

After modification, it looks like this:

Run test again. This is another issue caused by inconsistent versions. The Open Source world is just a habit! This solution is only a temporary solution, but it is not good. Let's look at solution 2 once and for all.

Solution 2:

Modify the POM file, change all 4.1 to 4.3, replace it directly, and then test it to download the dependency package. The test is normal.

Now, why is there 4.3in http://repository.jboss.com/maven2in the official JBoss repository? Look here:

Let's take a look at the index I just updated:

I suspect this is the case. The file name starting with Maven logging. * is missing somewhere.