Earlier you said that the org.jivesoftware package was not found, which means that maven is resolving the jar files (or else it would have failed earlier) and is trying t compile against them. I am not sure why it would not see the jar files though. Have you checked the jars in the maven repo to make sure they have the correct packages? BTW, I am wondering if you installed the smackx jar file twice, once as smackx and once as smack?
Could you send the output of your maven compile so that we can see if there is anything interesting? Thanks, Chris On Thu, May 29, 2008 at 9:59 AM, Jeff Sexton <[EMAIL PROTECTED]> wrote: > On Thu, May 29, 2008 at 8:37 AM, Bruce Snyder <[EMAIL PROTECTED]> > wrote: > > > On Thu, May 29, 2008 at 9:20 AM, Jeff Sexton <[EMAIL PROTECTED]> wrote: > > > Here's what I did... > > > > > > Edited the pom file in the root and changed the version of the two > smack > > > entries to the current version, then ran "mvn -Dmaven.test.skip=true > > clean > > > install" > > > As expected, this complained that the jars were not found and gave an > mvn > > > install command to use to install each one. I did that pointing to the > > > current jar files. Then I ran the "clean install" mvn command again. > > Now, > > > the failure is that the entire org.jivesoftware.smack package is not > > found. > > > I know almost nothing about maven, except what I've seen while working > on > > > this, so I really have not idea what to do next... > > > > These are not Maven errors per se. This Maven stating that it cannot > > locate the versions of the jar that you have told it to look for in > > the repositories listed in the root POM. Have you located the versions > > of the smack jars you'd like to use in a Maven repository somewhere? > > > I ran the mvn commands given by the first failure to "install" the latest > jars (version 3.0.4). Something like this: > > mvn install:install-file -DgroupId=jivesoftware -DartifactId=smack > -Dversion=3.0.4 [etc...] > > It seemed to succeed at that. Those are the jars I need as there are > pretty > significant differences. I don't know what else I need to do? > > One other thing, the older jabber components will fail to build against the > newer smack jars. I moved that whole jabber directory away and that seemed > to work. I don't know if that's the right thing to do, but it seemed to > avoid the build failure. > > > I > > just did a very quick search for the smack jars and the latest version > > I can find in the central Maven repository is 2.2.1: > > > > http://repo1.maven.org/maven2/jivesoftware/smack/ > > > > If a newer version is available, it needs to be published to a > > publicly available Maven repository, preferably central, so that it is > > accessible. > > > > > Side observation: this build process has a pretty steep learning curve > > just > > > to change 10 lines or so in XMPPEndPoint.java. > > > > We are planning to begin slimming down the ServiceMix 3 build very > > soon. However, ServiceMix is a complex product and working on the > > source does require having some advanced knowledge of various pieces > > of software including Maven. > > > > Bruce > > -- > > perl -e 'print > > unpack("u30","D0G)[EMAIL PROTECTED]&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*" > > );' > > > > Apache ActiveMQ - http://activemq.org/ > > Apache Camel - http://activemq.org/camel/ > > Apache ServiceMix - http://servicemix.org/ > > Apache Geronimo - http://geronimo.apache.org/ > > > > Blog: http://bruceblog.org/ > > > -- Chris Custine My Blog :: http://blog.organicelement.com Apache ServiceMix :: http://servicemix.apache.org Apache Directory Server :: http://directory.apache.org
