Hi Paul, The video looks good, and I can’t see any problems (i.e. everything looks to be working fine). What is it that you’re expecting to see that you don’t?
If you’re worried that you don’t see an index file, then don’t be. The indexer plugin only runs against certain project templates as, for example, there’s no point in indexing an API bundle or a DS component. Both of the projects in the video are DS components, and have no need for an index. If you were to create a testing project or an application project then those would use the indexer to create an index, and that index would be used in resolving/testing. You can tell the projects that will create an index because they contain: <plugin> <groupId>biz.aQute.bnd</groupId> <artifactId>bnd-indexer-maven-plugin</artifactId> </plugin> In their build/plugins configuration. This activates the template for the indexer plugin that comes from the <pluginManagement> of the parent. I hope this helps, Tim > On 20 May 2018, at 07:26, Paul F Fraser via osgi-dev <osgi-dev@mail.osgi.org> > wrote: > > Hi, > > After many hours immersing myself in youtube maven videos and working through > the new enRoute documentation I am slowly gaining an appreciation for the > techniques involved. > > The problem at the moment is handling the indexing and setting up the bndrun > files. > > When working through the examples repo the quickstart project, which uses > project archetype, creates the indexes in the target folder after a maven > install. > > The microservices project (bare bones project) does not do this for me. The > poms for both bare bones and project seem to depend on the indexing plugin. > > I have produced a short video (2 mins) of my approach and would appreciate > comments which might guide me to a solution. > > https://youtu.be/GswNFHxJ3e8 > > It might be worthwhile for me to complete the video (with some audio) when > the problems are sorted, it might be helpful to others. > > Or alternatively my approach may be totally wrong. > > Paul > > _______________________________________________ > OSGi Developer Mail List > osgi-dev@mail.osgi.org > https://mail.osgi.org/mailman/listinfo/osgi-dev
_______________________________________________ OSGi Developer Mail List osgi-dev@mail.osgi.org https://mail.osgi.org/mailman/listinfo/osgi-dev
