Hi, I had a similar problem yesterday. I did the same, checking out smix from svn. After deleting all older servicemix entries in my local maven repository, the build runs fine with the exception of a reference to xfire-parent-1.2-RC.pom. In the pom of xire-1.2-RC is a reference to the dev.java.net-Repository at Sun and my maven did not succeed in getting anything from there. The repository at java.net requires https, which may prevent maven to succeed (proxy or certificate issues?).
However, the xfire-parent.pom is also available at ibiblio from where I installed it locally. After that, the build ran fine. Klaus. gnodet wrote: > > Missing poms only generate warnings, but should not prevent the build to > succeed. I hope next spring releases will have a pom ... > Generating poms in a private repository is generally not a good thing as > it could clash with the ones on public repos once they are added. > > Do you have other build erros ? if yes, please paste the maven ouput. > > On 8/14/06, Bouchard, Kevin <[EMAIL PROTECTED]> wrote: >> >> Hi, >> >> >> >> I made a svn checkout of the servicemix project this morning from apache >> incubator. I have tried several times to build the code using Maven2 >> with no success. After some investigation, I have found that a few >> dependencies are absent from maven repositories. For example, Spring >> framework 2.0 RC1 POM file isn't available at any of the repositories. >> Is it a known issue? What is the solution? Is there a possibility to put >> the missing POM in the servicemix-repo? >> >> >> >> Thank you very much. >> >> >> >> Kevin. >> > > -- > Cheers, > Guillaume Nodet > > -- View this message in context: http://www.nabble.com/unable-to-build-servicemix-tf2105513.html#a5810049 Sent from the ServiceMix - User forum at Nabble.com.
