[
https://jira.duraspace.org/browse/DS-1343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=26639#comment-26639
]
Tim Donohue commented on DS-1343:
---------------------------------
Out of the four possible options listed above (in the description & in the
comments), I think the easiest ones to implement are either:
#1 - Stop shipping binary release (though this is a decision that needs to go
in front of all the Committers, as it's essentially a policy decision)
OR
#2 - Add build.properties & parent POM to the binary release (in the root
[dspace-src] directory). This one should actually just be a minor tweak to our
"assembly.xml" file
(https://github.com/DSpace/DSpace/blob/master/dspace/src/assemble/assembly.xml)
to ensure those files are added as "inclusions" (It's possible a few minor
'dspace-parent' POM changes would also be needed). To clarify, this would mean
there'd be a [dspace-src]/pom.xml and a [dspace-src]/build.properties file in
the *binary* release as well. So, the Binary release installation would be
identical to the full-source release -- the main difference being that the
"binary" release would only have one subdirectory, that being
[dspace-src]/dspace/
I think #3 (moving build.properties under [dspace-src]/dspace/) and #4
(removing build.properties altogether) are possible. But, at a glance, I worry
they'd take much more work/tweaks at this point in time, unless I'm overlooking
an easy route for either.
> Non-source zip package of DSpace 3.0-rc1 is broken/invalid
> ----------------------------------------------------------
>
> Key: DS-1343
> URL: https://jira.duraspace.org/browse/DS-1343
> Project: DSpace
> Issue Type: Bug
> Affects Versions: 3.0
> Reporter: Tim Donohue
> Priority: Blocker
> Fix For: 3.0
>
>
> Download the non-source ZIP from sourceforge:
> http://sourceforge.net/projects/dspace/files/DSpace%20Release%20Candidate/3.0-rc1/dspace-3.0-rc1-release.zip/download
> Using this "binary" release won't work, as it currently doesn't include the
> "build.properties" file (which is required for all builds).
> It seems like there's three possible fixes here:
> 1. We stop shipping a "binary" release (and just do full-source only)
> 2. OR, we modify the "binary" release so that it ships with a
> "build.properties" file & perhaps even the 'dspace-parent' POM (which may
> also be necessary) in the root directory.
> 3. OR, we move the 'build.properties' file to the [dspace-src]/dspace/
> directory (which is the only directory included in this "binary" release.
> I think I lean slightly towards #2. But, I'm not against just going with #1.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_sfd2d_oct
_______________________________________________
Dspace-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-devel
