guys I managed to create the feature generating mojo to determine the correct osgi version from a maven artifact. Therefore we no longer need to change versions of our maven artifacts to suit p2. We can carry on as we were. Sorry for the late notice. I only just saw this mail thread.
Saminda On Sun, Dec 20, 2009 at 7:58 PM, Lahiru Gunathilake <lah...@wso2.com> wrote: > > > On Sun, Dec 20, 2009 at 1:54 PM, Ruwan Linton <ru...@wso2.com> wrote: > >> Afkham Azeez wrote: >> > AFAIK, there is no hard and fast rule in P2 like that, only a >> convention. >> Then why do we always say that for P2 to work it has to be the same, >> hasn't any one tried this? If so lets try that now :-) >> > I have noticed that during the build process things get fails if we don't > have that convention. I'm almost done with the changes but I will hold it > without committing, if maven mess things without "-", we have to fix it in > P2 side. > > Lahiru > > > Regards > Lahiru > >> >> Thanks, >> Ruwan >> > >> > Azeez >> > >> > On Sun, Dec 20, 2009 at 1:42 PM, Ruwan Linton <ru...@wso2.com >> > <mailto:ru...@wso2.com>> wrote: >> > >> > Lahiru, >> > >> > We need to fix P2 such that it wont require the physical artifact >> name >> > to be the same as the bundle symbolic name. Otherwise we will not be >> > able to use third party OSGi bundle as it is without wrapping any >> > time. >> > >> > Also maven messes out the artifact order when we use '.' instead >> > of '-' >> > >> > I am going to change the orbit versions. >> > > >> > >> > Thanks, >> > Ruwan >> > >> > Hiranya Jayathilaka wrote: >> > > >> > > >> > > On Sun, Dec 20, 2009 at 9:29 AM, Lahiru Gunathilake >> > <lah...@wso2.com <mailto:lah...@wso2.com> >> > > <mailto:lah...@wso2.com <mailto:lah...@wso2.com>>> wrote: >> > > >> > > >> > > >> > > On Sun, Dec 20, 2009 at 8:03 AM, Ruwan Linton >> > <ru...@wso2.com <mailto:ru...@wso2.com> >> > > <mailto:ru...@wso2.com <mailto:ru...@wso2.com>>> wrote: >> > > >> > > Folks, >> > > >> > > What is the next Carbon version that we are planning to >> > > release from the >> > > trunk? I guess it is 3.0.0 right?, in which case we need >> to >> > > change the >> > > current trunk versions from 2.1.0-SNAPSHOT to >> > 3.0.0-SNAPSHOT. >> > > >> > > It should be 3.0.0.SNAPSHOT to work with P2 and I'm in the >> > process >> > > of changing it, now changing carbon-components versions. >> > > >> > > >> > > +1 >> > > >> > > BTW does this change has any implications on the P2 features that >> > > Saminda did for the trunk recently. Do we have to change them >> also? >> > > >> > > Thanks, >> > > Hiranya >> > > >> > > >> > > >> > > >> > > Lahiru >> > > >> > > >> > > Thanks, >> > > Ruwan >> > > >> > > -- >> > > Ruwan Linton >> > > Technical Lead & Product Manager; WSO2 ESB; >> > http://wso2.org/esb >> > > WSO2 <http://wso2.org/esbWSO2> Inc.; http://wso2.org >> > > email: ru...@wso2.com <mailto:ru...@wso2.com> >> > <mailto:ru...@wso2.com <mailto:ru...@wso2.com>>; cell: +94 77 >> > > 341 3097 >> > > blog: http://blog.ruwan.org >> > > >> > > >> > > >> > > _______________________________________________ >> > > Carbon-dev mailing list >> > > Carbon-dev@wso2.org <mailto:Carbon-dev@wso2.org> >> > <mailto:Carbon-dev@wso2.org <mailto:Carbon-dev@wso2.org>> >> > > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >> > > >> > > >> > > >> > > >> > > -- >> > > Lahiru Gunathilake >> > > Software Engineer - WSO2 Inc. >> > > >> > > _______________________________________________ >> > > Carbon-dev mailing list >> > > Carbon-dev@wso2.org <mailto:Carbon-dev@wso2.org> >> > <mailto:Carbon-dev@wso2.org <mailto:Carbon-dev@wso2.org>> >> > > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >> > > >> > > >> > > >> > > >> > > -- >> > > Hiranya Jayathilaka >> > > Software Engineer; >> > > WSO2 Inc.; http://wso2.org >> > > E-mail: hira...@wso2.com <mailto:hira...@wso2.com> >> > <mailto:hira...@wso2.com <mailto:hira...@wso2.com>>; Mobile: +94 >> 77 >> > > 633 3491 >> > > Blog: http://techfeast-hiranya.blogspot.com >> > > >> > >> ------------------------------------------------------------------------ >> > > >> > > _______________________________________________ >> > > Carbon-dev mailing list >> > > Carbon-dev@wso2.org <mailto:Carbon-dev@wso2.org> >> > > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >> > > >> > >> > >> > -- >> > Ruwan Linton >> > Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb >> > WSO2 <http://wso2.org/esb%0AWSO2> Inc.; http://wso2.org >> > email: ru...@wso2.com <mailto:ru...@wso2.com>; cell: +94 77 341 >> 3097 >> > blog: http://blog.ruwan.org >> > >> > >> > >> > _______________________________________________ >> > Carbon-dev mailing list >> > Carbon-dev@wso2.org <mailto:Carbon-dev@wso2.org> >> > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >> > >> > >> > >> > >> > -- >> > -- >> > Afkham Azeez >> > az...@wso2.com <mailto:az...@wso2.com> >> > WSO2 Inc. http://wso2.com >> > Blog: http://afkham.org >> > ------------------------------------------------------------------------ >> > >> > _______________________________________________ >> > Carbon-dev mailing list >> > Carbon-dev@wso2.org >> > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >> > >> >> >> -- >> Ruwan Linton >> Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb >> WSO2 <http://wso2.org/esbWSO2> Inc.; http://wso2.org >> email: ru...@wso2.com; cell: +94 77 341 3097 >> blog: http://blog.ruwan.org >> >> >> >> _______________________________________________ >> Carbon-dev mailing list >> Carbon-dev@wso2.org >> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >> > > > > -- > Lahiru Gunathilake > Software Engineer - WSO2 Inc. > > _______________________________________________ > Carbon-dev mailing list > Carbon-dev@wso2.org > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > >
_______________________________________________ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
