Hi Tim,
I followed your advice and find a bunch of mvn plugins for bnd here https://github.com/bndtools/bnd/tree/master/maven I have used bnd-indexer-maven-plugin on the example given in the tutorial <http://enroute.osgi.org/tutorial_eval/> http://enroute.osgi.org/tutorial_eval/050-start.html and created index files in all projects. All great!!!! Now I have two more question: 1- When I run the indexer plugin I see the following output [INFO] The Artifact org.osgi:osgi.enroute.websecurity.adapter:jar:2.0.0 could not be found in any repository, returning the local location which reflects in the generated index file as <capability namespace="osgi.content"> <attribute name="osgi.content" value="77b38abc362a40e293be9ff4cafba15b0eb73b0af394e697b648bcbb271b6ebe"/> <attribute name="url" value="file:/home/daghan/.m2/repository/org/osgi/osgi.enroute.websecurity.adapter/2.0.0/osgi.enroute.websecurity.adapter-2.0.0.jar"/> <attribute name="size" type="Long" value="48218"/> <attribute name="mime" value="application/vnd.osgi.bundle"/> </capability> I would expect something like <capability namespace="osgi.content"> <attribute name="osgi.content" value="77b38abc362a40e293be9ff4cafba15b0eb73b0af394e697b648bcbb271b6ebe"/> <attribute name="url" value="https://mvnrepository.com/artifact/org.osgi/osgi.enroute.websecurity.adapter/2.0.0"/> <attribute name="size" type="Long" value="48218"/> <attribute name="mime" value="application/vnd.osgi.bundle"/> </capability> am I doing something wrong? 2- These index contains the dependencies of the project. I also create index file for my own projects. I can do that from eclipse->project->Release bundles and the indexes corresponding to my projects are created under cnf->release->index.xml along with the jar file under the folder with the name of the project. Is there a way to do it with mvn plugins? Thanks for your response in advance Cheers -Daghan ________________________________ From: osgi-dev-boun...@mail.osgi.org <osgi-dev-boun...@mail.osgi.org> on behalf of Timothy Ward <tim.w...@paremus.com> Sent: Monday, November 14, 2016 10:48 AM To: OSGi Developer Mail List Subject: Re: [osgi-dev] Mvn for enroute is it possible to use only bndrun and not the pom file? Yes - however in order for the bndrun file to work it needs to have one or more repositories to pull bundles from. In the example the repository that is used is a “POM repository” i.e. it uses dependencies from a Maven POM. Therefore the bndrun can only “see” what’s in the POM! If you use a different kind of repository then there’s no need to put the dependency in the POM file, but then you need to create that other repository somehow. The bnd-indexer-maven-plugin may be of interest if you want to go in this direction, as might using Gradle and the bnd workspace model. I hope this helps. Regards, Tim On 13 Nov 2016, at 07:20, Daghan ACAY <daghana...@hotmail.com<mailto:daghana...@hotmail.com>> wrote: Hi, I am looking at http://enroute.osgi.org/tutorial_eval/400-command and under the heading "Adding the Command Bundle to the Runtime" it says to add the command bundle both to bndrun file and the pom.xml file. Strictly speaking command bundle is not a dependency so it does not need to go pom file. So I am looking something like this to be inserted to bndrun file: osgi.identity;filter:='(&(osgi.identity=osgi.enroute.examples.eval.command)(osgi.version>=1.0.0-SNAPSHOT))' but when I build with mvn install then I get the following error [ERROR] Failed to execute goal biz.aQute.bnd:bnd-export-maven-plugin:3.4.0-SNAPSHOT:export (default) on project osgi.enroute.examples.eval.bndrun: Unable to resolve <<INITIAL>> version=null: missing requirement osgi.enroute.examples.eval.command; osgi.version>=1.0.0-SNAPSHOT -> [Help 1] is it possible to use only bndrun and not the pom file? Cheers -Daghan _______________________________________________ OSGi Developer Mail List osgi-dev@mail.osgi.org<mailto: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