Well, we should update the documentation on the build site then to specify that Maven 2.x should be used rather than maven 1.x... I found after perusing the mailing list archives the amount of effort you guys went through to add support for building under maven 2 and it looks like a lot of work which I applaud your efforts, but the info under the build section is now out of date.
I will try again tomorrow to update my environment under maven 2.x - I was under the impression from the docs that everything was still maven 1.x compliant, but apparently that is no longer the case. which further implores the need to update META to support a Maven 2.x framework. thanks again, Jeffery Painter > Jeffery Painter wrote: >> ok.. so I had to actually update not pbe/pom.xml but I also had to >> modify >> pbe/project.xml to add the dependency for fulcrum-yaafi-crypto 1.0.6 in >> order to get it to build... then maven (version 1.1) complained that it >> could not find the 1.0.6 jar, so I had to download manually and install >> it >> in my local repo... I think the problem was it downloaded >> "fulcrum-crypto-1.0.6.jar" and it was looking for >> "fulcrum-yaafi-crypto-1.0.6" > > Aehm, we are talking *Maven-2* here. I guess the maven-1 builds are not > maintained well right now. They are about to go once the releases are > through. We changed group-ids, dependencies and stuff. > > Bye, Thomas. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
