lucene-solr-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yago Riveiro" <>
Subject Re: How best to fork Solr for enhancement
Date Tue, 23 Dec 2014 15:32:19 GMT
There is other options like Ember or Backbone, either way AngularJS is well adopted.

Alexandre, your question is about the radical change between versions?

In some way this shows progress and support to the framework.

Other good reason is that AngularJS has a ton of components ready to use.

/Yago Riveiro

On Tuesday, Dec 23, 2014 at 3:10 pm, Alexandre Rafalovitch <>, wrote:
Semi Off Topic, but is AngularJS the best next choice, given the

version 2 being so different from version 1?




Sign up for my Solr resources newsletter at

On 23 December 2014 at 06:52, Upayavira <> wrote:

> Hi,


> I've (hopefully) made some time to do some work on the Solr Admin UI

> (convert it to AngularJS). I plan to do it on a clone of the lucene-solr

> project at GitHub.


> Before I dive too thoroughly into this, I wanted to see if there were

> any best practices that would make it easier to back-port these changes

> into SVN should I actually succeed at producing something useful. Is it

> enough just to make a branch called SOLR-5507 and start committing my

> changes there?


> Periodically, I'll zip up the relevant bits and attach them to the JIRA

> ticket.




> Upayavira
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message