[
https://jira.duraspace.org/browse/DS-818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=20549#action_20549
]
Mark Diggory edited comment on DS-818 at 6/3/11 2:17 AM:
---------------------------------------------------------
The first series of changes for refactoring to support asynchronous release
processes is in place, this change actually only changes the release process
only minimally.
1. dspace-parent pom moved to its own project (trunk/dspace-parent/pom/xml
(https://fisheye3.atlassian.com/browse/dspace/dspace/branches/dspace-async-release/dspace-parent/pom.xml#6415)
2. all, addon and distribution profiles are removed from parent and placed into
(https://fisheye3.atlassian.com/browse/dspace/dspace/branches/dspace-async-release/dspace/pom.xml#6415)
3. releases and builds now always executed from
(https://fisheye3.atlassian.com/browse/dspace/dspace/branches/dspace-async-release/dspace)
4. all dspace "lib" build products are managed in a separate jar module
(https://fisheye3.atlassian.com/browse/dspace/dspace/branches/dspace-async-release/dspace/modules/cli/pom.xml#6415)
cleaning up dspace/pom.xml
5. dspace-parent still holds project wide dependencyManagement, but is added
via dependency import rather than parentage.
Please review and comment on these features, we will want to test this on Maven
3.0 and 2.2.
I propose adding these features to the trunk to get the restructuring process
completed with minimal effort.
was (Author: mdiggory):
The first series of changes forrefactoring to support asynchronous release
processes is in place, this change actually only changes the release process
only minimally.
1. dspace-parent pom moved to its own project (trunk/dspace-parent/pom/xml
(https://fisheye3.atlassian.com/browse/dspace/dspace/branches/dspace-async-release/dspace-parent/pom.xml#6415)
2. all, addon and distribution profiles are removed from parent and placed into
(https://fisheye3.atlassian.com/browse/dspace/dspace/branches/dspace-async-release/dspace/pom.xml#6415)
3. releases and builds now always executed from
(https://fisheye3.atlassian.com/browse/dspace/dspace/branches/dspace-async-release/dspace)
4. all dspace "lib" build products are managed in a separate jar module
(https://fisheye3.atlassian.com/browse/dspace/dspace/branches/dspace-async-release/dspace/modules/cli/pom.xml#6415)
cleaning up dspace/pom.xml
5. dspace-parent still holds project wide dependencyManagement, but is added
via dependency import rather than parentage.
Please review and comment on these features, we will want to test this on Maven
3.0 and 2.2.
I propose adding these features to the trunk to get the restructuring process
completed with minimal effort.
> Asynchronous Release
> --------------------
>
> Key: DS-818
> URL: https://jira.duraspace.org/browse/DS-818
> Project: DSpace
> Issue Type: New Feature
> Components: Documentation, DSpace API, JSPUI, Language Packs, LNI,
> OAI-PMH, REST API (experimental), Solr, SWORD, Unit Testing Framework, XMLUI
> Reporter: Mark Diggory
> Assignee: Mark Diggory
> Priority: Major
> Fix For: 1.8.0
>
>
> Asynchronous Release: Asynchronous Release is change in the DSpace release
> process and version numbering process on modules within the DSpace trunk to
> allow more flexibility adding prebuilt Addon modules into DSpace.
> Goals
> The primary goal of Async release is to break the the authoritative grip that
> dspace-parent has on the version assignment and dependencyManagement in the
> DSpace trunk modules such that:
> Make the build in the DSpace Modules Source Tree dependent on a specific
> dspace-api and dspace-xmlui-api versions. Specifically, dspace-statistics and
> dspace-discovery
> Make a packaged release of DSpace that includes a combination of Trunk and
> Module projects.
> More easily package releases of DSpace cyclically while allowing minor
> updates of core modules to occur more often, to easily provide a minor update
> path for DSpace.
> View wiki page for further details.
> https://wiki.duraspace.org/display/DSPACE/Asynchronous+Release
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.duraspace.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
Simplify data backup and recovery for your virtual environment with vRanger.
Installation's a snap, and flexible recovery options mean your data is safe,
secure and there when you need it. Discover what all the cheering's about.
Get your free trial download today.
http://p.sf.net/sfu/quest-dev2dev2
_______________________________________________
Dspace-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-devel
