Hi Steinar, Sorry, my bad, I didn’t read your message correctly ;)
So, correct me if I’m wrong, but it seems your application runs fine with 4.3.2, which is good ;) Now, about the command history, I just did a quick test: - starting karaf and doing some commands (for instance feature:list and feature:info ssh) - restart karaf to have a new shell session, and I have the commands in the history (I can recall with up arrow key, or display with shell:history) - I also tried with ssh and it works fine Can you describe your test case ? Thanks, Regards JB > Le 9 mai 2021 à 15:41, Steinar Bang <s...@dod.no> a écrit : > > Once I added the staging maven repository to the property > org.ops4j.pax.url.mvn.repositories in the config, i.e. > > 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 > > then my applications (that currently are running on 4.3.0, but failed on > 4.3.1) all seemed to run perfectly. > > However, console command history wasn't persisted across karaf > sessions. > > Not sure if this is a bug or an intended feature? If it is a feature, > it is possible to config the persisted history back? >
