> > Maybe this is what you were getting at in your last paragraph.
Yes, that's right. The PR already supports the generation of DEB, MSI and DMG files, but it does not sign anything nor does it publish any file to GitHub or elsewhere. It is also very limited right now, as the proof-of-concept only implements a single component with a hardcoded Solr URL. You can have a look at https://github.com/apache/solr/pull/2605/files#diff-dfb38b08ecb575f40b9dcdaf03f13c15d6c0dd8728cd5d0a4b1c92a5fd03429e for the generation of these files. I also don't know if the client should be backwards compatible with Solr 9.X, but I believe at the moment of writing the API isn't any different from 10.0? On Thu, Jan 30, 2025 at 8:40 PM David Smiley <dsmi...@apache.org> wrote: > Very exciting! > > I'm hoping one day to run the UI independently from Solr, as an option. In > this way, those of us not yet on Solr 10 could still take advantage of it > on our desktops. Maybe this is what you were getting at in your last > paragraph. > > On Thu, Jan 30, 2025 at 2:01 AM Christos Malliaridis < > c.malliari...@gmail.com> wrote: > > > Hello everyone, > > > > The PR with an experimental, new Admin UI implementation that introduces > a > > WebAssembly app and a standalone JVM client for Solr's UI overhaul has > been > > out for a while. > > > > After resolving multiple TODOs, it is time to finalize and merge the > > changes, so that we can start adding more functionality to it and see it > in > > future releases, starting with Solr 10. > > > > Most noticeable changes: > > - The PR adds an optional "production" flag that allows two different > > builds to be executed, one for development (default) and one for > production > > builds. This is currently only used for the new module, and optimizes > build > > times for development, and the generated assets for production. > > - Solr server has a separate module for the new UI and two jetty configs > > that are dynamically included depending on build mode (prod/dev). > > - There are changes in our gradle.properties template that increase some > > JVM default resources. Make sure to include them in your local > > gradle.properties to avoid any gradle issues > > - The first builds on local machines with the changes included may > download > > a set of new libraries and generate new assets. This may be noticed > through > > longer-lasting gradle tasks. If this significantly affects your > development > > experience, please let me know. > > - There are new ignored files (/.kotlin/), which may show up as changes > > when working with multiple branches > > - If you are having issues importing or building the project during your > > review or after the merge, please share it > > - Last but not least, the new UI is linked via a menu item in the left > that > > allows users to switch from the old to the new UI (it was previously a > > button at the top right corner) > > > > I am also investigating the options we have for publishing dev builds for > > the desktop client during the experimental phase. This would decouple the > > UI development from Solr's release cycles and increase the development > > pace. If you have any information that could be useful, please let me > know. > > > > Best, > > Christos > > >
