On 9/19/06, Irv Salisbury <[EMAIL PROTECTED]> wrote:
You know, the change James reccomended works! I try building without the settings.xml file and it doesn't work. I try building with the settings.xmlfile and it all works fine! I went back and forth to make sure and it was the key. So, can someone tell me exactly what this does?
The cargo.container.home property is used during integration tests. Now that you've set it, try: cd shale-apps mvn install -Pitest I have no idea why adding that profile makes the problem with commons-validator go away. I have that same Cargo config, and the build still fails. What fixes it for me is adding <version>1.3.0</version> to the commons-validator dependency in the shale-core module. That should not be necessary, because the version is set in <dependencyManagement> in the shale-parent pom. However, we've had other problems with Maven's dependency management. In this case, commons-validator is excluded from the myfaces dependency. When I run "mvn clean install -X" from 'framework' and look at the dependencies of the failing build, commons-validator doesn't show up at all. That explains the "package oas.commons.validtor does not exist" errors. -- Wendy
