cancel
Showing results for 
Search instead for 
Did you mean: 

Problem with demo.start

dc411
Champ in-the-making
Champ in-the-making
Brand new Activiti-er here. I'm attempting to install 5.3 on a fresh Debian 6.0 machine. I have both Ant 1.8 and JDK 6u24 installed. I've unzipped the folder into the /opt directory and am trying to start the demo. I keep getting the following error:

BUILD FAILED
/opt/activiti-5.3/setup/build.xml:407: couldn't find executable for script /opt/activiti-5.3/apps/apache-tomcat-6.0.32/bin/startup

Any help would be appreciated.

Thanks!
5 REPLIES 5

frederikherema1
Star Contributor
Star Contributor
Are you the demo running as root? Or does the user executing the demo-setup have right to chmod on the files? Normally, the startup.sh should be made executable by the setup procedure…

2sharma_vishal
Champ in-the-making
Champ in-the-making
I have also faced this problem during the installation, Its because of the proxy.When we start the ant demo.start it tries to download the tomcat in the downloads folder but
with the activiti5.2 the repository is not available because it looks for the older version of apache but if you are working with 5.3 than just fix the proxy settings in the build.xml. I hope it will work…..good luck!!

Vishal Sharma
Heidelberg University of Applied Sciences

sunjay
Champ in-the-making
Champ in-the-making
Hi there,

i had the same problem.
(had installed ant and activiti. i didn't install tomcat !)

After reading the 'long version' i hit on an idea :

ant -p
showed me the main targets.

i found tomcat.install as a good choice for a target, especially because i couldn't find the /apache-tomcat-6.0.32/bin/ folder either.
so i typed :

ant tomcat.install

after that i could start the demo

maby this one helps others too Smiley Very Happy

cheers

shabby
Champ in-the-making
Champ in-the-making
Hi I`ve the same problem…
How did I have to change my build.xml?

k-minor
Champ in-the-making
Champ in-the-making
Sunjay's "ant tomcat.install" tip got me past this issue.   And onto the next of three issues so far, probably all related to my company's firewall and proxy.