to summarize what I just did...
I took Aarons wonderful recommendation posted to his blog and implemented it
on the dspace-services, dspace-solr and dspace-solr-stats projects... we can
use it as well on the dspace source tree with some minor changes to add
dspace-pom as the parent of the dspace-parent pom.
http://aaronz-sakai.blogspot.com/2009/08/easy-license-headers-with-maven.html
I've created a template for licensing in java, xml, jsp, html, property, etc
files. running the license:format task will walk all the source and update
licenses appropriately.
Caution, this will touch many many files and change them. I would recommend
not doing it in the trunk until we are ready to officially release 1.6.0
(not before, not after) because it will seriously increase conflicts on svn
merging and applying patches. We have much work to get done before 1.6.0.
Maybe add it as a jira task and set a target time-frame of dependency for ti
to happen just prior to 1.6.0 release.
Note, the new license blurb I attached to the dspace-service etc uses a much
smaller boilerplate text and references to the license externally,
https://scm.dspace.org/svn/repo/licenses/LICENSE_HEADER
this reduces the requirement to change all the embedded licenses when the
canonical license has changes.
Mark
On Tue, Oct 6, 2009 at 1:40 PM, Bradley McLean <[email protected]> wrote:
> Good point. I'll check in a rewrite with the reference changed, thanks.
>
> Are you aware of a magic reliable maven plugin for this construction? The
> ones I've seen were rather fragile.
>
> Mark Diggory wrote:
>
>> Brad,
>>
>> This clause isn't very relevant anymore...
>>
>> DSpace uses third-party libraries which may be distributed under
>> different licenses to the above. These licenses are located in
>> the lib/licenses directory. You must agree to the terms of these
>> licenses, in addition to the above DuraSpace source code license, in
>> order to use this software.
>>
>>
>> These license are not in the lib directory anymore. And since everything
>> is distributed over maven, we can either use maven to construct a Licenses
>> directory or just do away the reference to the directory within the clause?
>>
>> Mark
>>
>> On Tue, Oct 6, 2009 at 6:51 AM, <[email protected] <mailto:
>> [email protected]>> wrote:
>>
>> Author: bradmc
>> Date: Tue Oct 6 13:51:02 2009
>> New Revision: 4369
>>
>> Log:
>> Update license to DuraSpace.
>>
>>
>> Modified:
>> licenses/LICENSE.txt
>>
>> Modified: licenses/LICENSE.txt
>>
>>
>> ==============================================================================
>> --- licenses/LICENSE.txt (original)
>> +++ licenses/LICENSE.txt Tue Oct 6 13:51:02 2009
>> @@ -1,4 +1,4 @@
>> -Copyright (c) 2002-2009, The Duraspace Foundation. All rights
>> reserved.
>> +Copyright (c) 2002-2009, DuraSpace. All rights reserved.
>>
>> Redistribution and use in source and binary forms, with or without
>> modification, are permitted provided that the following
>> conditions are
>> @@ -11,9 +11,10 @@
>> notice, this list of conditions and the following disclaimer in the
>> documentation and/or other materials provided with the distribution.
>>
>> -- Neither the name of the Duraspace Foundation nor the names of its
>> -contributors may be used to endorse or promote products derived from
>> -this software without specific prior written permission.
>> +- Neither the name DuraSpace nor the name of the DSpace Foundation
>> +nor the names of its contributors may be used to endorse or promote
>> +products derived from this software without specific prior written
>> +permission.
>>
>> THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
>> ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
>> @@ -26,4 +27,11 @@
>> ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR
>> TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT
>> OF THE
>> USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH
>> -DAMAGE.
>> \ No newline at end of file
>> +DAMAGE.
>> +
>> +
>> +DSpace uses third-party libraries which may be distributed under
>> +different licenses to the above. These licenses are located in
>> +the lib/licenses directory. You must agree to the terms of these
>> +licenses, in addition to the above DSpace source code license, in
>> +order to use this software.
>>
>>
>>
>> ------------------------------------------------------------------------------
>> Come build with us! The BlackBerry® Developer Conference in SF, CA
>> is the only developer event you need to attend this year.
>> Jumpstart your
>> developing skills, take BlackBerry mobile applications to market
>> and stay
>> ahead of the curve. Join us from November 9-12, 2009. Register
>> now!
>> http://p.sf.net/sfu/devconf
>> _______________________________________________
>> DSpace-changelog mailing list
>> [email protected]
>> <mailto:[email protected]>
>> https://lists.sourceforge.net/lists/listinfo/dspace-changelog
>>
>>
>> ------------------------------------------------------------------------
>>
>>
>> ------------------------------------------------------------------------------
>> Come build with us! The BlackBerry® Developer Conference in SF, CA
>> is the only developer event you need to attend this year. Jumpstart your
>> developing skills, take BlackBerry mobile applications to market and stay
>> ahead of the curve. Join us from November 9-12, 2009. Register now!
>> http://p.sf.net/sfu/devconf
>> ------------------------------------------------------------------------
>>
>> _______________________________________________
>> Dspace-devel mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/dspace-devel
>>
>>
>
>
------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Dspace-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-devel