Ok, that I understand. However in my question we're not yet using subsystems, the question (A) is just about bundle resolving using the repo.xml, not subsystems
2015-03-25 13:52 GMT+01:00 Kamesh Sampath <[email protected]>: > sorry my bad i did not notice it. > > but right now we can’t generate subsystem indexing in the repo using the > available tools, even my personal experience as you had i was able to do it > only via maven:bundle indexing which tries to resolve the subsystem content > form the maven repo, the repoindex does not index the esa as it does not > know how/what to index, currently even in OSGi spec we dont have the right > defs for it. > > @David, please feel to add if i had missed any point. > > — > *Kamesh Sampath* > Sr.Architect, Liferay India > Twitter <https://twitter.com/@kamesh_Sampath> | LinkedIn > <http://in.linkedin.com/pub/kamesh-sampath/4b/934/338/> > > On 25-Mar-2015, at 6:12 pm, Tim Vissers <[email protected]> wrote: > > It's not a bundle, it's a api package that is exported in be.aca.service > and imported in be.aca.service-user. > en t > Tim > > 2015-03-25 13:38 GMT+01:00 Kamesh Sampath <[email protected]>: > >> am not seeing be.aca.service.api in the obr:list, where is that bundle ? >> >> — >> *Kamesh Sampath* >> Sr.Architect, Liferay India >> Twitter <https://twitter.com/@kamesh_Sampath> | LinkedIn >> <http://in.linkedin.com/pub/kamesh-sampath/4b/934/338/> >> >> On 25-Mar-2015, at 6:02 pm, Tim Vissers <[email protected]> wrote: >> >> be.aca.service.api >> >> >> > >
