Hi, It seems to work for me (about the commands history).
Do you see the commands in shell:history ? Regards JB > Le 10 mai 2021 à 18:14, Steinar Bang <s...@dod.no> a écrit : > >>>>>> Jean-Baptiste Onofre <j...@nanthrax.net>: > >> Can you describe your test case ? > > 1. Download the tar.gz of the binary build > 2. Unpack into /tmp/apache-karaf-4.3.2/ > 3. Do "cd /tmp/apache-karaf-4.3.2/" > 4. Start karaf with "bin/karaf debug" > 5. From the karaf console add my own maven repo: > config:edit org.ops4j.pax.url.mvn > config:property-append org.ops4j.pax.url.mvn.repositories ", > https://maven.bang.priv.no/repository/@id=ukelonn@snapshots"; > config:property-set org.ops4j.pax.url.mvn.globalUpdatePolicy always > config:update > 6. Also from the karaf console, add the 4.3.2 staging maven repo (so > that karaf can provison stuff using maven): > config:edit org.ops4j.pax.url.mvn > config:property-append org.ops4j.pax.url.mvn.repositories ", > https://repository.apache.org/content/repositories/orgapachekaraf-1156/@id=karaf@staging"; > config:update > 7. Load myapps > feature:repo-add mvn:no.priv.bang.myapps/myapps/LATEST/xml/features > feature:install myapps > 8. Note: at this point command history work: I can do ctrl-p and see > the previous commands > 9. Stop karaf, edit jdbc urls and credentials in some of the > org.ops4j.datasource-*.cfg files > 10. Start karaf again and do "Ctrl-p" (because the arrow keys on my > laptop don't work so well) and there is no command history > > So the failure start at point 10, ie. from the console after stopping > and starting karaf. > > And this is something I do a lot with tarball karaf releases, and I've > never seen the command history go away before. > > Note: if you would like the applications to actually run, you would need > a PostgreSQL server running on the same host as karaf is running, with > blank databases > - authservice > - ukelonn > - handlereg > - sonar-collector > - oldalbum > all owned by PosgreSQL user "karaf" with password "karaf" (or stop and > edit the org.ops4j.datasource-*.cfg files to change databases names, > location or credentiials, like in 9. above) > > (but I don't think working apps is necessary for testing the command > history issue) >
