[
https://jira.duraspace.org/browse/DS-1144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=24499#comment-24499
]
Tim Donohue commented on DS-1144:
---------------------------------
Hi Mark,
Finally getting back to this ticket.
Again, I do like nearly all the ideas you have here. I like the direction this
is going in.
I guess the only outstanding question I have is around the treatment of
'dspace-stats' and 'dspace-discovery-solr' (which seem to be similar in a lot
of ways, but are treated differently, at least in terms of naming).
As you mentioned, there is hope that in the future there will be an option to
use either Solr or Elastic-Search for 'dspace-stats' and 'dspace-discovery'.
This makes sense, but it sounds like you are then suggesting that once
Elastic-Search is an option we'd have a folder structure like:
[src]/dspace-stats-solr/
[src]/dspace-stats-elastic/
[src]/dspace-discovery-solr/
[src]/dspace-discovery-elastic/
My question is, should we just let those all end up sitting at the "root"
level? Or do we want to rethink this into a structure more like:
[src]/dspace-stats/dspace-stats-solr/
[src]/dspace-stats/dspace-stats-elastic/
[src]/dspace-discovery/dspace-discovery-solr/
[src]/dspace-discovery/dspace-discovery-elastic/
Or, potentially for the time being, just remove all mentions of Solr or Elastic
search (and as necessary in the future, revisit this should we ever release
DSpace Stats & Discovery with multiple options).
[src]/dspace-stats/src/main/java/
[src]/dspace-discovery/src/main/java/
Beyond that, I think this is looking good. I just want us to be consistent
with how we are treating "-discovery" and "-stats". We should either suffix
them both with "-solr" or suffix neither with "-solr" (and potentially revisit
it later on, if we decide to release an Elastic-Search option)
> Maven Project Consolidation
> ---------------------------
>
> Key: DS-1144
> URL: https://jira.duraspace.org/browse/DS-1144
> Project: DSpace
> Issue Type: Improvement
> Reporter: Mark Diggory
> Assignee: Mark Diggory
> Priority: Major
> Fix For: 3.0
>
>
> https://wiki.duraspace.org/display/DSPACE/Maven+Project+Consolidation
> This project would reorganize and consolidate some of the maven project
> hierarchy to reduce the number of maven projects neccessary to operate DSpace.
> Benefits: Reduce the number of maven projects in DSpace "Core" from 39 to 19.
> GitHub Branch for this is located here:
> https://github.com/DSpace/DSpace/tree/maven-project-consolidation
> This project would consolidate:
> dspace-xmlui
> dspace-xmlui-wing
> src/main/java
> dspace-xmlui-api
> src/main/java
> src/main/resources
> dspace-xmlui-webapp
> src/main/resources
> src/main/webapp
> and it would reduce it down to
> dspace-xmlui
> src/main/java
> src/main/resources
> src/main/webapp
> We would utilize the current model found in dspace-swordv2
> (http://scm.dspace.org/svn/repo/dspace/trunk/dspace/modules/swordv2)
> dspace-swordv2
> src/main/java
> src/main/resources
> src/main/webapp
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.duraspace.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
Better than sec? Nothing is better than sec when it comes to
monitoring Big Data applications. Try Boundary one-second
resolution app monitoring today. Free.
http://p.sf.net/sfu/Boundary-dev2dev
_______________________________________________
Dspace-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-devel
