[
https://issues.apache.org/jira/browse/SOLR-8035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14987086#comment-14987086
]
Upayavira commented on SOLR-8035:
---------------------------------
Just to note, I'm mulling on whether we might actually *need* a build process.
We have two conflicting needs:
* development time: change a file - commit it
* build time: minify/merge/etc
The latter currently isn't being done at all. There are many JS tools out there
that do the equivalent of Ivy dependency management, and others that minify
CSS/JS/HTML and then merge those files into a smaller number of files, such
that the overall HTTP payload of the UI could be substantially reduced. For
local loads this has never been an issue, but I have been to visit hosted Solr
servers where the UI fails to load due to poor network connectivity.
Ideally, "ant run" would run the UI in place, whereas "ant server" would
execute a build process and produce minfied files/etc.
> Move solr/webapp to solr/server/solr-webapp
> -------------------------------------------
>
> Key: SOLR-8035
> URL: https://issues.apache.org/jira/browse/SOLR-8035
> Project: Solr
> Issue Type: Bug
> Components: UI
> Reporter: Erik Hatcher
> Assignee: Erik Hatcher
> Priority: Critical
> Fix For: 5.4, Trunk
>
> Attachments: SOLR-8035.patch
>
>
> Let's move solr/webapp *source* files to their final actual distro
> destination. This facilitates folks editing the UI in real-time (save
> change, refresh in browser) rather than having to "stop, ant server, restart"
> to see a change.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
