6 Replies Latest reply on Apr 20, 2005 4:46 AM by Dimitris Andreadis

    jboss-jmx cann't be compiled

    Jun Ho Cho Newbie

      I cann't compile jboss-jmx module in tag-name jboss-4.0.
      In my opinion, there is no some class needing when compile.

      for example, org.jboss.mx.server.ServerConstants

        • 1. Re: jboss-jmx cann't be compiled
          Jun Ho Cho Newbie

          In addition, build.xml is wrong.

          library.classpath property have no sun.jmx.classpath property.

          • 2. Re: jboss-jmx cann't be compiled
            Dimitris Andreadis Master

            You mean the jmx module stand-alone? It compiles fine as part of the jboss checkout. AFAIK it's been a couple of years since the last stand-alone realease (jboss-mx v1.1.2)

            • 3. Re: jboss-jmx cann't be compiled
              Jun Ho Cho Newbie

               

              "dimitris@jboss.org" wrote:
              You mean the jmx module stand-alone? It compiles fine as part of the jboss checkout. AFAIK it's been a couple of years since the last stand-alone realease (jboss-mx v1.1.2)


              I check out jboss-4.0 and run build.xml in build sub-directory. I met following error.

              [javac] Compiling 103 source files to C:\workspace\jboss-4.0\jmx\output\classes
              C:\workspace\jboss-4.0\jmx\src\main\org\jboss\cache\invalidation\bridges\JGCacheInvalidati
              onBridge.java:15: cannot resolve symbol
              symbol : class BatchInvalidation
              location: package invalidation
              import org.jboss.cache.invalidation.BatchInvalidation;
              ^
              C:\workspace\jboss-4.0\jmx\src\main\org\jboss\cache\invalidation\bridges\JGCacheInvalidati
              onBridge.java:16: cannot resolve symbol
              symbol : class InvalidationManager
              location: package invalidation
              import org.jboss.cache.invalidation.InvalidationManager;
              ^
              C:\workspace\jboss-4.0\jmx\src\main\org\jboss\cache\invalidation\bridges\JGCacheInvalidati
              onBridge.java:17: cannot resolve symbol
              symbol : class InvalidationGroup
              location: package invalidation
              import org.jboss.cache.invalidation.InvalidationGroup;
              ^
              C:\workspace\jboss-4.0\jmx\src\main\org\jboss\cache\invalidation\bridges\JGCacheInvalidati
              onBridge.java:18: cannot resolve symbol
              symbol : class InvalidationManagerMBean
              location: package invalidation
              import org.jboss.cache.invalidation.InvalidationManagerMBean;
              ^
              C:\workspace\jboss-4.0\jmx\src\main\org\jboss\cache\invalidation\bridges\JGCacheInvalidati
              onBridge.java:19: cannot resolve symbol
              symbol : class BridgeInvalidationSubscription
              location: package invalidation
              import org.jboss.cache.invalidation.BridgeInvalidationSubscription;

              ....
              ^

              • 4. Re: jboss-jmx cann't be compiled
                Darran Lofthouse Master

                 

                "miloveme" wrote:

                I check out jboss-4.0


                How did you perform the checkout? What was the CVS command that you used? Did you specify 'Branch_4_0'?

                • 5. Re: jboss-jmx cann't be compiled
                  Jun Ho Cho Newbie

                   

                  "darranl" wrote:
                  "miloveme" wrote:

                  I check out jboss-4.0


                  How did you perform the checkout? What was the CVS command that you used? Did you specify 'Branch_4_0'?


                  when i checkout with Brach_4_0 branch name, I have following error.

                  cvs checkout: [08:06:18] waiting for jboss-build's lock
                  in /cvsroot/jboss/jbossmq/src/main/org/jboss/mq/il/oil2

                  so, I wait 30 minutes.. but some message.

                  • 6. Re: jboss-jmx cann't be compiled
                    Dimitris Andreadis Master

                    This is a sourceforge issue, usually a transient one. Sourceforge has been very slow lately...