08-21-2010 04:26 PM
D:\WhiteRoom\activiti\activiti-5.0.alpha4\setup>antI dont know what is wrong or missing, but according to the build.xml configuration file
Buildfile: D:\WhiteRoom\activiti\activiti-5.0.alpha4\setup\build.xml
[echo] Activiti home = ..
[echo] Activiti version = 5.0.alpha4
h2.install:
[mkdir] Created dir: D:\WhiteRoom\activiti\activiti-5.0.alpha4\apps\h2
[copy] Copying 5 files to D:\WhiteRoom\activiti\activiti-5.0.alpha4\apps\h2
internal.classpath.libs:
internal.taskdef.launch:
h2.start:
[launch] launching cmd 'D:\WhiteRoom\activiti\activiti-5.0.alpha4\apps\h2\h2.start.bat '
in dir 'D:\WhiteRoom\activiti\activiti-5.0.alpha4\apps\h2'
[launch] waiting for launch completion msg 'TCP server running on'…
[launch] TCP server running on tcp://192.168.1.34:9092 (others can connect)
db.create:
[sql] Executing resource: org/activiti/db/create/activiti.mysql.create.sql
[sql] 29 of 29 SQL statements executed successfully
tomcat.install:
[echo] Activiti home = ..
[echo] Activiti version = 5.0.alpha4
internal.download.tomcat:
[unzip] Expanding: D:\WareHouse\apache\tomcat\6.0.29\apache-tomcat-6.0.29.zip
into D:\WhiteRoom\activiti\activiti-5.0.alpha4\apps
[echo] Activiti home = ..
[echo] Activiti version = 5.0.alpha4
tomcat.copy.users:
[echo] Activiti home = ..
[echo] Activiti version = 5.0.alpha4
tomcat.enable.debug:
cfg.create:
[mkdir] Created dir: D:\WhiteRoom\activiti\activiti-5.0.alpha4\setup\build\activiti-cfg
[copy] Copying 1 file to D:\WhiteRoom\activiti\activiti-5.0.alpha4\setup\build\activiti-cfg
[jar] Building jar: D:\WhiteRoom\activiti\activiti-5.0.alpha4\setup\build\activiti-cfg.jar
deploy.activiti.engine.into.tomcat:
[copy] Warning: activiti-cfg.jar modified in the future.
[copy] Copying 6 files to D:\WhiteRoom\activiti\activiti-5.0.alpha4\apps\apache-tomcat-6.0.29\lib
[delete] Deleting: D:\WhiteRoom\activiti\activiti-5.0.alpha4\apps\apache-tomcat-6.0.29\lib\el-api.jar
db.demo.data:
[sql] Executing resource: D:\WhiteRoom\activiti\activiti-5.0.alpha4\setup\files\demo\mysql.data.sql
[sql] 23 of 23 SQL statements executed successfully
[zip] Building zip: D:\WhiteRoom\activiti\activiti-5.0.alpha4\setup\build\activiti-examples.bar
[deploy-bar] Initializing process engine default
[deploy-bar] 21/08/2010 02:44:15 PM org.activiti.ProcessEngines initProcessEnginFromResource
[deploy-bar] INFO: initializing process engine for resource
jar:file:/D:/WhiteRoom/activiti/activiti-5.0.alpha4/setup/build/activiti-cfg.jar!/activiti.properties
[deploy-bar] 21/08/2010 02:44:15 PM org.activiti.ProcessEngines initProcessEnginFromResource
[deploy-bar] INFO: Exception while initializing process engine :
Error setting driver on UnpooledDataSource. Cause:
java.lang.ClassNotFoundException: com.mysql.jdbc.Driver
BUILD FAILED
D:\WhiteRoom\activiti\activiti-5.0.alpha4\setup\build.xml:195: org.activiti.ActivitiException:
Could not find a process engine with name 'default'
at org.activiti.impl.ant.DeployBarTask.execute(DeployBarTask.java:73)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291)
at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
at org.apache.tools.ant.Task.perform(Task.java:348)
at org.apache.tools.ant.Target.execute(Target.java:390)
at org.apache.tools.ant.Target.performTasks(Target.java:411)
at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1397)
at org.apache.tools.ant.Project.executeTarget(Project.java:1366)
at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
at org.apache.tools.ant.Project.executeTargets(Project.java:1249)
at org.apache.tools.ant.Main.runBuild(Main.java:801)
at org.apache.tools.ant.Main.startAnt(Main.java:218)
at org.apache.tools.ant.launch.Launcher.run(Launcher.java:280)
at org.apache.tools.ant.launch.Launcher.main(Launcher.java:109)
Total time: 10 seconds
D:\WhiteRoom\activiti\activiti-5.0.alpha4\setup>
<target name="internal.classpath.libs">and the line 195 mentioned in the error stacktrace is this
<path id="classpath.libs">
<fileset dir="${activiti.home}/lib">
<include name="*.jar" />
</fileset>
</path>
</target>
<taskdef name="deploy-bar" classname="org.activiti.impl.ant.DeployBarTask">Not very useful in try to dectect the error related with the MySql's driver
<classpath>
<pathelement path="files/demo"/>
<fileset dir="build">
<include name="activiti-cfg.jar"/>
</fileset>
<fileset dir="${activiti.home}/lib">
<include name="activiti-engine-${activiti.version}.jar"/>
<include name="mybatis-*.jar"/>
<include name="h2-*.jar"/>
<include name="freemarker-*.jar" />
<include name="juel*.jar" />
</fileset>
</classpath>
</taskdef>
<deploy-bar file="${activiti.home}/setup/build/activiti-examples.bar" />
</target>
08-21-2010 10:15 PM
<taskdef name="deploy-bar" classname="org.activiti.impl.ant.DeployBarTask">
<classpath>
<pathelement path="files/demo"/>
<fileset dir="build">
<include name="activiti-cfg.jar"/>
</fileset>
<fileset dir="${activiti.home}/lib">
<include name="activiti-engine-${activiti.version}.jar"/>
<include name="mybatis-*.jar"/>
<include name="h2-*.jar"/>
<include name="mysql-*.jar"/>
<include name="freemarker-*.jar" />
<include name="juel*.jar" />
</fileset>
</classpath>
</taskdef>
<deploy-bar file="${activiti.home}/setup/build/activiti-examples.bar" />
</target>
08-22-2010 01:26 PM
the exception is thrown while executing the deploy-bar task, I would guess you have to add the mysql-connector-*.jar to your fileset.Yes I added <include name="mysql-*.jar"/> in such taskdef and all goes well, thanks a lot!!, and to be honest I thought the solution that you told me, but I didn't because I thought that such build.xml was totally already tested to work with both DB
As you use mysql you can comment the h2 related tasks and delete the <include name="h2-*.jar"/> from your taskdef.Is not necessary for a successful startup, I don't test yet the sample code
If you comment the h2 tasks dont forget to remove them from your build dependencies.Again Is not necessary for a successful startup, I don't test yet the sample code
08-23-2010 02:50 AM
08-23-2010 10:34 AM
08-24-2010 10:33 AM
08-24-2010 11:50 AM
10-24-2010 03:18 AM
10-25-2010 03:05 AM
Tags
Find what you came for
We want to make your experience in Hyland Connect as valuable as possible, so we put together some helpful links.