I don’t know what you mean - it clearly always said "mvn verify" <https://github.com/osgi/osgi.enroute.site/pull/161> ;)
Thanks for the bug report. If you do find anything else on the site then feel free to raise bugs against the https://github.com/osgi/osgi.enroute.site <https://github.com/osgi/osgi.enroute.site> repository. Many thanks, Tim > On 23 Apr 2018, at 18:54, Kevin Boyle <kevintbo...@yahoo.com> wrote: > > Thanks Tim, > I followed the instructions on > http://enroute.osgi.org/tutorial/020-tutorial_qs.html > <http://enroute.osgi.org/tutorial/020-tutorial_qs.html> which executes the > "mvn bnd-resolver:resolve" before doing the "mvn package" and doesn't mention > anything about indexing. Is the example incomplete or incorrect? I did > run "mvn package" and the app.jar was created and ran correctly so I believe > your comments are correct but wonder why the tutorial has "mvn > bnd-resolver:resolve" coming before the "mvn package"? Any ideas? > K > > > > > > <1524505875375blob.jpg> > > > On Monday, April 23, 2018, 1:47:47 PM EDT, Tim Ward <tim.w...@paremus.com> > wrote: > > > Hi Kevin, > > Did you do any other kind of build first? My guess is that the problem you > have is that you’re skipping ahead in the example. > > If you’re working purely from the command line then you need to generate the > indexes before you can do a resolve. If you go straight for the resolve then > the indexes aren’t present and the resolve will fail. > > The command to generate all the indexes is: > > mvn bnd-indexer:index bnd-indexer:index@test-index > > But note that unless you have built the example projects locally you will be > indexing the versions from the OSGi snapshot repository, not the locally > built bundles (which don’t exist). In any event, once you have the indexes > the resolve will succeed. > > In the normal example flow you would do a mvn package (or mvn verify) first > to generate the bundles and indexes, then you could do a re-resolve if you > wanted. Note that if you do all of this in Bndtools then the continuous build > plugin builds all of these things for you automatically every time that you > save so that your resolve is always up to date. > > I hope this helps. > > Regards, > > Tim > >> On 23 Apr 2018, at 18:32, Kevin Boyle via osgi-dev <osgi-dev@mail.osgi.org >> <mailto:osgi-dev@mail.osgi.org>> wrote: >> >> I realized that I was not in example/quickstart which I've corrected. >> >> Now when I run >> >> mvn bnd-resolver:resolve >> >> I'm getting >> [ERROR] Failed to execute goal >> biz.aQute.bnd:bnd-resolver-maven-plugin:4.0.0-SNAPSHOT:resolve (default-cli) >> on project app: Unable to resolve <<INITIAL>>: missing requirement >> osgi.identity;filter:='(osgi.identity=org.apache.felix.webconsole)' -> [Help >> 1] >> >> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute >> goal biz.aQute.bnd:bnd-resolver-maven-plugin:4.0.0-SNAPSHOT:resolve >> (default-cli) on project app: Unable to resolve <<INITIAL>>: missing >> requirement >> osgi.identity;filter:='(osgi.identity=org.apache.felix.webconsole)' >> >> at org.apache.maven.lifecycle.internal.MojoExecutor.execute >> (MojoExecutor.java:213) >> >> at org.apache.maven.lifecycle.internal.MojoExecutor.execute >> (MojoExecutor.java:154) >> >> at org.apache.maven.lifecycle.internal.MojoExecutor.execute >> (MojoExecutor.java:146) >> >> >> >> >> On Monday, April 23, 2018, 1:19:18 PM EDT, Kevin Boyle >> <kevintbo...@yahoo.com <mailto:kevintbo...@yahoo.com>> wrote: >> >> >> >> I’m new to OSGi and I’m following the enroute tutorials >> <http://enroute.osgi.org/tutorial/020-tutorial_qs.html> but ran into a >> problem immediates. I downloaded the example code >> <https://github.com/osgi/osgi.enroute> from GITHub >> >> git clone https://github.com/osgi/osgi.enroute.git >> <https://github.com/osgi/osgi.enroute.git> >> Then ran the maven command and received the error below. >> >> mvn bnd-resolver:resolve >> >> This was executed on my macbook, under macOS Sierra 10.12.6 >> Please help. >> Thank you. >> Kevin >> >> >> Kevins-MBP:osgi kevintboyle$ git clone >> https://github.com/osgi/osgi.enroute.git >> <https://github.com/osgi/osgi.enroute.git> >> Cloning into 'osgi.enroute'... >> remote: Counting objects: 14145, done. >> remote: Compressing objects: 100% (5/5), done. >> remote: Total 14145 (delta 0), reused 1 (delta 0), pack-reused 14140 >> Receiving objects: 100% (14145/14145), 61.73 MiB | 1015.00 KiB/s, done. >> Resolving deltas: 100% (7557/7557), done. >> Kevins-MBP:osgi kevintboyle$ ls >> osgi.enroute >> Kevins-MBP:osgi kevintboyle$ cd osgi.enroute >> Kevins-MBP:osgi.enroute kevintboyle$ mvn bnd-resolver:resolve >> [INFO] Scanning for projects... >> [INFO] >> ------------------------------------------------------------------------ >> [INFO] Reactor Build Order: >> [INFO] >> [INFO] OSGi enRoute indexes parent >> [pom] >> [INFO] osgi-api >> [pom] >> [INFO] impl-index >> [jar] >> [INFO] enterprise-api >> [pom] >> [INFO] debug-bundles >> [pom] >> [INFO] test-bundles >> [jar] >> [INFO] OSGi enRoute Archetypes parent >> [pom] >> [INFO] project >> [maven-archetype] >> [INFO] ds-component >> [maven-archetype] >> [INFO] rest-component >> [maven-archetype] >> [INFO] project-bare >> [maven-archetype] >> [INFO] application >> [maven-archetype] >> [INFO] api >> [maven-archetype] >> [INFO] bundle-test >> [maven-archetype] >> [INFO] OSGi enRoute examples parent >> [pom] >> [INFO] quickstart >> [pom] >> [INFO] rest >> [jar] >> [INFO] app >> [jar] >> [INFO] microservice >> [pom] >> [INFO] dao-api >> [jar] >> [INFO] rest-service >> [jar] >> [INFO] dao-impl >> [jar] >> [INFO] rest-app >> [jar] >> [INFO] dao-impl-jpa >> [jar] >> [INFO] rest-app-jpa >> [jar] >> [INFO] rest-service-test >> [jar] >> [INFO] OSGi enRoute All >> [pom] >> Downloading from central: >> https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-metadata.xml >> >> <https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-metadata.xml> >> Downloading from central: >> https://repo.maven.apache.org/maven2/org/codehaus/mojo/maven-metadata.xml >> <https://repo.maven.apache.org/maven2/org/codehaus/mojo/maven-metadata.xml> >> Downloaded from central: >> https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-metadata.xml >> >> <https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-metadata.xml> >> (14 kB at 17 kB/s) >> Downloaded from central: >> https://repo.maven.apache.org/maven2/org/codehaus/mojo/maven-metadata.xml >> <https://repo.maven.apache.org/maven2/org/codehaus/mojo/maven-metadata.xml> >> (20 kB at 25 kB/s) >> [INFO] >> ------------------------------------------------------------------------ >> [INFO] Reactor Summary: >> [INFO] >> [INFO] OSGi enRoute indexes parent 7.0.0-SNAPSHOT ......... SKIPPED >> [INFO] osgi-api 7.0.0-SNAPSHOT ............................ SKIPPED >> [INFO] impl-index 7.0.0-SNAPSHOT .......................... SKIPPED >> [INFO] enterprise-api 7.0.0-SNAPSHOT ...................... SKIPPED >> [INFO] debug-bundles 7.0.0-SNAPSHOT ....................... SKIPPED >> [INFO] test-bundles 7.0.0-SNAPSHOT ........................ SKIPPED >> [INFO] OSGi enRoute Archetypes parent 7.0.0-SNAPSHOT ...... SKIPPED >> [INFO] project 7.0.0-SNAPSHOT ............................. SKIPPED >> [INFO] ds-component 7.0.0-SNAPSHOT ........................ SKIPPED >> [INFO] rest-component 7.0.0-SNAPSHOT ...................... SKIPPED >> [INFO] project-bare 7.0.0-SNAPSHOT ........................ SKIPPED >> [INFO] application 7.0.0-SNAPSHOT ......................... SKIPPED >> [INFO] api 7.0.0-SNAPSHOT ................................. SKIPPED >> [INFO] bundle-test 7.0.0-SNAPSHOT ......................... SKIPPED >> [INFO] OSGi enRoute examples parent ....................... SKIPPED >> [INFO] quickstart ......................................... SKIPPED >> [INFO] rest ............................................... SKIPPED >> [INFO] app ................................................ SKIPPED >> [INFO] microservice ....................................... SKIPPED >> [INFO] dao-api ............................................ SKIPPED >> [INFO] rest-service ....................................... SKIPPED >> [INFO] dao-impl ........................................... SKIPPED >> [INFO] rest-app ........................................... SKIPPED >> [INFO] dao-impl-jpa ....................................... SKIPPED >> [INFO] rest-app-jpa ....................................... SKIPPED >> [INFO] rest-service-test .................................. SKIPPED >> [INFO] OSGi enRoute All 0.0.1-SNAPSHOT .................... SKIPPED >> [INFO] >> ------------------------------------------------------------------------ >> [INFO] BUILD FAILURE >> [INFO] >> ------------------------------------------------------------------------ >> [INFO] Total time: 1.769 s >> [INFO] Finished at: 2018-04-23T13:17:07-04:00 >> [INFO] >> ------------------------------------------------------------------------ >> [ERROR] No plugin found for prefix 'bnd-resolver' in the current project and >> in the plugin groups [org.apache.maven.plugins, org.codehaus.mojo] available >> from the repositories [local (/Users/kevintboyle/.m2/repository), central >> (https://repo.maven.apache.org/maven2 >> <https://repo.maven.apache.org/maven2>)] -> [Help 1] >> [ERROR] >> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e >> switch. >> [ERROR] Re-run Maven using the -X switch to enable full debug logging. >> [ERROR] >> [ERROR] For more information about the errors and possible solutions, please >> read the following articles: >> [ERROR] [Help 1] >> http://cwiki.apache.org/confluence/display/MAVEN/NoPluginFoundForPrefixException >> >> <http://cwiki.apache.org/confluence/display/MAVEN/NoPluginFoundForPrefixException> >> Kevins-MBP:osgi.enroute kevintboyle$ >> >> >> _______________________________________________ >> OSGi Developer Mail List >> osgi-dev@mail.osgi.org <mailto:osgi-dev@mail.osgi.org> >> https://mail.osgi.org/mailman/listinfo/osgi-dev > > <1524505875375blob.jpg>
_______________________________________________ OSGi Developer Mail List osgi-dev@mail.osgi.org https://mail.osgi.org/mailman/listinfo/osgi-dev
