Hi, On Sun, Jul 15, 2012 at 8:44 PM, Thilina Buddhika <thili...@wso2.com> wrote:
> This should be upgraded and just committed the change. > > Although it should be upgraded, it should be able to build Rampart with > previous WSS4J version because it was released with 3.2.x. Was this an > online build ? > Yes.. This is an online build. It looks wss4j 1.5.11-wso2v3 is not in nexus. Wss4j Upgrade solved the issue and now building fine. > Thanks, > Thilina > > On Sun, Jul 15, 2012 at 8:37 PM, Ranga Siriwardena <ra...@wso2.com> wrote: > >> Hi devs, >> >> Im getting following error when building platform with a clean repo. It >> looks wss4j version is incorrect. >> >> >> [INFO] >> ------------------------------------------------------------------------ >> [INFO] Reactor Summary: >> [INFO] >> [INFO] Apache Rampart .................................... FAILURE >> [1:41.074s] >> [INFO] Rampart - Policy .................................. SKIPPED >> [INFO] Rampart - Trust ................................... SKIPPED >> [INFO] Rampart - Core .................................... SKIPPED >> [INFO] Rampart - Test Suite .............................. SKIPPED >> [INFO] Rampart - Mar ..................................... SKIPPED >> [INFO] Rampart - Trust-Mar ............................... SKIPPED >> [INFO] Rampart - Integration ............................. SKIPPED >> [INFO] >> ------------------------------------------------------------------------ >> [INFO] BUILD FAILURE >> [INFO] >> ------------------------------------------------------------------------ >> [INFO] Total time: 1:43.109s >> [INFO] Finished at: Sun Jul 15 20:35:00 IST 2012 >> [INFO] Final Memory: 8M/981M >> [INFO] >> ------------------------------------------------------------------------ >> [ERROR] Failed to execute goal on project rampart-project: Could not >> resolve dependencies for project >> org.apache.rampart:rampart-project:pom:1.6.1-wso2v4: Failure to find >> org.apache.ws.security:wss4j:jar:1.5.11-wso2v3 in >> http://dist.wso2.org/maven2 was cached in the local repository, >> resolution will not be reattempted until the update interval of >> wso2-maven2-repository has elapsed or updates are forced -> [Help 1] >> [ERROR] >> [ERROR] To see the full stack trace of the errors, re-run Maven with the >> -e switch. >> [ERROR] Re-run Maven using the -X switch to enable full debug logging. >> [ERROR] >> [ERROR] For more information about the errors and possible solutions, >> please read the following articles: >> [ERROR] [Help 1] >> http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException >> >> >> >> Thank You. >> Ranga. >> >> -- >> Ranga Siriwardena >> Software Engineer >> WSO2 Inc. >> >> >> _______________________________________________ >> Dev mailing list >> Dev@wso2.org >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > Thilina Buddhika > Associate Technical Lead > WSO2 Inc. ; http://wso2.com > lean . enterprise . middleware > > phone : +94 77 44 88 727 > blog : http://blog.thilinamb.com > Thank You. Ranga. -- Ranga Siriwardena Software Engineer WSO2 Inc.
_______________________________________________ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
