7 Replies Latest reply on May 9, 2006 10:02 AM by tom.baeyens

    new structure libraries

    tom.baeyens

      currently, you still have to mess with libraries yourself to get the new jbpm.3 build working.

      just to let you know that i'm working on it. i'm getting the new structure libraries checked into the jboss repository.

      also i'm documenting the build process and new structure as much as possible.

      should be done later today... i'll let you know here.

        • 1. Re: new structure libraries
          tom.baeyens

          all dependencies should be in the repository.

          the build-from-source instructions are in build/readme.html

          who can test those instructions and the build scripts on your local machine ?

          can you give it a try ?

          • 2. Re: new structure libraries
            svetzal

            The get.dependencies goal doesn't retrieve the following resources for me:

            http://repository.jboss.com/jboss/4.0.3/lib/jboss-common.jar
            http://repository.jboss.com/jboss/4.0.3/lib/jboss-jmx.jar
            http://repository.jboss.com/jboss/4.0.3/lib/jboss-system.jar
            http://repository.jboss.com/facelets/1.1.1/lib/facelets.jar

            Given you seem to be using the Maven2 repository structure, why not download these things to ~/.m2/ instead of ~/jbpm/ ? It would save folks having to download them who already have them locally...

            • 3. Re: new structure libraries
              tom.baeyens

              i think you didn't get the latest sources. jboss version should be 4.0.3.SP1 and the facelets jar should be called: jsf-facelets.jar

              we don't use a maven structure, but we probably could. it just takes me too much time to check out if all libs are present in the maven 2 jboss repository (http://repository.jboss.com/maven2/...).

              if all the libs are present there, it is just a matter of updating the properties.

              people can update the local repository location to ~/.m2 if they want to. if we would use the libs from the maven 2 repository, it would be worth while documenting the local repository location customization more explicitely.

              • 4. Re: new structure libraries
                svetzal

                Yeah, my bad, checked out fresh source tree and it gets dependencies just fine...

                • 5. Re: new structure libraries
                  koen.aers

                  In the meantime Tom fixed it ;-)

                  Cheers,
                  Koen

                  • 6. Re: new structure libraries
                    svetzal

                    I'm having the following build error:

                    [ant] Exiting /home/steve/Work/oss/jbpm.3/jpdl/jar/build.xml.
                    [mkdir] Created dir: /home/steve/Work/oss/jbpm.3/jpdl/db/target/ddl
                    [jbpmschema] using jbpm configuration jbpm/db2.jbpm.cfg.xml
                    [ant] Exiting /home/steve/Work/oss/jbpm.3/jpdl/db/build.xml.

                    BUILD FAILED
                    /home/steve/Work/oss/jbpm.3/build/build.xml:36: The following error occurred while executing this line:
                    java.lang.NoClassDefFoundError: org/apache/commons/logging/LogFactory

                    It's trying to run the jbpmschema tags in the jpdl/db/build.xml

                    I've tried to trace things through and as far as I can tell this library is in my repository.

                    I've traced the dependency back from schema.task.classpath, task.classpath.base, repository.external.dependency.libs, lib.commons.logging.path, lib.commons.logging.dir, lib.commons.logging.version (wow I hoped this build was going to get simpler) - at all points these variables should resolve to the proper place.

                    Is anyone else having this problem? Any clue as to what might be going wrong for me?

                    • 7. Re: new structure libraries
                      tom.baeyens

                      what version of ant are you using ?

                      what libs do you have in your ant-home/lib directory ?

                      sorry for the many properties :( good to know that you have a problem with it. so we know that investing time in simplification is a good idea.

                      it would be cool if ant had an easier way for debugging classpath problems. and echo of the classpath would already be a great help.