Hi, This happened after removing old bam from 4.1.0 branch. Looks like stratos components still depend on old bam still. Can we please get this fixed soon?.
thanks, On Tue, Mar 5, 2013 at 11:12 AM, Geeth Munasinghe <[email protected]> wrote: > Hi > There is an error > > [INFO] BUILD FAILURE > [INFO] > ------------------------------------------------------------------------ > [INFO] Total time: 9.061s > [INFO] Finished at: Mon Mar 04 21:43:28 PST 2013 > [INFO] Final Memory: 267M/1178M > [INFO] > ------------------------------------------------------------------------ > [ERROR] Failed to execute goal on project > org.wso2.carbon.usage.summary.generator: Could not resolve dependencies for > project > org.wso2.carbon:org.wso2.carbon.usage.summary.generator:bundle:2.1.0: The > following artifacts could not be resolved: > org.wso2.carbon:org.wso2.carbon.bam.core:jar:4.1.0, > org.wso2.carbon:org.wso2.carbon.bam.common:jar:4.1.0, > org.wso2.carbon:org.wso2.carbon.bam.util:jar:4.1.0: Failure to find > org.wso2.carbon:org.wso2.carbon.bam.core:jar:4.1.0 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] > > thanks > > > *G. K. S. Munasinghe > * > *Software Engineer,* > *WSO2, Inc. http://wso2.com * > *lean.enterprise.middleware.* > * > * > email: [email protected] > phone:(+94) 777911226 > > > On Mon, Mar 4, 2013 at 11:34 AM, Supun Malinga <[email protected]> wrote: > >> +1, >> Please remove from both trunk and branch(4.1.0) accordingly. >> >> thanks, >> >> >> On Mon, Mar 4, 2013 at 10:01 AM, Amila Maha Arachchi <[email protected]>wrote: >> >>> Yes, now we are not using them. Lets remove and fix if there are any >>> build failures. >>> >>> >>> On Mon, Mar 4, 2013 at 9:49 AM, Kasun Weranga <[email protected]> wrote: >>> >>>> Hi, >>>> >>>> We didn't remove it because stratos billing and metering was using >>>> those earlier bam components until they move to new bam. I think now we can >>>> remove it. When removing if they still have references to old bam >>>> components there can be build failures. So need check that before removing. >>>> >>>> Thanks, >>>> KasunW. >>>> >>>> >>>> On Sun, Mar 3, 2013 at 7:24 PM, Supun Malinga <[email protected]> wrote: >>>> >>>>> Hi bam folks, >>>>> >>>>> components/bam, components/bam2 >>>>> features/bam, features/bam2 >>>>> >>>>> I know bam2 is the improved bam version. But do we still use both?. >>>>> We should either merge or remove /bam. >>>>> >>>>> thanks, >>>>> -- >>>>> Supun Malinga, >>>>> >>>>> Software Engineer, >>>>> WSO2 Inc. >>>>> http://wso2.com >>>>> http://wso2.org >>>>> email - [email protected] <[email protected]> >>>>> mobile - 071 56 91 321 >>>>> >>>> >>>> >>>> >>>> -- >>>> *Kasun Weranga* >>>> ** >>>> Member, Management Committee - Data Technologies >>>> Software Engineer >>>> *WSO2, Inc. >>>> *lean.enterprise.middleware. >>>> mobile : +94 772314602 >>>> <http://sanjeewamalalgoda.blogspot.com/>blog : >>>> http://kasunweranga.blogspot.com/ >>>> >>> >>> >>> >>> -- >>> *Amila Maharachchi* >>> Technical Lead >>> Member, Management Committee - Cloud & Platform TG >>> WSO2, Inc.; http://wso2.com >>> >>> Blog: http://maharachchi.blogspot.com >>> Mobile: +94719371446 >>> >>> >> >> >> -- >> Supun Malinga, >> >> Software Engineer, >> WSO2 Inc. >> http://wso2.com >> http://wso2.org >> email - [email protected] <[email protected]> >> mobile - 071 56 91 321 >> >> _______________________________________________ >> Dev mailing list >> [email protected] >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > -- Supun Malinga, Software Engineer, WSO2 Inc. http://wso2.com http://wso2.org email - [email protected] <[email protected]> mobile - 071 56 91 321
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
