I'm new to ActiveMQ so please forgive my ignorance if this question seems obvious. I downloaded the 5.7 version the ActiveMQ source to a Tilera (non-x86 architecture) CentOS machine and then compiled it using "mvn clean install -Dmaven.test.skip=true". The compilation reported success with all modules.
However, regarding testing the build, the documentation for ActiveMQ provides a link to the "Starting ActiveMQ" portion of the document which specifies that one must execute "bin\activemq" to start the application. Unfortunately, no (obvious) bin directory is created during the compilation/installation stage. For instance, there is no bin sub-directory in the "activemq-parent-5.7.0" directory from which I compiled all of the source code. Using "find . -name bin -type d" inside the "activemq-parent-5.7.0" directory yields four results, only one of which seems relevant. It is located at "./assembly/src/release/bin". However, trying to execute the activemq executable in this directory yields the error: ERROR: './assembly/src/release/bin/run.jar' does not exist ...which is true (i.e., run.jar does not exist in this directory). How do I appropriately test ActiveMQ once I've compiled it from source? - Bruce -- View this message in context: http://activemq.2283324.n4.nabble.com/Compiling-from-source-tp4660941.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
