[
https://jira.duraspace.org/browse/DS-1144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=24502#comment-24502
]
Mark Diggory commented on DS-1144:
----------------------------------
I don't think your far off from my perspective. My consolidation goal is based
on libraries that are common across all apps canbe consolidated into
dspace-api. And it is better to "extract" the providers of services (Search,
Browse, Discovery, Stats, MediaFilters, Consumers, DAO, etc) out of and make
them dependent on dspace-api
dspace-common was going to be the project that assembled all these dependencies
back together so that you did not need to add them all to each and every webapp.
(Note at one time, I was trying to make the actual dspace assembly project this
common maven project, but its difficult to combine assembly and jar projects
into one unit).
The reason dspace-stats still is outside is just the dspace-stats is not as as
cleanly separated into service and provider as dspace-discovery is. It needs
to be separated apart into stats service and stats solr provider to keep the
solr parts out of dspace-api (if that is even an issue).
-----
Even if you and I agree is our long term goal to break apart dspace-api into
content/core and separate apps, the rest of the committers group isn't fully
buying into it, there is not general trend emerging to separate these out
(unless theres some big project over in RichardR's space I'm not aware of, but
thats another story). This is why I started folding everything together again,
For instance, if we want to replace DSQuery and Browse with Discovery, I think
it important that we get the code organized into one project and do it there.
This either means that we would alter XMLUI and JSPUI code to dormally remove
Search/Browse in favor of Discovery, or we will reimplement DSQuery and Browse
as services that reuse the Solr/Discovery Provider.
> 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
