6 Replies Latest reply on Mar 25, 2008 2:22 AM by starksm64

    EJB client launcher

    pgier

      My maven thirdparty build is not finding ejb3.client.ClientLauncher when building the testsuite.


      /qa/services/hudson/hudson_workspace/workspace/JBoss-AS-5.0.x-TestSuite-sun15-Maven-Thirdparty/trunk/testsuite/src/main/org/jboss/test/ee5client/unit/AppClientUnitTestCase.java:28: package org.jboss.ejb3.client does not exist
      [javac] import org.jboss.ejb3.client.ClientLauncher;
      [javac] ^
      [javac] /qa/services/hudson/hudson_workspace/workspace/JBoss-AS-5.0.x-TestSuite-sun15-Maven-Thirdparty/trunk/testsuite/src/main/org/jboss/test/ee5client/unit/SimpleResourceEarUnitTestCase.java:31: package org.jboss.ejb3.client does not exist
      [javac] import org.jboss.ejb3.client.ClientLauncher;
      [javac] ^
      [javac]


      It looks like this class was moved from the ejb3 project into the app server. Am I just using an ejb3 snapshot that is too new?

      Any help on this appreciated :-)


        • 1. Re: EJB client launcher
          starksm64

          ClientLauncher is now in the jbossas ejb3 project jboss-appclient.jar and the jbossall-client.jar.

          • 2. Re: EJB client launcher
            pgier

            I think the testsuite is still compiling against the ClientLauncher in the ejb-core jar, since the snapshot ejb build in the thirdparty repository still contains this class. What does the testsuite compile classpath need to include for this?

            • 3. Re: EJB client launcher
              starksm64

              I have my workspace synced with all the changes and will validate the testsuite compile, updating whatever is broken. Its probably just that the jboss.ejb3.classpath is out of date in tools/etc/buildmagic/modules.ent

              • 4. Re: EJB client launcher
                pgier

                It's not actually broken yet, but I guess when the updated ejb3-core snapshot is deployed to the 3rd party repo, then you should see the compile error.

                I was just seeing this because the maven thirdparty build is downloading a more recent snapshot.

                • 5. Re: EJB client launcher
                  starksm64

                  Oh, yes. I'll get the testsuite building with the current ejb3-core snaphsot that does not have the ClientLauncher.

                  • 6. Re: EJB client launcher
                    starksm64

                    The only import of the ClientLauncher would be the ejb3 module, and that has been updated. The build againt the ejb3 trunk is working for me now.