[
https://jira.duraspace.org/browse/DS-854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=22454#comment-22454
]
Mark H. Wood edited comment on DS-854 at 9/16/11 12:34 PM:
-----------------------------------------------------------
More generally: we ought to review all dependency, tool, *and* plugin versions
for each release cycle (excluding patchlevel cycles). People make a good point
that we need to keep versions of supporting software pinned down during
development, to keep builds comparable and thus prevent the entire fabric of
existence coming unglued. But we also need to let the environment evolve when
it's convenient, and near the start of a release cycle seems like the logical
time, since things are in flux anyway. (I wonder if there's a Maven plugin for
"examine all external dependency and plugin versions, and [ suggest upgrades |
update the POM(s), with stated exclusions ]"?)
We have a checklist for the end of the release cycle, but perhaps we need one
for the beginning too.
was (Author: mwood):
More generally: we ought to review all dependency, tool, *and* plugin
versions for each release cycle (excluding patchlevel cycles). People make a
good point that we need to keep versions of supporting software pinned down
during development, to keep builds comparable and thus prevent the entire
fabric of existence coming unglued. But we also need to let the environment
evolve when it's convenient, and near the start of a release cycle seems like
the logical time, since things are in flux anyway. (I wonder if there's a
Maven plugin for "examine all external dependency and plugin versions, and [
suggest upgrades | update the POM(s), with stated exclusions ]"?)
> Licenses on non-DSpace files have been replaced by DSpace boilerplate license
> -----------------------------------------------------------------------------
>
> Key: DS-854
> URL: https://jira.duraspace.org/browse/DS-854
> Project: DSpace
> Issue Type: Task
> Components: XMLUI
> Affects Versions: 1.7.0
> Reporter: Peter Dietz
> Assignee: Mark Diggory
> Fix For: 1.8.0
>
> Attachments: Tim-dspace-pom.patch
>
>
> PeterDietz> ...crap, just noticed we stole licensing from jquery+other JS's
> == http://demo.dspace.org/xmlui/static/js/jquery-1.4.2.min.js
> <mhwood> Ah, you mean the magic maven license plugin didn't know to keep its
> hands off jquery et al.
> <mhwood> pom wants some more <exclude>s, like
> <exclude>**/jquery*.js</exclude>?
> <mhwood> <exclude>**/scriptaculous/*</exclude>
> <mhwood> Others?
> <PeterDietz> yep, I think so, otherwise we'll relicense them again..
> scriptaculous/*.js, choise-support.js,
> <PeterDietz> Mirage / ... / modernizr.*.js
> <kshepherd> iirc, there's also some duplication in jquery
> <kshepherd> a static version and a google CDN version
> <kshepherd> (in Mirage, at least)
> <mhwood> Who will tell JIRA?
> * kshepherd doesn't quite follow the licensing thing.. where are these stolen
> licenses?
> <mhwood> License plugin replaced the owners' license text with DSpace's
> boilerplate.
> <kshepherd> ohhh, eek
--
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
------------------------------------------------------------------------------
BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA
http://p.sf.net/sfu/rim-devcon-copy2
_______________________________________________
Dspace-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-devel
