So there's a few things you'll probably need to do to make it work in Eclipse.
First, build the project on the command line using Maven (this important for step 3 so generated code is available) Second, after importing as a Maven project into Eclipse, to fix issues with maven in eclipse go to Maven Problems tree under Markers. Expand that and you can take care of the lifecycle mapping problems. Right click on an error that says "Plugin execution not covered by lifecycle configuration...." and go to quick fix. Then select "Mark goal descriptor as ignored in Eclipse build in Eclipse preferences" You'll need to repeat this a few times but eventually that will clear up the maven errors as they are related to plugin executions that you don't need to run in eclipse. Lastly, you'll probably need to clean up some class path issues related to generated code. For example, for the activemq- client project you'll need to edit the Java build path and add activemq-client/target/generated-sources/javacc as a source folder. (this requires building on the command line first). There could be other projects with a similar issue. Keep in mind that if there's a particular subproject giving you problems building (such as maybe issues with building activemq-leveldb-store becuase of Scala), you could always remove that specific subproject from Eclipse if it isn't related to what you are trying to debug. On Wed, Jun 17, 2015 at 1:52 PM, bbuzzard <billy.buzz...@bnsflogistics.com> wrote: > I have ActiveMQ-5.5.1 on a production machine and I would like to remotely > troubleshoot a specific camel route on it. I have tried to Build > ActiveMQ-5.8.0, but I seem to be running into similar problems. > > I am using Eclipse Luna 4.4.2. Internally Luna is using the EMBEDDED Maven > 3.2.1/1.5.2.20150413-2214. Luna is using jdk1.6.0_45. > > I connected to https://svn.apache.org/respos/asf and checked out > ActiveMQ-5.5.1 as a Maven Project. The dialog: Import Maven Projects: > Setup > Maven plugin connectors popped up and showed the following: > > activemq-protobuf:1.1:compile (1 errors) > Action=Resolve Later > /activemq-core/pom.xml > javacc-maven-plugin:2.0:javacc (1 errors) > Action=Resolve Later > /activemq-core/pom.xml > javacc-maven-plugin:2.6:javacc (1 errors) > Action=Resolve Later > /activemq-client/pom.xml > maven-bundle-plugin:2.1.0:cleanVersions (24 errors) > Action=Resolve Later > Execution cleanVersions, in /activemq-all/pom.xml > Execution cleanVersions, in /activemq-blueprint/pom.xml > Execution cleanVersions, in /activemq-camel/pom.xml > Execution cleanVersions, in /activemq-console/pom.xml > Execution cleanVersions, in /activemq-core/pom.xml > Execution cleanVersions, in /activemq-fileserver/pom.xml > Execution cleanVersions, in /activemq-jaas/pom.xml > Execution cleanVersions, in /activemq-jmdns/pom.xml > Execution cleanVersions, in /activemq-karaf/pom.xml > Execution cleanVersions, in /activemq-openwire-generator/pom.xml > Execution cleanVersions, in /activemq-optional/pom.xml > Execution cleanVersions, in /activemq-pool/pom.xml > Execution cleanVersions, in /activemq-ra/pom.xml > Execution cleanVersions, in /activemq-rar/pom.xml > Execution cleanVersions, in /activemq-run/pom.xml > Execution cleanVersions, in /activemq-spring/pom.xml > Execution cleanVersions, in /activemq-web-console/pom.xml > Execution cleanVersions, in /activemq-web-demo/pom.xml > Execution cleanVersions, in /activemq-web/pom.xml > Execution cleanVersions, in /activemq-xmpp/pom.xml > Execution cleanVersions, in /kahadb/pom.xml > Execution cleanVersions, in /maven-activemq-memtest-plugin/pom.xml > Execution cleanVersions, in /maven-activemq-perf-plugin/pom.xml > Execution cleanVersions, in /maven-activemq-plugin/pom.xml > maven-bundle-plugin:2.1.0:manifest > Action=Resolve Later > Execution bundle-manifest, in /activemq-web-console/pom.xml > maven-jaxb2-plugin:0.7.2:generate (1 errors) > /activemq-xmpp/pom.xml > maven-plugin-plugin:2.5.1:descriptor (3 errors) > Action=Resolve Later > Execution default-descriptor, in > /maven-activemq-memtest-plugin/pom.xml > Execution default-descriptor, in > /maven-activemq-perf-plugin/pom.xml > Execution default-descriptor, in /maven-activemq-plugin/pom.xml > maven-xbean-plugin:3.7:mapping (2 errors) > Action=Resolve Later > /activemq-core/pom.xml > /activemq-ra/pom.xml > > I am not sure how to resolved the errors listed above. When I build from > the command line and ship the tests it seems to build, but when I try to do > the same thing from within Luna it DOES NOT WORK. > > All I want to do is to remotely debug an existing ActiveMQ-5.5.1. I assume > I have to have ActiveMQ-5.5.1 checked out into my workspace and that it > should have no errors. I cannot clear the errors until I built it and > Maven > in Luna is not working. > > Help! I am killing a bunch of time trying to do something I am sure > ActiveMQ developers are doing on a daily basis. > > If you know the step by step instructions on how to build ActiveMQ-5.8.0 > inside of Eclipse Luna, send them to me and I will try that. > > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/Errors-trying-to-build-ActiveMQ-5-5-1-from-source-tp4697726p4697917.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. >
