1 Reply Latest reply on May 10, 2007 8:28 AM by Edward Staub

    Docbook-Support error even after setting System Path

    Meghana Joglekar Novice

      Hello,

      I have checked out cvs source for jbpm.3 and running the root 'ant build' target. I get following error. I have searched the forum and accordingly made sure that cvs.exe is in my System Path.

      D:\jbpm-bpel-trunk\jbpm.3\jpdl\userguide\build.xml:17: Cannot find C:\Documents
      and Settings\mjoglekar/jbpm/repository/docbook-support/support.xml imported from
       D:\jbpm-bpel-trunk\jbpm.3\jpdl\userguide\build.xml
      


      But I still get the error on 'import' tag. Is there anything else I can try?

      Thanks,
      Meghana

      PS: My objective is to get JBPM engine and BPEL extension built locally and deploy them to already installed JBoss AS. Can someone tell me what are the artifacts I need from cvs and where should they go under JBoss 4.0.5?

        • 1. Re: Docbook-Support error even after setting System Path
          Edward Staub Expert

          Meghanai,

          The build goes out and CVS-fetches all of the libraries it uses into the "local repository", which is by default in $user_home/jbpm/repository.

          Because there are so many external jars to fetch, from so many other places, in my experience, this rarely is completely successful.

          Unfortunately, the checking mechanism for each "get" is to just see if a file exists that should have been gotten. Frequently the cvs get will fail half-way, resulting in half of a zip or jar file. (Yes, I have good connectivity!)

          One way or another, I recommend filling a local repository till it's all correct, and then don't ever fetch remotely again. Frankly, I can't imagine how the current process is good for anyone.

          Your particular problem is special... the cvs fetch for docbook support is just plain missing, I think. Go download docbook, figure out where it's supposed to go in your repository from build/build.properties (search for docbook, look at your repository to see how other directory trees are structured), and put it there yourself. Sorry, I don't remember the details of URL, etc.

          -Ed Staub