I downloaded the very latest Servicemix src and wiped out my maven repository to have a fresh start. The step 2 build fails. New reason I have not seen before regarding an incompatible jaxb...
I think I need to give this up, building from source is just not fully cooked (yes, I'm sure it works fine in some specific environments). I can hook up my application with a web service or something instead of XMPP as a proof of the ESB concept. Other parts of Servicemix seem to work fine as far as I can tell. It's been way too much work just to update the smack jars and change a couple of java files with code I've already written and know works. I'll try again at a later time. Thanks all. On Tue, Jun 3, 2008 at 8:24 AM, Jeff Sexton <[EMAIL PROTECTED]> wrote: > On Mon, Jun 2, 2008 at 11:53 PM, Chris Custine <[EMAIL PROTECTED]> > wrote: > >> On Mon, Jun 2, 2008 at 4:44 PM, Jeff Sexton <[EMAIL PROTECTED]> wrote: >> > I worked on something else for a day, but I'm back at this now. I seem >> to >> > be able to alter source code and build a new XMPP zip file. I set up a >> > separate computer to drop the resulting zip file into hotdeployables on, >> > all >> > built with the new smack dependancy. Here's a couple problems... >> > >> > When I rebuild with the command "mvn -Dmaven.test.skip=true -Pnochecks >> > clean >> > install" I get a lot of output ending with a class-not-found >> > com/sun/codemodel/JCodeModel >> > If I rebuild with the two step process, it seems to succeed fine, so I >> did >> > that. It takes longer, but that's not saying much. >> >> >> You should definitely be able to run "mvn -Pnochecks clean install" from >> the >> servicemix-xmpp directory itself and the build should run fine. I am not >> sure what this error is about so if you keep getting it let us know. >> > > I can in fact build what seems to be a valid zip file just fine. I get > issues when a) trying to deploy that zip file, and b) running "clean > install" from the src root. This is interesting - this morning I started > from scratch. I unpacked a new src directory from the original download of > last week and tried the two step build process. In step two it now fails > with JCodeModel not found. This build worked fine last week. I suppose the > local maven repository must have changed. Should I wipe that out too? > > >> >> > >> > >> > When I put my new zip file in hotdeployables and start servicemix, it >> > starts >> > up fine. When I then deploy an SA that uses XMPP, I get a class >> -not-found >> > on one of the new classes in the new smack.jar file. Obviously the >> correct >> > version of the smack jars are not available to servicemix for some >> reason. >> >> >> These dependencies are managed with a dependencyManagement section it he >> top >> level pom.xml file. If you open the top level pom you will find the two >> entries with <groupId>jivesoftware</groupId> and you will need to make >> sure >> you update the versions there. After you do that make sure that you build >> the top level once to install the pom. >> > > > I did that, yes. This isn't completely making sense, which is why I wanted > to start fresh from the src distribution to make sure I got everything done > correctly. This is what I think Ishould do,as I understand it. > > 1) unpack src > 2) remove the old jabber light-weight components > 3) build with the two step process > 4) edit the root pom.xml and change the version of the smack jars > 5) mvn install the new jars (if I need to wipe out the maven repository at > ~/.m2) > 6) replace the servicemix-xmpp java files, and edit the smack version in > the xmpp pom.xml > 7) do "clean install" in the servicemix-xmpp directory to build a new zip > (this has worked for me, last week) > 8) deploy the new zip to hotdeploy (replace the old one) > 9) start > 10) deploy the SA I already made > > Q1 - Are these steps correct and is step 7 all that is required to make > this change or do I need to do a "clean install" in servicemix/src first? > Q2 - What's this JCodeModel problem all about? > > Thanks! > > >
