Hi On Tue, Dec 20, 2011 at 5:08 PM, KasunG Gajasinghe <kas...@wso2.com> wrote:
> Hi, > > The artifact org.wso2.wsf.javascript:axiom-e4x has inconsistent versions > in the trunk. For example, in components/hostobjects/ , it uses the version > 2.0.0 using the property <axiom.e4x.version>2.0.0</axiom.e4x.version>. > > But in components/jaggery/pom.xml, it has re-defined <axiom.e4x.version>, > where it's set to 2.0.0.SNAPSHOT. And again, for the same artifact, > components/mashup/pom.xml has defined another version property named > wsf.js.axiom.version.mashup, which again has the value 2.0.0.SNAPSHOT. > I have reverted back to 2.0.0. should be fine now. Regards, /Nuwan > > The issue is that there is no 2.0.0.SNAPSHOT version available in nexus > [1]. Therefore, the relevant artifacts are failing. A build log for one > such artifact is given below. I didn't have this issue when I was building > this around a week back! Please fix this. > > [1] > http://maven.wso2.org/nexus/content/groups/wso2-public/org/wso2/wsf/javascript/axiom-e4x/ > > [INFO] > ------------------------------------------------------------------------ > [INFO] BUILD FAILURE > [INFO] > ------------------------------------------------------------------------ > [INFO] Total time: 2:32.115s > [INFO] Finished at: Tue Dec 20 16:39:59 IST 2011 > [INFO] Final Memory: 419M/1200M > [INFO] > ------------------------------------------------------------------------ > [ERROR] Failed to execute goal on project > org.wso2.carbon.mashup.javascript.hostobjects.registry: Could not resolve > dependencies for project > org.wso2.carbon:org.wso2.carbon.mashup.javascript.hostobjects.registry:bundle:3.2.0-SNAPSHOT: > Failure to find org.wso2.wsf.javascript:axiom-e4x:jar:2.0.0.SNAPSHOT in > http://maven.wso2.org/nexus/content/groups/wso2-public/ was cached in the > local repository, resolution will not be reattempted until the update > interval of wso2-nexus 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 > [ERROR] > > Thanks, > --KasunG > > -- > *Kasun Gajasinghe* > Software Engineer; WSO2 Inc.; http://wso2.com > > , > *email: **kasung AT spamfree wso2.com** cell: **+94 (77) 678-0813* > *blog: **http://blog.kasunbg.org* <http://blog.kasunbg.org> > > * > twitter: **http://twitter.com/kasunbg* <http://twitter.com/kasunbg> > > * > * > > > _______________________________________________ > Carbon-dev mailing list > Carbon-dev@wso2.org > http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > -- *Thanks & Regards, Nuwan Bandara Senior Software Engineer WSO2 Inc. | http://wso2.com lean . enterprise . middleware http://nuwan.bandara.co * <http://www.nuwanbando.com/>
_______________________________________________ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
