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
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
ma...@gmail.com on behalf of helix84
>
> Sent: 14 November 2014 10:25
> To: TAYLOR Robin
> Cc: dspace-devel@lists.sourceforge.net
> Subject: Re: [Dspace-devel] Maven optional modules
>
> Hi Robin,
>
> last year we talked about making LNI optional because it has only a
Robin Taylor
Main Library
University of Edinburgh
From: ivan.ma...@gmail.com on behalf of helix84
Sent: 14 November 2014 10:25
To: TAYLOR Robin
Cc: dspace-devel@lists.sourceforge.net
Subject: Re: [Dspace-devel] Maven optional modules
Hi Robin,
last year we t
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 (WebDAV)
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 n
