[
https://jira.duraspace.org/browse/DS-1144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=24501#comment-24501
]
Tim Donohue commented on DS-1144:
---------------------------------
I may be missing something here then. My comments above are based on the fact
that I see Stats & Discovery as very "similar" modules (in the same way that
all the webapps are similar in structure). They both currently have Solr
implementations & in the future may or may not support other options (like
Elastic Search).
The oddity (to me), is that despite those similarities, as far as I can tell,
the Stats code is all in [src]/dspace-stats/ whereas the Discovery code is
split into [src]/dspace-api (Provider) and [src]/dspace-discovery-solr/
(Implementation).
I guess my assumption was that we should be treating these both similar (just
like we've restructured all the webapps in a similar fashion). The point of
this whole reorg is obviously to simplify our Maven structure (in order to ease
in new/novice developers learning how to work with DSpace).
In my mind this makes we wonder whether all the Discovery stuff shouldn't just
be in [src]/dspace-discovery (both Provider & implemenation). But, maybe
there's a reason that this won't work well?
The key point here is that -- if I'm confused about why Discovery & Stats seem
to have taken different paths in terms of "where the code lives", than I wonder
what newer developers will run into.
> 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
