I uploaded an RC3.
Karl

On Sat, Dec 18, 2010 at 5:04 AM, Karl Wright <daddy...@gmail.com> wrote:
> I found two other build.xml files that were missing headers.  This was
> because Grant's implementation of rat-sources was incomplete.  So I'm
> going to have to spin an RC3.
>
> I fixed rat-sources.  The current output is as follows (excuse the wrap):
>
> [rat:report] 32 Unknown Licenses
> [rat:report]
> [rat:report] *******************************
> [rat:report]
> [rat:report] Unapproved licenses:
> [rat:report]
> [rat:report]   C:/wip/mcf-release/release-0.1-branch/json/org/json/CDL.java
> [rat:report]   C:/wip/mcf-release/release-0.1-branch/json/org/json/Cookie.java
> [rat:report]   
> C:/wip/mcf-release/release-0.1-branch/json/org/json/CookieList.ja
> va
> [rat:report]   C:/wip/mcf-release/release-0.1-branch/json/org/json/HTTP.java
> [rat:report]   
> C:/wip/mcf-release/release-0.1-branch/json/org/json/HTTPTokener.j
> ava
> [rat:report]   
> C:/wip/mcf-release/release-0.1-branch/json/org/json/JSONArray.jav
> a
> [rat:report]   
> C:/wip/mcf-release/release-0.1-branch/json/org/json/JSONException
> .java
> [rat:report]   C:/wip/mcf-release/release-0.1-branch/json/org/json/JSONML.java
> [rat:report]   
> C:/wip/mcf-release/release-0.1-branch/json/org/json/JSONObject.ja
> va
> [rat:report]   
> C:/wip/mcf-release/release-0.1-branch/json/org/json/JSONString.ja
> va
> [rat:report]   
> C:/wip/mcf-release/release-0.1-branch/json/org/json/JSONStringer.
> java
> [rat:report]   
> C:/wip/mcf-release/release-0.1-branch/json/org/json/JSONTokener.j
> ava
> [rat:report]   
> C:/wip/mcf-release/release-0.1-branch/json/org/json/JSONWriter.ja
> va
> [rat:report]   C:/wip/mcf-release/release-0.1-branch/json/org/json/Test.java
> [rat:report]   C:/wip/mcf-release/release-0.1-branch/json/org/json/XML.java
> [rat:report]   
> C:/wip/mcf-release/release-0.1-branch/json/org/json/XMLTokener.ja
> va
> [rat:report]   
> C:/wip/mcf-release/release-0.1-branch/connectors/meridio/webservi
> ce/Test Harness/Installation files/Setup.Ini
> [rat:report]   
> C:/wip/mcf-release/release-0.1-branch/connectors/meridio/webservi
> ce/Test Harness/source code/TestHarness.cs
> [rat:report]   
> C:/wip/mcf-release/release-0.1-branch/connectors/meridio/webservi
> ce/Web Service/Installation files/Setup.Ini
> [rat:report]   
> C:/wip/mcf-release/release-0.1-branch/connectors/sharepoint/webse
> rvice/MCPermissionsService.csproj
> [rat:report]   
> C:/wip/mcf-release/release-0.1-branch/connectors/sharepoint/webse
> rvice/MetaCarta.snk
> [rat:report]   
> C:/wip/mcf-release/release-0.1-branch/connectors/sharepoint/webse
> rvice/Properties/AssemblyInfo.cs
> [rat:report]   
> C:/wip/mcf-release/release-0.1-branch/connectors/sharepoint/webse
> rvice/Properties/Settings.Designer.cs
> [rat:report]   
> C:/wip/mcf-release/release-0.1-branch/connectors/sharepoint/webse
> rvice/Properties/Settings.settings
> [rat:report]   
> C:/wip/mcf-release/release-0.1-branch/connectors/sharepoint/webse
> rvice/Web References/SPPermissionsService/Reference.cs
> [rat:report]   
> C:/wip/mcf-release/release-0.1-branch/connectors/sharepoint/webse
> rvice/Web References/SPPermissionsService/Reference.map
> [rat:report]   
> C:/wip/mcf-release/release-0.1-branch/framework/crawler-ui/src/ma
> in/webapp/WEB-INF/jsp/c.tld
> [rat:report]   
> C:/wip/mcf-release/release-0.1-branch/framework/crawler-ui/src/ma
> in/webapp/WEB-INF/jsp/fmt.tld
> [rat:report]   
> C:/wip/mcf-release/release-0.1-branch/framework/crawler-ui/src/ma
> in/webapp/WEB-INF/jsp/sql.tld
> [rat:report]   
> C:/wip/mcf-release/release-0.1-branch/framework/crawler-ui/src/ma
> in/webapp/WEB-INF/jsp/x.tld
> [rat:report]   
> C:/wip/mcf-release/release-0.1-branch/site/src/documentation/skin
> s/common/xslt/html/split.xsl
> [rat:report]   
> C:/wip/mcf-release/release-0.1-branch/site/src/documentation/skin
> s/lucene/note.txt
> [rat:report]
> [rat:report] *******************************
>
>
> The files under json contain the json.org license, which Apache agreed
> was OK despite rat's complaining.
> The files under framework/crawler-ui/src/main/webapp/WEB-INF/jsp are
> all from tomcat, but they were not labeled with appropriate licenses
> at that time.  Should I attach licenses to these?
> The files under site came from Grant's initial check-in of the lcf
> site; I don't know their etiology or which license should apply to
> them.
>
> The SharePoint and Meridio web service files are generated files,
> which I believe do not need licensing.  The generating tool is Visual
> Studio.
>
> Before I generate an RC3, can Grant please let me know what further
> should be done here?
>
> Thanks,
> Karl
>
>
> On Thu, Dec 16, 2010 at 7:04 PM, Karl Wright <daddy...@gmail.com> wrote:
>> There is now an RC2 on people.apache.org.
>>
>> Karl
>>
>>
>> On Thu, Dec 16, 2010 at 3:44 PM, Grant Ingersoll <gsing...@apache.org> wrote:
>>>
>>> On Dec 16, 2010, at 4:22 AM, Karl Wright wrote:
>>>
>>>> Tests are now complete for the framework changes.
>>>> Robert, Grant, please comment on CONNECTORS-128 about the future of
>>>> the FileNet and Documentum connectors.  If those connectors are deemed
>>>> acceptable, I can generate a new release candidate.
>>>>
>>>> Karl
>>>>
>>>> On Sun, Dec 12, 2010 at 6:48 PM, Karl Wright <daddy...@gmail.com> wrote:
>>>>> The preliminary change has been done, and I was able to hand-test a
>>>>> good chunk of the modified queries by hand, so I checked it in.  I
>>>>> still need to test document expiration, however, and I'd like the
>>>>> automated tests to cover the modified functionality.  I won't be able
>>>>> to get to it this until next weekend at the earliest,
>>>>>
>>>>> During the process of removing string constants from all queries, I
>>>>> also noticed that string constants are used by the FileNet and
>>>>> Documentum connectors.  These connectors have a proprietary, SQL-like
>>>>> language (I don't know what the FileNet language is called, but the
>>>>> Documentum one is called DQL.)  There does not appear to be any way to
>>>>> use the equivalent of query parameters for either sql-like language.
>>>>> If quoting is always unsafe, that would imply that neither the FileNet
>>>>> connector nor the Documentum connector could be made secure, by
>>>>> Robert's standards.  Of course, the same is going to be true of any
>>>>> FileNet or Documentum client code.
>>>>>
>>>>> Robert, Grant, do you believe I should delete these connectors?
>>>
>>> No, I don't think you should.  If that's the only way to do it, then it is 
>>> what it is and we have to go with it.
>>>
>>>
>>
>

Reply via email to