I'd say if we have to do that, we should create our own classes and paste
the code there under ObjectStyle license, and put the VPP license in our
third party liceses directory under docs.
My reasoning is that if we have a Java class under our source tree, it is
a part of Cayenne and we will be maintaining it. Otherwise it should be
imported as a binary jar.
BTW, how many Java classes from VPP are you planning to import, and what
benefit they add to cgen (FileSets and mappers I would imagine)?
Andrus
> I'd like to incorporate some of the VPP -- http://vpp.sourceforge.net/
> -- source code into our cgen task.
> VPP is licensed as BSD (license below). Because it'd make configuring
> cgen more complicated to keep it as a separate jar and because we don't
> need the whole thing, I'd like to propose incorporating parts of it
> into cayenne as org.objectstyle.foundrylogic.vpp or something like that
> (the distributed package is foundrylogic.vpp).
>
> I'd leave the license as-is for the files that are simply repackaged.
>
> Does this make sense?
>
> Or would it be better to handle it some other way?
>
> -Mike
>
> =====================================================
> /*
> Copyright (c) 2003, FoundryLogic, LLC
> All rights reserved.
>
> Redistribution and use in source and binary forms, with or without
> modification, are permitted provided that the following conditions are
> met:
>
> * Redistributions of source code must retain the above copyright
> notice, this list of conditions and the following disclaimer.
>
> * Redistributions in binary form must reproduce the above copyright
> notice, this list of conditions and the following disclaimer in the
> documentation and/or other materials provided with the distribution.
>
> * Neither the name of FoundryLogic, LLC 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 LIMITED
> TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A
> PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
> OWNER
OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
> SPECIAL,
EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
> LIMITED TO,
PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
> DATA, OR
PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND 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.
>
> This product includes software developed by the
> Apache Software Foundation (http://www.apache.org/).
> */
> =====================================================
This archive was generated by hypermail 2.0.0 : Mon May 23 2005 - 16:16:53 EDT