[Dspace-devel] Maven optional modules
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 next release so that currently just leaves Mirage2. Personally I think a number of the features that Mirage2 introduced, such as the use of SCSS and the management of Javascript, are going to become standard for many web applications. So it may be that we should move towards integrating these features into other themes, meaning that Mirage2 could just become another theme and no longer need to be optional. Cheers, Robin. Robin Taylor Main Library University of Edinburgh -- The University of Edinburgh is a charitable body, registered in Scotland, with registration number SC005336. -- Comprehensive Server Monitoring with Site24x7. Monitor 10 servers for $9/Month. Get alerted through email, SMS, voice calls or mobile push notifications. Take corrective actions from your mobile device. http://pubads.g.doubleclick.net/gampad/clk?id=154624111&iu=/4140/ostg.clktrk ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
Re: [Dspace-devel] Maven optional modules
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). In any case, this would be a good time for LNI users to speak up. Regards, ~~helix84 Compulsory reading: DSpace Mailing List Etiquette https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette -- Comprehensive Server Monitoring with Site24x7. Monitor 10 servers for $9/Month. Get alerted through email, SMS, voice calls or mobile push notifications. Take corrective actions from your mobile device. http://pubads.g.doubleclick.net/gampad/clk?id=154624111&iu=/4140/ostg.clktrk ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
Re: [Dspace-devel] Maven optional modules
Hi helix84, Apologies, there were some discussions but I've just checked my emails and realise they were not copied to any list but just between Hardy, myself and Tim. The history is that Hardy was in the process of decommissioning the LNI module for version 5 on the assumption that nobody actually used it. It was mentioned in a weekly developer meeting at which point I intervened and asked if it could stay as we do make use of it. We have a product called PURE from Elsevier that talks to DSpace using the LNI. We spoke to Elsevier and there is one other site that has the same set up in place. A compromise was agreed that the LNI would stay but be made optional for version 5 with the expectation that it would be dropped for version 6. That having been said, I completely agree that there should be a public consultation before dropping it completely. Cheers, Robin. 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 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). In any case, this would be a good time for LNI users to speak up. Regards, ~~helix84 Compulsory reading: DSpace Mailing List Etiquette https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette -- The University of Edinburgh is a charitable body, registered in Scotland, with registration number SC005336. -- Comprehensive Server Monitoring with Site24x7. Monitor 10 servers for $9/Month. Get alerted through email, SMS, voice calls or mobile push notifications. Take corrective actions from your mobile device. http://pubads.g.doubleclick.net/gampad/clk?id=154624111&iu=/4140/ostg.clktrk ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
Re: [Dspace-devel] Maven optional modules
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. Here's that ticket: https://jira.duraspace.org/browse/DS-2124 As noted in the ticket's comments, this topic was also discussed in a developer meeting on Sept 24, at which point Robin pointed out that PURE still uses LNI: http://irclogs.duraspace.org/index.php?date=2014-09-24 Hope that helps to fill in the gaps here. - Tim On 11/14/2014 4:50 AM, TAYLOR Robin wrote: > Hi helix84, > > Apologies, there were some discussions but I've just checked my emails and > realise they were not copied to any list but just between Hardy, myself and > Tim. The history is that Hardy was in the process of decommissioning the LNI > module for version 5 on the assumption that nobody actually used it. It was > mentioned in a weekly developer meeting at which point I intervened and asked > if it could stay as we do make use of it. We have a product called PURE from > Elsevier that talks to DSpace using the LNI. We spoke to Elsevier and there > is one other site that has the same set up in place. A compromise was agreed > that the LNI would stay but be made optional for version 5 with the > expectation that it would be dropped for version 6. That having been said, I > completely agree that there should be a public consultation before dropping > it completely. > > Cheers, Robin. > > 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 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). In any case, this would be a good time for LNI > users to speak up. > > > Regards, > ~~helix84 > > Compulsory reading: DSpace Mailing List Etiquette > https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette > -- Comprehensive Server Monitoring with Site24x7. Monitor 10 servers for $9/Month. Get alerted through email, SMS, voice calls or mobile push notifications. Take corrective actions from your mobile device. http://pubads.g.doubleclick.net/gampad/clk?id=154624111&iu=/4140/ostg.clktrk ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
Re: [Dspace-devel] Maven optional modules
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 preinstall all of Mirage2's dependencies). But, for the longer term, I definitely agree we should rethink this idea. With 5.0, this was our first experience making any modules "optional", and we've obviously hit some snags in the release process because of this. Going forward (for 6.0 and beyond), we may want to consider whether we even want to allow for optional modules...or if anything that is "optional" should really just be a separate project in GitHub (similar to the plan for LNI). In that situation, users can choose to optionally download and install these extra modules into their DSpace. Just some initial thoughts here, Tim On 11/14/2014 4:03 AM, TAYLOR Robin wrote: > 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 next release > so that currently just leaves Mirage2. Personally I think a number of the > features that Mirage2 introduced, such as the use of SCSS and the management > of Javascript, are going to become standard for many web applications. So it > may be that we should move towards integrating these features into other > themes, meaning that Mirage2 could just become another theme and no longer > need to be optional. > > Cheers, Robin. > > Robin Taylor > Main Library > University of Edinburgh > -- Comprehensive Server Monitoring with Site24x7. Monitor 10 servers for $9/Month. Get alerted through email, SMS, voice calls or mobile push notifications. Take corrective actions from your mobile device. http://pubads.g.doubleclick.net/gampad/clk?id=154624111&iu=/4140/ostg.clktrk ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
Re: [Dspace-devel] Maven optional modules
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
