I could not any GPL+Classpath license in the mix.
GitHub history
<https://github.com/geotools/geotools/commits/master/licenses/GPL%2BCP> of
the file shows:
- GEOT-3397, changing XSD.qName to avoid reflection …
jdeolive authored on Jan 26, 2011
Which looks to date back to svn times? git-svn-id:
http://svn.osgeo.org/geotools/trunk@36490
e5c1c795-43da-0310-a71f-fac65c449510
Looking at the Jira issue: https://jira.codehaus.org/browse/GEOT-3397 did
not show much.
Justin do you have any comment here? It is possibly a reflection of cutting
and pasting some Java QName code....
Jody Garnett
On Wed, Sep 24, 2014 at 11:06 AM, Jody Garnett <[email protected]>
wrote:
> No need to republish the jars Ian, in the past when we missed things like
> this I download the zip, made the correction, and uploaded the result to
> source forge.
>
> We should check where that GPL license came from - I hope it is simply a
> mistake (or from a community module that has not been through QA yet).
>
> Jody Garnett
>
> On Wed, Sep 24, 2014 at 9:46 AM, Ian Turton <[email protected]> wrote:
>
>> I can fix the typos and minor changes (like noting you need 1.7) tomorrow
>> and repush the jars. While I finish up the GeoServer build.
>>
>> Licence changes and killing abstract data store probably need to be done
>> on master and back ported to 12.1 ?
>>
>> Ian
>> (who has spent the entire afternoon in project meetings and whose brain
>> is fried)
>>
>> On 24 September 2014 17:40, Andrea Aime <[email protected]>
>> wrote:
>>
>>> Hi Jody,
>>> since this large delay is posing a threat to our monthly time boxed
>>> release
>>> model, shall we just go ahead with the release and fix the two things
>>> you pointed to in the next release?
>>>
>>> Cheers
>>> Andrea
>>>
>>>
>>> On Wed, Sep 24, 2014 at 6:22 PM, Jody Garnett <[email protected]>
>>> wrote:
>>>
>>>> Morning Ian:
>>>>
>>>> Taking a moment to test geotools-12.0-project.zip.
>>>>
>>>> README.html
>>>> - Got one thing to change here, all the README links need to point to
>>>> "stable" rather than latest. I guess this should of been done for the RC1
>>>> when we branched off.
>>>> - README.html is good about indicating Java 7 is now required.
>>>>
>>>> README.md
>>>> CONTRIBUTING.md
>>>> - Probably not needed for project download ...
>>>> - I think we grab this straight from GitHub tag now right so may not be
>>>> a way to avoid it
>>>>
>>>> pom.xml does
>>>> - Does not included any snapshot dependencies - good.
>>>>
>>>> licenses
>>>> - There is a GPL+CP license here - that is not cool where does it come
>>>> from?
>>>> - everything else looks okay
>>>>
>>>> mvn install -Dall
>>>> - BUILD SUCCESS 14:10.894s
>>>>
>>>> docs
>>>> - build/install/jdk.html <-- needs to say Java 7 is required
>>>> - tutorial/abstractdatastore.html <-- kill me :)
>>>>
>>>> So two problems
>>>> 1) GPL_CP needs to be removed, have to hunt down what module added it
>>>> 2) README.html needs links changed to stable
>>>>
>>>>
>>>> Jody Garnett
>>>>
>>>>
>>>> ------------------------------------------------------------------------------
>>>> Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
>>>> Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
>>>> Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
>>>> Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
>>>>
>>>> http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
>>>> _______________________________________________
>>>> GeoTools-Devel mailing list
>>>> [email protected]
>>>> https://lists.sourceforge.net/lists/listinfo/geotools-devel
>>>>
>>>>
>>>
>>>
>>> --
>>> ==
>>> GeoServer Professional Services from the experts! Visit
>>> http://goo.gl/NWWaa2 for more information.
>>> ==
>>>
>>> Ing. Andrea Aime
>>> @geowolf
>>> Technical Lead
>>>
>>> GeoSolutions S.A.S.
>>> Via Poggio alle Viti 1187
>>> 55054 Massarosa (LU)
>>> Italy
>>> phone: +39 0584 962313
>>> fax: +39 0584 1660272
>>> mob: +39 339 8844549
>>>
>>> http://www.geo-solutions.it
>>> http://twitter.com/geosolutions_it
>>>
>>> *AVVERTENZE AI SENSI DEL D.Lgs. 196/2003*
>>>
>>> Le informazioni contenute in questo messaggio di posta elettronica e/o
>>> nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il
>>> loro utilizzo è consentito esclusivamente al destinatario del messaggio,
>>> per le finalità indicate nel messaggio stesso. Qualora riceviate questo
>>> messaggio senza esserne il destinatario, Vi preghiamo cortesemente di
>>> darcene notizia via e-mail e di procedere alla distruzione del messaggio
>>> stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso,
>>> divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od
>>> utilizzarlo per finalità diverse, costituisce comportamento contrario ai
>>> principi dettati dal D.Lgs. 196/2003.
>>>
>>>
>>>
>>> The information in this message and/or attachments, is intended solely
>>> for the attention and use of the named addressee(s) and may be confidential
>>> or proprietary in nature or covered by the provisions of privacy act
>>> (Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection
>>> Code).Any use not in accord with its purpose, any disclosure, reproduction,
>>> copying, distribution, or either dissemination, either whole or partial, is
>>> strictly forbidden except previous formal approval of the named
>>> addressee(s). If you are not the intended recipient, please contact
>>> immediately the sender by telephone, fax or e-mail and delete the
>>> information in this message that has been received in error. The sender
>>> does not give any warranty or accept liability as the content, accuracy or
>>> completeness of sent messages and accepts no responsibility for changes
>>> made after they were sent or for other risks which arise as a result of
>>> e-mail transmission, viruses, etc.
>>>
>>> -------------------------------------------------------
>>>
>>
>>
>>
>> --
>> Ian Turton
>>
>
>
------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
_______________________________________________
GeoTools-Devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel
