Hi all,
Was away yesterday so just read the notes from the developer meeting. With
regards to our Maven optional modules, rather than finding a way to accommodate
them in our Pom's should we maybe be looking to not have optional modules? The
expectation is that the LNI will be dropped for the
Hi Robin,
last year we talked about making LNI optional because it has only a
few users, so the reason was to reduce build times. I don't remember
us talking about dropping it (confirmed by a quick search in IRC
logs). I don't see a reason to drop something that we have that is a
standard
Regarding the LNI discussions, there's a ticket related to removing LNI
from default DSpace. The suggestion is that we move it to its own
separate GitHub project (and folks who want to use and maintain it still
can). As far as I'm aware though, we have little (if any) users of LNI
these days.
Robin and all,
Regarding the optional modules: It seems like in 5.0, we have to move
forward with these modules as optional. At least to me, it seems like
it'd require a lot of work/time to make Mirage2 required -- plus it
drastically lengthens the time it takes to build DSpace (unless you
I would rather mirage2 be a regular (compiled) xmlui theme. I rarely add
new JS libraries, and when I do, I can include them via script src. For
CSS/JS minification, you could use a service like cloudflare cdn to serve
compiled/cached versions of your sites. I guess, the old flow allowed me to
