[
https://issues.apache.org/jira/browse/SOLR-14414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17928885#comment-17928885
]
Chris M. Hostetter commented on SOLR-14414:
-------------------------------------------
The jetbrains issue was just an example of someone saying these types of
problems can be resolved by pinning nodejs - the versions are certainly
different ad older.
I think expecting people to upgrade their entire host OS in order to build solr
– just because one (still experimental) optional sub-project needs nodejs – is
a big ask. It's one thing to say "this project requires jdk21" because you
easily have multiple JDKs on the same bod, but you can't easily have multiple
GLIBC versions.
(and remember, this isn't just me: [we keep seeing jenkins
failures|https://ci-builds.apache.org/job/Solr/job/Solr-Docker-Test-main/630/console#gradle-task-76]
because some jenkins workers aren't up to date with the latest greatest GLIBC
either)
----
Given how much complexity & Host OS requirements are involved in
building/testing the new UI (you also have to have {{chrome}} installed
somewhere in your PATH to run tests correct?) , I think ideally there should be
a simple gradle property that completely enables/disables all tasks in the
{{:solr:ui}} subproject so they never try to run (and never run any of their
dependency tasks in the top level build (although i'm also not really sure i
understand why {{kotlinNpmInstall}} needs to be a be level task instead of a
task in the {{:solr:ui}} subproject?)
> New Admin UI
> ------------
>
> Key: SOLR-14414
> URL: https://issues.apache.org/jira/browse/SOLR-14414
> Project: Solr
> Issue Type: Improvement
> Components: Admin UI
> Affects Versions: 9.0
> Reporter: Marcus Eagan
> Priority: Major
> Labels: pull-request-available
> Attachments: QueryUX-SolrAdminUIReboot.mov
>
> Time Spent: 10h
> Remaining Estimate: 0h
>
> We have had a lengthy discussion in the mailing list about the need to build
> a modern UI that is both more security and does not depend on deprecated, end
> of life code. In this ticket, I intend to familiarize the community with the
> efforts of the community to do just that that. While we are nearing feature
> parity, but not there yet as many have suggested we could complete this task
> in iterations, here is an attempt to get the ball rolling. I have mostly
> worked on it in weekend nights on the occasion that I could find the time.
> Angular is certainly not my specialty, and this is my first attempt at using
> TypeScript besides a few brief learning exercises here and there. However, I
> will be engaging experts in both of these areas for consultation as our
> community tries to pull our UI into another era.
> Many of the components here can improve. One or two them need to be
> rewritten, and there are even at least three essential components to the app
> missing, along with some tests. A couple other things missing are the V2 API,
> which I found difficult to build with in this context because it is not
> documented on the web. I understand that it is "self-documenting," but the
> most easy-to-use APIs are still documented on the web. Maybe it is entirely
> documented on the web, and I had trouble finding it. Forgive me, as that
> could be an area of assistance. Another area where I need assistance is
> packaging this application as a Solr package. I understand this app is not in
> the right place for that today, but it can be. There are still many
> improvements to be made in this Jira and certainly in this code.
> The project is located in {{lucene-solr/solr/webapp2}}, where there is a
> README for information on running the app.
> The app can be started from the this directory with {{npm start}} for now. It
> can quickly be modified to start as a part of the typical start commands as
> it approaches parity. I expect there will be a lot of opinions. I welcome
> them, of course. The community input should drive the project's success.
> Discussion in mailing list:
> https://mail-archives.apache.org/mod_mbox/lucene-dev/202004.mbox/%3CCAF76exK-EB_tyFx0B4fBiA%3DJj8gH%3Divn2Uo6cWvMwhvzRdA3KA%40mail.gmail.com%3E
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
