[Lucene.Net] [jira] [Resolved] (LUCENENET-404) Improve brand logo design
[ https://issues.apache.org/jira/browse/LUCENENET-404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Troy Howard resolved LUCENENET-404. --- Resolution: Fixed Uploaded the artifacts in r1153264 Improve brand logo design - Key: LUCENENET-404 URL: https://issues.apache.org/jira/browse/LUCENENET-404 Project: Lucene.Net Issue Type: Sub-task Components: Project Infrastructure Reporter: Troy Howard Assignee: Troy Howard Priority: Minor Labels: branding, logo Attachments: lucene-alternates.jpg, lucene-medium.png, lucene-net-logo-display.jpg The existing Lucene.Net logo leaves a lot to be desired. We'd like a new logo that is modern and well designed. To implement this, Troy is coordinating with StackOverflow/StackExchange to manage a logo design contest, the results of which will be our new logo design. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[Lucene.Net] [jira] [Resolved] (LUCENENET-437) Port Contrib.Shingle from Java
[ https://issues.apache.org/jira/browse/LUCENENET-437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Troy Howard resolved LUCENENET-437. --- Resolution: Fixed Fix Version/s: (was: Lucene.Net 2.9.4g) Port Contrib.Shingle from Java -- Key: LUCENENET-437 URL: https://issues.apache.org/jira/browse/LUCENENET-437 Project: Lucene.Net Issue Type: Task Components: Lucene.Net Contrib, Lucene.Net Test Affects Versions: Lucene.Net 2.9.4, Lucene.Net 2.9.4g Reporter: Troy Howard Assignee: Troy Howard Priority: Minor Fix For: Lucene.Net 2.9.4 Port Contrib.Shingle from Java -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[Lucene.Net] [jira] [Commented] (LUCENENET-437) Port Contrib.Shingle from Java
[ https://issues.apache.org/jira/browse/LUCENENET-437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13067328#comment-13067328 ] Troy Howard commented on LUCENENET-437: --- I assume you're referring to the issue found here: http://blogs.msdn.com/b/ericlippert/archive/2011/07/12/what-curious-property-does-this-string-have.aspx Port Contrib.Shingle from Java -- Key: LUCENENET-437 URL: https://issues.apache.org/jira/browse/LUCENENET-437 Project: Lucene.Net Issue Type: Task Components: Lucene.Net Contrib, Lucene.Net Test Affects Versions: Lucene.Net 2.9.4, Lucene.Net 2.9.4g Reporter: Troy Howard Assignee: Troy Howard Priority: Minor Fix For: Lucene.Net 2.9.4, Lucene.Net 2.9.4g Port Contrib.Shingle from Java -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[Lucene.Net] [jira] [Issue Comment Edited] (LUCENENET-437) Port Contrib.Shingle from Java
[ https://issues.apache.org/jira/browse/LUCENENET-437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13067328#comment-13067328 ] Troy Howard edited comment on LUCENENET-437 at 7/18/11 9:56 PM: I assume you're referring to the issue found here: http://blogs.msdn.com/b/ericlippert/archive/2011/07/12/what-curious-property-does-this-string-have.aspx I am aware of that issue.. however the implementation in ListComparer is exactly the behaviour of Java. I copied the implementation straight from the Java docs. http://download.oracle.com/javase/1.4.2/docs/api/java/util/List.html#hashCode() The issue you're describing is more of a problem with the .NET implementation of GetHashcode() rather than the correctness of using hashcode for comparison. See (for implementation): http://www.dotnetperls.com/gethashcode Anyhow, I'll update this to use SupportClass.EquatableList since it allows the code to pass unit tests, and also not have that particular problem. was (Author: thoward37): I assume you're referring to the issue found here: http://blogs.msdn.com/b/ericlippert/archive/2011/07/12/what-curious-property-does-this-string-have.aspx Port Contrib.Shingle from Java -- Key: LUCENENET-437 URL: https://issues.apache.org/jira/browse/LUCENENET-437 Project: Lucene.Net Issue Type: Task Components: Lucene.Net Contrib, Lucene.Net Test Affects Versions: Lucene.Net 2.9.4, Lucene.Net 2.9.4g Reporter: Troy Howard Assignee: Troy Howard Priority: Minor Fix For: Lucene.Net 2.9.4, Lucene.Net 2.9.4g Port Contrib.Shingle from Java -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[Lucene.Net] [jira] [Commented] (LUCENENET-437) Port Contrib.Shingle from Java
[
https://issues.apache.org/jira/browse/LUCENENET-437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13067370#comment-13067370
]
Troy Howard commented on LUCENENET-437:
---
From the docs for List.hashCode():
Returns the hash code value for this list. The hash code of a list is defined
to be the result of the following calculation:
hashCode = 1;
Iterator i = list.iterator();
while (i.hasNext()) {
Object obj = i.next();
hashCode = 31*hashCode + (obj==null ? 0 : obj.hashCode());
}
This ensures that list1.equals(list2) implies that
list1.hashCode()==list2.hashCode() for any two lists, list1 and list2, as
required by the general contract of Object.hashCode.
The contract intended for Object.hashCode() specifically includes that
object1.equals(object2) == object1.hashCode().equals(object2.hashCode()).
This is stated here:
http://download.oracle.com/javase/1.4.2/docs/api/java/lang/Object.html#hashCode()
Quoted:
public int hashCode()
Returns a hash code value for the object. This method is supported for the
benefit of hashtables such as those provided by java.util.Hashtable.
The general contract of hashCode is:
- Whenever it is invoked on the same object more than once during an execution
of a Java application, the hashCode method must consistently return the same
integer, provided no information used in equals comparisons on the object is
modified. This integer need not remain consistent from one execution of an
application to another execution of the same application.
- If two objects are equal according to the equals(Object) method, then calling
the hashCode method on each of the two objects must produce the same integer
result.
- It is not required that if two objects are unequal according to the
equals(java.lang.Object) method, then calling the hashCode method on each of
the two objects must produce distinct integer results. However, the programmer
should be aware that producing distinct integer results for unequal objects may
improve the performance of hashtables.
As much as is reasonably practical, the hashCode method defined by class Object
does return distinct integers for distinct objects. (This is typically
implemented by converting the internal address of the object into an integer,
but this implementation technique is not required by the JavaTM programming
language.)
Again, this is Java's code contract, which was in some cases, improperly
implemented in the .NET CLR.
Port Contrib.Shingle from Java
--
Key: LUCENENET-437
URL: https://issues.apache.org/jira/browse/LUCENENET-437
Project: Lucene.Net
Issue Type: Task
Components: Lucene.Net Contrib, Lucene.Net Test
Affects Versions: Lucene.Net 2.9.4, Lucene.Net 2.9.4g
Reporter: Troy Howard
Assignee: Troy Howard
Priority: Minor
Fix For: Lucene.Net 2.9.4, Lucene.Net 2.9.4g
Port Contrib.Shingle from Java
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[Lucene.Net] [jira] [Commented] (LUCENENET-437) Port Contrib.Shingle from Java
[ https://issues.apache.org/jira/browse/LUCENENET-437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13067373#comment-13067373 ] Troy Howard commented on LUCENENET-437: --- Although, according to that definition, .NET's implementation is allowed. It's just not a good idea for exactly the reasons we've been discussing. Port Contrib.Shingle from Java -- Key: LUCENENET-437 URL: https://issues.apache.org/jira/browse/LUCENENET-437 Project: Lucene.Net Issue Type: Task Components: Lucene.Net Contrib, Lucene.Net Test Affects Versions: Lucene.Net 2.9.4, Lucene.Net 2.9.4g Reporter: Troy Howard Assignee: Troy Howard Priority: Minor Fix For: Lucene.Net 2.9.4, Lucene.Net 2.9.4g Port Contrib.Shingle from Java -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[Lucene.Net] [jira] [Commented] (LUCENENET-437) Port Contrib.Shingle from Java
[ https://issues.apache.org/jira/browse/LUCENENET-437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13067384#comment-13067384 ] Troy Howard commented on LUCENENET-437: --- Well, it does, because of Object.hashCode()'s definition. It ensures equality, but does not ensure inequality. In other words, the contract ensures that for all types, this passes: Assert.IsTrue(object1.equals(object2)) Assert.IsTrue(object1.hashCode().equals(object2.hashCode())) but does not ensure that this passes: Assert.IsFalse(object1.equals(object2)) Assert.IsFalse(object1.hashCode().equals(object2.hashCode())) However, the docs state that while the equality of hashcodes may not be consistent with inequality of hash codes, that all efforts should be made to ensure both. The problem we face is that with Hashtable/HashSet, we generally care more about inequality (eg Uniqueness) than we do about equality (eg Sameness). What we're trying to determine, using hashCode/equals is the uniqueness of an item in the set, which is a different kind of logic (though clearly related). So, using .hashCode() to determine uniqueness of an item in a set is incorrect, it should always be correct for determining sameness. Port Contrib.Shingle from Java -- Key: LUCENENET-437 URL: https://issues.apache.org/jira/browse/LUCENENET-437 Project: Lucene.Net Issue Type: Task Components: Lucene.Net Contrib, Lucene.Net Test Affects Versions: Lucene.Net 2.9.4, Lucene.Net 2.9.4g Reporter: Troy Howard Assignee: Troy Howard Priority: Minor Fix For: Lucene.Net 2.9.4, Lucene.Net 2.9.4g Port Contrib.Shingle from Java -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[Lucene.Net] [jira] [Commented] (LUCENENET-437) Port Contrib.Shingle from Java
[ https://issues.apache.org/jira/browse/LUCENENET-437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13067388#comment-13067388 ] Troy Howard commented on LUCENENET-437: --- Sorry, read too fast. Your last comment is true. Essentially, we're saying the same thing. Port Contrib.Shingle from Java -- Key: LUCENENET-437 URL: https://issues.apache.org/jira/browse/LUCENENET-437 Project: Lucene.Net Issue Type: Task Components: Lucene.Net Contrib, Lucene.Net Test Affects Versions: Lucene.Net 2.9.4, Lucene.Net 2.9.4g Reporter: Troy Howard Assignee: Troy Howard Priority: Minor Fix For: Lucene.Net 2.9.4, Lucene.Net 2.9.4g Port Contrib.Shingle from Java -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[Lucene.Net] [jira] [Created] (LUCENENET-437) Port Contrib.Shingle from Java
Port Contrib.Shingle from Java -- Key: LUCENENET-437 URL: https://issues.apache.org/jira/browse/LUCENENET-437 Project: Lucene.Net Issue Type: Task Components: Lucene.Net Contrib, Lucene.Net Test Affects Versions: Lucene.Net 2.9.4 Reporter: Troy Howard Assignee: Troy Howard Priority: Minor Fix For: Lucene.Net 2.9.4 Port Contrib.Shingle from Java -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[Lucene.Net] [jira] [Work started] (LUCENENET-437) Port Contrib.Shingle from Java
[ https://issues.apache.org/jira/browse/LUCENENET-437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on LUCENENET-437 started by Troy Howard. Port Contrib.Shingle from Java -- Key: LUCENENET-437 URL: https://issues.apache.org/jira/browse/LUCENENET-437 Project: Lucene.Net Issue Type: Task Components: Lucene.Net Contrib, Lucene.Net Test Affects Versions: Lucene.Net 2.9.4 Reporter: Troy Howard Assignee: Troy Howard Priority: Minor Fix For: Lucene.Net 2.9.4 Port Contrib.Shingle from Java -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[Lucene.Net] [jira] [Resolved] (LUCENENET-437) Port Contrib.Shingle from Java
[ https://issues.apache.org/jira/browse/LUCENENET-437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Troy Howard resolved LUCENENET-437. --- Resolution: Fixed See r1147514 Port Contrib.Shingle from Java -- Key: LUCENENET-437 URL: https://issues.apache.org/jira/browse/LUCENENET-437 Project: Lucene.Net Issue Type: Task Components: Lucene.Net Contrib, Lucene.Net Test Affects Versions: Lucene.Net 2.9.4 Reporter: Troy Howard Assignee: Troy Howard Priority: Minor Fix For: Lucene.Net 2.9.4 Port Contrib.Shingle from Java -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[Lucene.Net] [jira] [Commented] (LUCENENET-404) Improve brand logo design
[ https://issues.apache.org/jira/browse/LUCENENET-404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13058761#comment-13058761 ] Troy Howard commented on LUCENENET-404: --- Just a quick update. The artist is making some final edits before we commit. Will post them soon. I'll attach examples. Improve brand logo design - Key: LUCENENET-404 URL: https://issues.apache.org/jira/browse/LUCENENET-404 Project: Lucene.Net Issue Type: Sub-task Components: Project Infrastructure Reporter: Troy Howard Assignee: Troy Howard Priority: Minor Labels: branding, logo The existing Lucene.Net logo leaves a lot to be desired. We'd like a new logo that is modern and well designed. To implement this, Troy is coordinating with StackOverflow/StackExchange to manage a logo design contest, the results of which will be our new logo design. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[Lucene.Net] [jira] [Work started] (LUCENENET-404) Improve brand logo design
[ https://issues.apache.org/jira/browse/LUCENENET-404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on LUCENENET-404 started by Troy Howard. Improve brand logo design - Key: LUCENENET-404 URL: https://issues.apache.org/jira/browse/LUCENENET-404 Project: Lucene.Net Issue Type: Sub-task Components: Project Infrastructure Reporter: Troy Howard Assignee: Troy Howard Priority: Minor Labels: branding, logo Attachments: lucene-alternates.jpg, lucene-medium.png, lucene-net-logo-display.jpg The existing Lucene.Net logo leaves a lot to be desired. We'd like a new logo that is modern and well designed. To implement this, Troy is coordinating with StackOverflow/StackExchange to manage a logo design contest, the results of which will be our new logo design. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[Lucene.Net] [jira] [Commented] (LUCENENET-404) Improve brand logo design
[ https://issues.apache.org/jira/browse/LUCENENET-404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13046757#comment-13046757 ] Troy Howard commented on LUCENENET-404: --- I will post the artifacts here, and commit them to the repo. We need to get a SGA submitted from StackOverflow as well. Improve brand logo design - Key: LUCENENET-404 URL: https://issues.apache.org/jira/browse/LUCENENET-404 Project: Lucene.Net Issue Type: Sub-task Components: Project Infrastructure Reporter: Troy Howard Assignee: Troy Howard Priority: Minor Labels: branding, logo The existing Lucene.Net logo leaves a lot to be desired. We'd like a new logo that is modern and well designed. To implement this, Troy is coordinating with StackOverflow/StackExchange to manage a logo design contest, the results of which will be our new logo design. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[Lucene.Net] [jira] [Commented] (LUCENENET-417) implement streams as field values
[ https://issues.apache.org/jira/browse/LUCENENET-417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13039443#comment-13039443 ] Troy Howard commented on LUCENENET-417: --- Chris's goal here is to prevent large blobs from being placed in memory either as binary data or as string data. This is to prevent OOM exceptions on very large documents. Using Stream semantics, you can avoid this. The limitation of TextReader value types not being stored is due to the TextReader type being forward-only, which is based around how Encodings work, not due to some kind of fundamental mismatch with Lucene's business rules. There is no reason you should not be provide a resettable Stream, and an Encoding and perform the same operations, but reset the stream between tokenization and value storage stages. The only issue would be multi-threading, if tokenization and value storage were happening at the same time, they could not operate against the same stream. implement streams as field values - Key: LUCENENET-417 URL: https://issues.apache.org/jira/browse/LUCENENET-417 Project: Lucene.Net Issue Type: New Feature Components: Lucene.Net Core Reporter: Christopher Currens Attachments: BinaryStream.patch Adding binary values to a field is an expensive operation, as the whole binary data must be loaded into memory and then written to the index. Adding the ability to use a stream instead of a byte array could not only speed up the indexing process, but reducing the memory footprint as well. -Java lucene has the ability to use a TextReader the both analyze and store text in the index.- Lucene.NET lacks the ability to store string data in the index via streams. This should be a feature added into Lucene .NET as well. My thoughts are to add another Field constructor, that is Field(string name, System.IO.Stream stream, System.Text.Encoding encoding), that will allow the text to be analyzed and stored into the index. Comments about this approach are greatly appreciated. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[Lucene.Net] [jira] [Closed] (LUCENENET-397) Resolution of the legal issues
[ https://issues.apache.org/jira/browse/LUCENENET-397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Troy Howard closed LUCENENET-397. - Resolution: Not A Problem This version of Luke.Net is dependent on WPF which conflicts with our desire for this to be cross platform. Legal clearance is not necessary. Resolution of the legal issues -- Key: LUCENENET-397 URL: https://issues.apache.org/jira/browse/LUCENENET-397 Project: Lucene.Net Issue Type: Sub-task Components: Lucene.Net Contrib Reporter: Scott Lombard Assignee: Troy Howard Priority: Blocker Labels: Luke.Net Fix For: Lucene.Net 2.9.4 Resolution of the legal issues around ingesting the code into Lucene.Net. Coordinate with Aaron Powell to obtain software grant paperwork. Per Stefan Bodewig (Incubating Mentor): All it takes is: * attach the code to a JIRA ticket. * have software grants signed by all contributors to the original code base. * write a single page for the Incubator site * start a vote on Incubator general and wait for 72 hours. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[Lucene.Net] [jira] [Closed] (LUCENENET-398) Prepare the code for ingestion
[ https://issues.apache.org/jira/browse/LUCENENET-398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Troy Howard closed LUCENENET-398. - Resolution: Not A Problem Not including this code due to WPF Prepare the code for ingestion -- Key: LUCENENET-398 URL: https://issues.apache.org/jira/browse/LUCENENET-398 Project: Lucene.Net Issue Type: Sub-task Components: Lucene.Net Contrib Reporter: Scott Lombard Assignee: Sergey Mirvoda Labels: Luke.Net Fix For: Lucene.Net 2.9.4 Prepare source to be imported in the Lucene.Net respository. Staging area is a bitbucket fork at: https://bitbucket.org/thoward/luke.net-incbuating from original codebase at: https://bitbucket.org/slace/luke.net See tasks on bitbucket site (forked) for source-code related issues that need to be addressed prior to ingesting into Lucene.Net codebase. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[Lucene.Net] [jira] [Commented] (LUCENENET-391) Luke.Net for Lucene.Net
[ https://issues.apache.org/jira/browse/LUCENENET-391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13009268#comment-13009268 ] Troy Howard commented on LUCENENET-391: --- Amanuel: +1 Agreed Luke.Net for Lucene.Net --- Key: LUCENENET-391 URL: https://issues.apache.org/jira/browse/LUCENENET-391 Project: Lucene.Net Issue Type: New Feature Components: Lucene.Net Contrib Reporter: Pasha Bizhan Assignee: Sergey Mirvoda Priority: Minor Labels: Luke.Net Fix For: Lucene.Net 2.9.4 Attachments: luke-net-bin.zip, luke-net-src.zip Create a port of Java Luke to .NET for use with Lucene.Net See attachments for a 1.4 compatible version or https://bitbucket.org/thoward/luke.net-incbuating for a partial implementation that is 2.9.2 compatible. The attached version was contributed by Pasha Bizhan, and the bitbucket version was contributed by Aaron Powell (above version is a fork, original at https://bitbucket.org/slace/luke.net). If source code from either is used, a software grant must be provided from the original authors. The final version should be 2.9.4 compatible and implement most or all features of Java Luke 1.0.1 (see http://code.google.com/p/luke/ ). -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[Lucene.Net] [jira] Commented: (LUCENENET-377) Upgrade solution to VS2010
[ https://issues.apache.org/jira/browse/LUCENENET-377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12999481#comment-12999481 ] Troy Howard commented on LUCENENET-377: --- I did another version of this for the 2.9.2-incubating-RC2 build. Have a look at: https://svn.apache.org/repos/asf/incubator/lucene.net/tags/Lucene.Net_2_9_2_RC2 I placed all .sln files, as VS2010 format, in a ~/build/ directory, and updated the Release profiles to build to a ~/bin/ and ~/doc/ directories. This makes for better releases packaging structure and consolidates all solution files to a single directory (no more hunting them down). I made my changes on that branch, but could merge them in somewhere (vs2010 branch or trunk) if we like this layout/design. We also really need to address naming and namespaces. They are all over the place. I had to update a lot of things to make it all make sense. Test.dll is really inadequate naming!! I'll say more on namespaces later, in another context... Regarding VS2010 files in general, Neal brings up an interesting problem case: MsBuild 2.0 or 3.5 pre SP1 can't build a VS2010 file (even if it's target version is set to 2.0). We either need to set our standard high for end users (require .NET 3.5 SP1 or higher, and/or Visual Studio 2010), or provide VS2008 compatible versions of the solution and project files. Upgrade solution to VS2010 -- Key: LUCENENET-377 URL: https://issues.apache.org/jira/browse/LUCENENET-377 Project: Lucene.Net Issue Type: Task Components: Lucene.Net Core Affects Versions: Lucene.Net 2.9.2, Lucene.Net 2.9.4, Lucene.Net 3.x Reporter: Jeffrey Cameron Assignee: Prescott Nasser Labels: solution Fix For: Lucene.Net 2.9.4 Attachments: lucene.zip Original Estimate: 10m Remaining Estimate: 10m VS2005 is quite out of date now and there are many new improvements in VS2010. You can still leave the framework support at .NET 2.0 if you like. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira
[Lucene.Net] [jira] Commented: (LUCENENET-381) Official release of Lucene.Net 2.9.2
[ https://issues.apache.org/jira/browse/LUCENENET-381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12998145#comment-12998145 ] Troy Howard commented on LUCENENET-381: --- Started the PPMC vote at: http://bit.ly/eRqE13 Official release of Lucene.Net 2.9.2 Key: LUCENENET-381 URL: https://issues.apache.org/jira/browse/LUCENENET-381 Project: Lucene.Net Issue Type: Task Components: Lucene.Net Contrib, Lucene.Net Core, Lucene.Net Demo, Lucene.Net Test Affects Versions: Lucene.Net 2.9.2 Reporter: George Aroush Assignee: Troy Howard Priority: Critical Fix For: Lucene.Net 2.9.2 This task is to create an official packaged released of Lucene.Net 2.9.2. See http://www.apache.org/dev/#releases for details on how to create a release. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira
[Lucene.Net] [jira] Assigned: (LUCENENET-379) Clean up Lucene.Net website
[ https://issues.apache.org/jira/browse/LUCENENET-379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Troy Howard reassigned LUCENENET-379: - Assignee: Prescott Nasser (was: Troy Howard) Clean up Lucene.Net website --- Key: LUCENENET-379 URL: https://issues.apache.org/jira/browse/LUCENENET-379 Project: Lucene.Net Issue Type: Task Components: Project Infrastructure Reporter: George Aroush Assignee: Prescott Nasser Labels: Website Fix For: Lucene.Net 2.9.2 Attachments: Lucene.zip, New Logo Idea.jpg, asfcms.zip, asfcms_1.patch Original Estimate: 80h Remaining Estimate: 80h The existing Lucene.Net home page at http://lucene.apache.org/lucene.net/ is still based on the incubation, out of date design. This JIRA task is to bring it up to date with other ASF project's web page. The existing website is here: https://svn.apache.org/repos/asf/lucene/lucene.net/site/ See http://www.apache.org/dev/project-site.html to get started. It would be best to start by cloning an existing ASF project's website and adopting it for Lucene.Net. Some examples, https://svn.apache.org/repos/asf/lucene/pylucene/site/ and https://svn.apache.org/repos/asf/lucene/java/site/ -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira
[Lucene.Net] [jira] Commented: (LUCENENET-380) Evaluate Sharpen as a port tool
[ https://issues.apache.org/jira/browse/LUCENENET-380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12998156#comment-12998156 ] Troy Howard commented on LUCENENET-380: --- So far Sharpen seems to be the most viable option. Worth noting: NGit (a .NET port of JGit) is also using Sharpen to do their code generation. They have pretty good documentation about the process. They have developed a bunch of support classes to enable the Sharpen conversion. I was thinking of contacting Lluis (developer of NGit), and seeing if he would be able to help us get our Sharpen setup rolling, or at least help evaluate our use case. Anyhow, check out the project at: https://github.com/slluis/ngit Evaluate Sharpen as a port tool --- Key: LUCENENET-380 URL: https://issues.apache.org/jira/browse/LUCENENET-380 Project: Lucene.Net Issue Type: Task Components: Build Automation, Lucene.Net Contrib, Lucene.Net Core, Lucene.Net Demo, Lucene.Net Test Reporter: George Aroush Assignee: Prescott Nasser Attachments: 3.0.2_JavaToCSharpConverter_AfterPostProcessing.zip, 3.0.2_JavaToCSharpConverter_NoPostProcessing.zip, IndexWriter.java, Lucene.Net.3_0_3_Sharpen20110106.zip, Lucene.Net.Sharpen20101104.zip, Lucene.Net.Sharpen20101114.zip, NIOFSDirectory.java, QueryParser.java, TestBufferedIndexInput.java, TestDateFilter.java This task is to evaluate Sharpen as a port tool for Lucene.Net. The files to be evaluated are attached. We need to run those files (which are off Java Lucene 2.9.2) against Sharpen and compare the result against JLCA result. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira
[Lucene.Net] [jira] Commented: (LUCENENET-380) Evaluate Sharpen as a port tool
[ https://issues.apache.org/jira/browse/LUCENENET-380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12998175#comment-12998175 ] Troy Howard commented on LUCENENET-380: --- Alex - I was thinking we could fork Sharpen along those lines. AFAIK, Sharpen doesn't accept contributions, and including the source code in our repo would require them to donate to us... So we'd have to do that outside of the ASF. We could bring together both changes to Sharpen to reduce pre/post patches and also create a reusable set of Support classes starting with the ones at NGit. Perhaps over time we could convince db4o to merge our fork back in, or donate Sharpen to ASF. Evaluate Sharpen as a port tool --- Key: LUCENENET-380 URL: https://issues.apache.org/jira/browse/LUCENENET-380 Project: Lucene.Net Issue Type: Task Components: Build Automation, Lucene.Net Contrib, Lucene.Net Core, Lucene.Net Demo, Lucene.Net Test Reporter: George Aroush Assignee: Prescott Nasser Attachments: 3.0.2_JavaToCSharpConverter_AfterPostProcessing.zip, 3.0.2_JavaToCSharpConverter_NoPostProcessing.zip, IndexWriter.java, Lucene.Net.3_0_3_Sharpen20110106.zip, Lucene.Net.Sharpen20101104.zip, Lucene.Net.Sharpen20101114.zip, NIOFSDirectory.java, QueryParser.java, TestBufferedIndexInput.java, TestDateFilter.java This task is to evaluate Sharpen as a port tool for Lucene.Net. The files to be evaluated are attached. We need to run those files (which are off Java Lucene 2.9.2) against Sharpen and compare the result against JLCA result. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira
[Lucene.Net] [jira] Commented: (LUCENENET-380) Evaluate Sharpen as a port tool
[ https://issues.apache.org/jira/browse/LUCENENET-380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12998185#comment-12998185 ] Troy Howard commented on LUCENENET-380: --- I guess the best thing to do is to put it to a 72 hour vote on the list. It would cover, generally, using Sharpen for conversion, and by proxy creating and maintaining a non-ASF fork of Sharpen that our process depends on. The ultimate question, of course, is what should we call the fork? ;) Evaluate Sharpen as a port tool --- Key: LUCENENET-380 URL: https://issues.apache.org/jira/browse/LUCENENET-380 Project: Lucene.Net Issue Type: Task Components: Build Automation, Lucene.Net Contrib, Lucene.Net Core, Lucene.Net Demo, Lucene.Net Test Reporter: George Aroush Assignee: Prescott Nasser Attachments: 3.0.2_JavaToCSharpConverter_AfterPostProcessing.zip, 3.0.2_JavaToCSharpConverter_NoPostProcessing.zip, IndexWriter.java, Lucene.Net.3_0_3_Sharpen20110106.zip, Lucene.Net.Sharpen20101104.zip, Lucene.Net.Sharpen20101114.zip, NIOFSDirectory.java, QueryParser.java, TestBufferedIndexInput.java, TestDateFilter.java This task is to evaluate Sharpen as a port tool for Lucene.Net. The files to be evaluated are attached. We need to run those files (which are off Java Lucene 2.9.2) against Sharpen and compare the result against JLCA result. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira
[Lucene.Net] [jira] Assigned: (LUCENENET-380) Evaluate Sharpen as a port tool
[ https://issues.apache.org/jira/browse/LUCENENET-380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Troy Howard reassigned LUCENENET-380: - Assignee: Alex Thompson (was: Prescott Nasser) Assigning to Alex to this task (now that I figured out how to add people into the assignee's list). Evaluate Sharpen as a port tool --- Key: LUCENENET-380 URL: https://issues.apache.org/jira/browse/LUCENENET-380 Project: Lucene.Net Issue Type: Task Components: Build Automation, Lucene.Net Contrib, Lucene.Net Core, Lucene.Net Demo, Lucene.Net Test Reporter: George Aroush Assignee: Alex Thompson Attachments: 3.0.2_JavaToCSharpConverter_AfterPostProcessing.zip, 3.0.2_JavaToCSharpConverter_NoPostProcessing.zip, IndexWriter.java, Lucene.Net.3_0_3_Sharpen20110106.zip, Lucene.Net.Sharpen20101104.zip, Lucene.Net.Sharpen20101114.zip, NIOFSDirectory.java, QueryParser.java, TestBufferedIndexInput.java, TestDateFilter.java This task is to evaluate Sharpen as a port tool for Lucene.Net. The files to be evaluated are attached. We need to run those files (which are off Java Lucene 2.9.2) against Sharpen and compare the result against JLCA result. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira
[Lucene.Net] [jira] Updated: (LUCENENET-172) This patch fixes the unexceptional exceptions ecountered in FastCharStream and SupportClass
[ https://issues.apache.org/jira/browse/LUCENENET-172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Troy Howard updated LUCENENET-172: -- Due Date: 28/Mar/11 Fix Version/s: (was: Lucene.Net 3.x) Lucene.Net 2.9.4 Scheduled for 2.9.4 release. (Re: previous discussion. We're ok with deviations from Java Lucene, starting with the 2.9.4 release) This patch fixes the unexceptional exceptions ecountered in FastCharStream and SupportClass --- Key: LUCENENET-172 URL: https://issues.apache.org/jira/browse/LUCENENET-172 Project: Lucene.Net Issue Type: Improvement Components: Lucene.Net Core Affects Versions: Lucene.Net 2.3.1, Lucene.Net 2.3.2 Reporter: Ben Martz Priority: Minor Fix For: Lucene.Net 2.9.4 Attachments: lucene_2.3.1_exceptions_fix.patch The java version of Lucene handles end-of-file in FastCharStream by throwing an exception. This behavior has been ported to .NET but the behavior carries an unacceptable cost in the .NET environment. This patch is based on the prior work in LUCENENET-8 and LUCENENET-11, which I gratefully acknowledge for the solution. While I understand that this patch is outside of the current project specification in that it deviates from the pure nature of the port, I believe that it is very important to make the patch available to any developer looking to leverage Lucene.Net in their project. Thanks for your consideration. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira
[Lucene.Net] [jira] Created: (LUCENENET-402) Update website to reflect current status and information
Update website to reflect current status and information Key: LUCENENET-402 URL: https://issues.apache.org/jira/browse/LUCENENET-402 Project: Lucene.Net Issue Type: Sub-task Components: Project Infrastructure Reporter: Troy Howard Assignee: Prescott Nasser Update website content to accurately reflect current project status and information. See staging site at: http://lucene.net.staging.apache.org/lucene.net/ To edit content, please use: https://cms.apache.org/lucene.net/ -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira
[Lucene.Net] [jira] Created: (LUCENENET-403) Improve site layout and design
Improve site layout and design -- Key: LUCENENET-403 URL: https://issues.apache.org/jira/browse/LUCENENET-403 Project: Lucene.Net Issue Type: Sub-task Components: Project Infrastructure Reporter: Troy Howard Assignee: Prescott Nasser Improve the website layout and design. Current staging design is based off an extremely simplistic implementation of Apache CMS basic template using the default Apache CMS CSS styling. Let's try to make it look better and have a more intuitive navigational structure. See staging site at: http://lucene.net.staging.apache.org/lucene.net/ To edit content, please use: https://cms.apache.org/lucene.net/ -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira
[Lucene.Net] [jira] Created: (LUCENENET-404) Improve brand logo design
Improve brand logo design - Key: LUCENENET-404 URL: https://issues.apache.org/jira/browse/LUCENENET-404 Project: Lucene.Net Issue Type: Sub-task Components: Project Infrastructure Reporter: Troy Howard Assignee: Troy Howard Priority: Minor The existing Lucene.Net logo leaves a lot to be desired. We'd like a new logo that is modern and well designed. To implement this, Troy is coordinating with StackOverflow/StackExchange to manage a logo design contest, the results of which will be our new logo design. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira
[Lucene.Net] [jira] Updated: (LUCENENET-391) Luke.Net for Lucene.Net
[ https://issues.apache.org/jira/browse/LUCENENET-391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Troy Howard updated LUCENENET-391: -- Due Date: 28/Mar/11 Description: Create a port of Java Luke to .NET for use with Lucene.Net See attachments for a 1.4 compatible version or https://bitbucket.org/thoward/luke.net-incbuating for a partial implementation that is 2.9.2 compatible. The attached version was contributed by Pasha Bizhan, and the bitbucket version was contributed by Aaron Powell (above version is a fork, original at https://bitbucket.org/slace/luke.net). If source code from either is used, a software grant must be provided from the original authors. The final version should be 2.9.4 compatible and implement most or all features of Java Luke 1.0.1 (see http://code.google.com/p/luke/ ). was:.net port of Luke.Net for Lucene.Net Affects Version/s: (was: Lucene.Net 2.9.2) Fix Version/s: Lucene.Net 2.9.4 Assignee: Sergey Mirvoda Scheduled for 2.9.4 and updated description to reflect recent contributions. Luke.Net for Lucene.Net --- Key: LUCENENET-391 URL: https://issues.apache.org/jira/browse/LUCENENET-391 Project: Lucene.Net Issue Type: New Feature Components: Lucene.Net Contrib Reporter: Pasha Bizhan Assignee: Sergey Mirvoda Priority: Minor Labels: Luke.Net Fix For: Lucene.Net 2.9.4 Attachments: luke-net-bin.zip, luke-net-src.zip Create a port of Java Luke to .NET for use with Lucene.Net See attachments for a 1.4 compatible version or https://bitbucket.org/thoward/luke.net-incbuating for a partial implementation that is 2.9.2 compatible. The attached version was contributed by Pasha Bizhan, and the bitbucket version was contributed by Aaron Powell (above version is a fork, original at https://bitbucket.org/slace/luke.net). If source code from either is used, a software grant must be provided from the original authors. The final version should be 2.9.4 compatible and implement most or all features of Java Luke 1.0.1 (see http://code.google.com/p/luke/ ). -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira
[Lucene.Net] [jira] Updated: (LUCENENET-397) Resolution of the legal issues
[ https://issues.apache.org/jira/browse/LUCENENET-397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Troy Howard updated LUCENENET-397: -- Due Date: 28/Mar/11 Description: Resolution of the legal issues around ingesting the code into Lucene.Net. Coordinate with Aaron Powell to obtain software grant paperwork. Per Stefan Bodewig (Incubating Mentor): All it takes is: * attach the code to a JIRA ticket. * have software grants signed by all contributors to the original code base. * write a single page for the Incubator site * start a vote on Incubator general and wait for 72 hours. was:Resolution of the legal issues around ingesting the code into Lucene.Net Fix Version/s: Lucene.Net 2.9.4 Labels: Luke.Net (was: ) Updated description and scheduled for 2.9.4 release. Resolution of the legal issues -- Key: LUCENENET-397 URL: https://issues.apache.org/jira/browse/LUCENENET-397 Project: Lucene.Net Issue Type: Sub-task Components: Lucene.Net Contrib Reporter: Scott Lombard Assignee: Troy Howard Priority: Blocker Labels: Luke.Net Fix For: Lucene.Net 2.9.4 Resolution of the legal issues around ingesting the code into Lucene.Net. Coordinate with Aaron Powell to obtain software grant paperwork. Per Stefan Bodewig (Incubating Mentor): All it takes is: * attach the code to a JIRA ticket. * have software grants signed by all contributors to the original code base. * write a single page for the Incubator site * start a vote on Incubator general and wait for 72 hours. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira
[Lucene.Net] [jira] Updated: (LUCENENET-398) Prepare the code for ingestion
[ https://issues.apache.org/jira/browse/LUCENENET-398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Troy Howard updated LUCENENET-398: -- Description: Prepare source to be imported in the Lucene.Net respository. Staging area is a bitbucket fork at: https://bitbucket.org/thoward/luke.net-incbuating from original codebase at: https://bitbucket.org/slace/luke.net See tasks on bitbucket site (forked) for source-code related issues that need to be addressed prior to ingesting into Lucene.Net codebase. was:Prepare source to be imported in the Lucene.Net respository Fix Version/s: Lucene.Net 2.9.4 Labels: Luke.Net (was: ) Updated description and scheduled for 2.9.4 release. Prepare the code for ingestion -- Key: LUCENENET-398 URL: https://issues.apache.org/jira/browse/LUCENENET-398 Project: Lucene.Net Issue Type: Sub-task Components: Lucene.Net Contrib Reporter: Scott Lombard Assignee: Sergey Mirvoda Labels: Luke.Net Fix For: Lucene.Net 2.9.4 Prepare source to be imported in the Lucene.Net respository. Staging area is a bitbucket fork at: https://bitbucket.org/thoward/luke.net-incbuating from original codebase at: https://bitbucket.org/slace/luke.net See tasks on bitbucket site (forked) for source-code related issues that need to be addressed prior to ingesting into Lucene.Net codebase. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira
[Lucene.Net] [jira] Updated: (LUCENENET-398) Prepare the code for ingestion
[ https://issues.apache.org/jira/browse/LUCENENET-398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Troy Howard updated LUCENENET-398: -- Due Date: 28/Feb/11 Prepare the code for ingestion -- Key: LUCENENET-398 URL: https://issues.apache.org/jira/browse/LUCENENET-398 Project: Lucene.Net Issue Type: Sub-task Components: Lucene.Net Contrib Reporter: Scott Lombard Assignee: Sergey Mirvoda Labels: Luke.Net Fix For: Lucene.Net 2.9.4 Prepare source to be imported in the Lucene.Net respository. Staging area is a bitbucket fork at: https://bitbucket.org/thoward/luke.net-incbuating from original codebase at: https://bitbucket.org/slace/luke.net See tasks on bitbucket site (forked) for source-code related issues that need to be addressed prior to ingesting into Lucene.Net codebase. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira
[Lucene.Net] [jira] Updated: (LUCENENET-372) NLS pack for Lucene.NET: BR, CJK, CN, CZ, DE, FR, NL, RU analyzers
[ https://issues.apache.org/jira/browse/LUCENENET-372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Troy Howard updated LUCENENET-372: -- Due Date: 28/Mar/11 Description: Port of java analyzers. Sorry for 1.4 version, it's from 2005 year Update to 2.9.2/2.9.4 compatibility for 2.9.4 release. was: Port of java analyzers. Sorry for 1.4 version, it's from 2005 year Fix Version/s: Lucene.Net 2.9.4 NLS pack for Lucene.NET: BR, CJK, CN, CZ, DE, FR, NL, RU analyzers -- Key: LUCENENET-372 URL: https://issues.apache.org/jira/browse/LUCENENET-372 Project: Lucene.Net Issue Type: New Feature Components: Lucene.Net Contrib Reporter: Pasha Bizhan Assignee: Prescott Nasser Priority: Minor Labels: Analyzers Fix For: Lucene.Net 2.9.4 Attachments: lucene-net-nls.zip Port of java analyzers. Sorry for 1.4 version, it's from 2005 year Update to 2.9.2/2.9.4 compatibility for 2.9.4 release. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira
[Lucene.Net] [jira] Created: (LUCENENET-399) Port changes from Java Lucene 2.9.3 and 2.9.4 releases
Port changes from Java Lucene 2.9.3 and 2.9.4 releases -- Key: LUCENENET-399 URL: https://issues.apache.org/jira/browse/LUCENENET-399 Project: Lucene.Net Issue Type: Task Components: Lucene.Net Core, Lucene.Net Test Reporter: Troy Howard Fix For: Lucene.Net 2.9.4 Port changes from Java Lucene 2.9.3 and 2.9.4 releases. The Lucene.Net 2.9.4 release will roll up the changes from both of those releases into one. Unit tests should be added or updated to reflect the changes. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira
[Lucene.Net] [jira] Updated: (LUCENENET-380) Evaluate Sharpen as a port tool
[ https://issues.apache.org/jira/browse/LUCENENET-380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Troy Howard updated LUCENENET-380: -- Component/s: Build Automation Due Date: 28/Feb/11 (was: 31/Dec/10) Fix Version/s: (was: Lucene.Net 3.x) Assignee: Prescott Nasser Scheduled task. We should come to a decision about our preferred tooling for this and start work on actual implementation by March 1st. Evaluate Sharpen as a port tool --- Key: LUCENENET-380 URL: https://issues.apache.org/jira/browse/LUCENENET-380 Project: Lucene.Net Issue Type: Task Components: Build Automation, Lucene.Net Contrib, Lucene.Net Core, Lucene.Net Demo, Lucene.Net Test Reporter: George Aroush Assignee: Prescott Nasser Attachments: 3.0.2_JavaToCSharpConverter_AfterPostProcessing.zip, 3.0.2_JavaToCSharpConverter_NoPostProcessing.zip, IndexWriter.java, Lucene.Net.3_0_3_Sharpen20110106.zip, Lucene.Net.Sharpen20101104.zip, Lucene.Net.Sharpen20101114.zip, NIOFSDirectory.java, QueryParser.java, TestBufferedIndexInput.java, TestDateFilter.java This task is to evaluate Sharpen as a port tool for Lucene.Net. The files to be evaluated are attached. We need to run those files (which are off Java Lucene 2.9.2) against Sharpen and compare the result against JLCA result. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira
[Lucene.Net] [jira] Created: (LUCENENET-400) Evaluate tooling for continuous integration server
Evaluate tooling for continuous integration server -- Key: LUCENENET-400 URL: https://issues.apache.org/jira/browse/LUCENENET-400 Project: Lucene.Net Issue Type: Task Components: Build Automation, Project Infrastructure Reporter: Troy Howard Assignee: michael herndon We would like to have a CI server setup for Lucene.Net. It has been suggested to do this outside of the ASF infrastructure, but this would not work for ASF. Please review the available options at http://ci.apache.org/ and evaluate which CI server system would be preferred for our setup. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira
[Lucene.Net] [jira] Created: (LUCENENET-401) Update website to be Apache CMS based
Update website to be Apache CMS based - Key: LUCENENET-401 URL: https://issues.apache.org/jira/browse/LUCENENET-401 Project: Lucene.Net Issue Type: Sub-task Components: Project Infrastructure Reporter: Troy Howard Assignee: Prescott Nasser Update site to work with Apache CMS. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (LUCENENET-389) Signing the released assembly
[ https://issues.apache.org/jira/browse/LUCENENET-389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Troy Howard updated LUCENENET-389: -- Affects Version/s: (was: Lucene.Net 2.9.2) Lucene.Net 2.9.4 Fix Version/s: (was: Lucene.Net 2.9.2) Lucene.Net 2.9.4 Remaining Estimate: 1h (was: 16h) Original Estimate: 1h (was: 16h) Scheduled for 2.9.4 release. The signing requested here is not part of the normal release process. It's in reference to created a Strong Named Assembly, generally so that a DLL may be included in the GAC. See here: http://msdn.microsoft.com/en-us/library/wd40t7ad.aspx The normal Apache binary releases are signed, but that's a different process, and more focused on verification of the source/creator of the assembly. Because this can't be built from the current 2.9.2 tag without modifications, we'll need to push this out to the 2.9.4 release. Signing the released assembly - Key: LUCENENET-389 URL: https://issues.apache.org/jira/browse/LUCENENET-389 Project: Lucene.Net Issue Type: Improvement Components: Lucene.Net Core Affects Versions: Lucene.Net 2.9.4 Reporter: Patric Forsgard Priority: Critical Fix For: Lucene.Net 2.9.4 Original Estimate: 1h Remaining Estimate: 1h In the project I working in i need a signed version of the Lucene.Net-assembly. For the moment I will compile and sign with my own key but it would be great if the official release already should be signed. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (LUCENENET-377) Upgrade solution to VS2010
[ https://issues.apache.org/jira/browse/LUCENENET-377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Troy Howard updated LUCENENET-377: -- Fix Version/s: (was: Lucene.Net 2.9.2) Lucene.Net 2.9.4 Pushing this out to 2.9.4 release because it will require a commit that will put us beyond the existing 2.9.2 tag. The 2.9.2 release should be made from that tag with no further modifications. Upgrade solution to VS2010 -- Key: LUCENENET-377 URL: https://issues.apache.org/jira/browse/LUCENENET-377 Project: Lucene.Net Issue Type: Task Components: Lucene.Net Core Affects Versions: Lucene.Net 2.9.2, Lucene.Net 2.9.4, Lucene.Net 3.x, .NET API Reporter: Jeffrey Cameron Assignee: Prescott Nasser Labels: solution Fix For: Lucene.Net 2.9.4 Attachments: lucene.zip Original Estimate: 10m Remaining Estimate: 10m VS2005 is quite out of date now and there are many new improvements in VS2010. You can still leave the framework support at .NET 2.0 if you like. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (LUCENENET-377) Upgrade solution to VS2010
[ https://issues.apache.org/jira/browse/LUCENENET-377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Troy Howard updated LUCENENET-377: -- Due Date: 28/Mar/11 Upgrade solution to VS2010 -- Key: LUCENENET-377 URL: https://issues.apache.org/jira/browse/LUCENENET-377 Project: Lucene.Net Issue Type: Task Components: Lucene.Net Core Affects Versions: Lucene.Net 2.9.2, Lucene.Net 2.9.4, Lucene.Net 3.x, .NET API Reporter: Jeffrey Cameron Assignee: Prescott Nasser Labels: solution Fix For: Lucene.Net 2.9.4 Attachments: lucene.zip Original Estimate: 10m Remaining Estimate: 10m VS2005 is quite out of date now and there are many new improvements in VS2010. You can still leave the framework support at .NET 2.0 if you like. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (LUCENENET-266) Putting support classes in separate files and in a separate directory
[ https://issues.apache.org/jira/browse/LUCENENET-266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Troy Howard updated LUCENENET-266: -- Component/s: Lucene.Net Core Due Date: 28/Mar/11 Fix Version/s: Lucene.Net 2.9.4 Labels: refactoring (was: ) Scheduled for 2.9.4 release. Putting support classes in separate files and in a separate directory -- Key: LUCENENET-266 URL: https://issues.apache.org/jira/browse/LUCENENET-266 Project: Lucene.Net Issue Type: Improvement Components: Lucene.Net Core Reporter: Andrei Iliev Labels: refactoring Fix For: Lucene.Net 2.9.4 I am going to add some new classes (nio support, IdentityHashMap, ...) What is the best place to put it in? SuportClass is getting bigger and bigger. I think it is time to put all support classes in separate files and in a separate directory (ex. JavaSupport). Any comments? -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (LUCENENET-371) Unit test for Search.Regex port
[ https://issues.apache.org/jira/browse/LUCENENET-371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Troy Howard updated LUCENENET-371: -- Component/s: Lucene.Net Core Due Date: 28/Mar/11 Fix Version/s: Lucene.Net 2.9.4 Scheduled for 2.9.4 release. Unit test for Search.Regex port --- Key: LUCENENET-371 URL: https://issues.apache.org/jira/browse/LUCENENET-371 Project: Lucene.Net Issue Type: Test Components: Lucene.Net Core Reporter: Daniele Fusi Priority: Minor Fix For: Lucene.Net 2.9.4 Attachments: TestRegexpQuery.cs I added some essential unit tests for my port of Search.Regex. Hope this will help you integrating this feature into one of your next releases. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (LUCENENET-330) Search.Regex minimal port
[ https://issues.apache.org/jira/browse/LUCENENET-330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Troy Howard updated LUCENENET-330: -- Component/s: Lucene.Net Core Due Date: 28/Mar/11 Fix Version/s: Lucene.Net 2.9.4 Scheduled for 2.9.4 release. Search.Regex minimal port - Key: LUCENENET-330 URL: https://issues.apache.org/jira/browse/LUCENENET-330 Project: Lucene.Net Issue Type: New Feature Components: Lucene.Net Core Reporter: Daniele Fusi Priority: Minor Fix For: Lucene.Net 2.9.4 Attachments: Regex.zipx This is a minimal port for Lucene regex-based queries and span queries. The port refers to RegexQuery and SpanRegexQuery only, with their dependencies. The corresponding Java source is quoted in each class remarks. The only renaming was JavaUtilRegexCapabilities which was translated into C# as CSharpRegexCapabilities. No time for adding unit tests and other sources by now, sorry, should I find it I'll make a new post. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (LUCENENET-374) IndexReader.IsCurrent returning false positive in some cases
[ https://issues.apache.org/jira/browse/LUCENENET-374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Troy Howard updated LUCENENET-374: -- Component/s: Lucene.Net Core Due Date: 28/Mar/11 Environment: Lucene 2.9.2 (was: Lucene 2.9.2.2) Affects Version/s: Lucene.Net 2.9.2 Fix Version/s: Lucene.Net 2.9.4 Scheduled for 2.9.4 release. IndexReader.IsCurrent returning false positive in some cases Key: LUCENENET-374 URL: https://issues.apache.org/jira/browse/LUCENENET-374 Project: Lucene.Net Issue Type: Bug Components: Lucene.Net Core Affects Versions: Lucene.Net 2.9.2 Environment: Lucene 2.9.2 Reporter: Paul Gunn Fix For: Lucene.Net 2.9.4 Attachments: SegmentInfo.patch I've isolated the issue to a pretty small test case [below]. Under the covers, it looks like NrtIsCurrent is returning 'true' incorrectly when documents are deleted then committed [but before any other documents are added]. Please let me know if any addition data is needed to repro. Thanks, Paul Lucene.Net.Store.RAMDirectory ramDir = new Lucene.Net.Store.RAMDirectory(); Lucene.Net.Index.IndexWriter writer = new Lucene.Net.Index.IndexWriter(ramDir, new Lucene.Net.Analysis.KeywordAnalyzer(), true, new Lucene.Net.Index.IndexWriter.MaxFieldLength(1000) ); Lucene.Net.Documents.Field field = new Lucene.Net.Documents.Field(TEST, mytest, Lucene.Net.Documents.Field.Store.YES, Lucene.Net.Documents.Field.Index.ANALYZED); Lucene.Net.Documents.Document doc = new Lucene.Net.Documents.Document(); doc.Add(field); writer.AddDocument(doc); Lucene.Net.Index.IndexReader reader = writer.GetReader(); writer.DeleteDocuments(new Lucene.Net.Index.Term(TEST, mytest)); bool iscurrent1 = reader.IsCurrent(); // FALSE as expected writer.Commit(); bool iscurrent2 = reader.IsCurrent(); // returns TRUE now - Incorrect System.Diagnostics.Debug.Assert(iscurrent1 == iscurrent2); // ASSERT FAILs -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (LUCENENET-379) Clean up Lucene.Net website
[ https://issues.apache.org/jira/browse/LUCENENET-379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12996254#comment-12996254 ] Troy Howard commented on LUCENENET-379: --- I would place the log in the disclaimer section at the bottom. Too many logos near the top is just going to be cluttered. We'll already have two largish logos, if we stick with the current template. Another alternative would be to ditch the main Apache logo and replace with the incubator logo. I'll post a message on incubator general asking for guidance about logo design contests and the appropriate way to go about that as a podling. Thanks, Troy Clean up Lucene.Net website --- Key: LUCENENET-379 URL: https://issues.apache.org/jira/browse/LUCENENET-379 Project: Lucene.Net Issue Type: Task Reporter: George Aroush Attachments: Lucene.zip, New Logo Idea.jpg, asfcms.zip, asfcms_1.patch The existing Lucene.Net home page at http://lucene.apache.org/lucene.net/ is still based on the incubation, out of date design. This JIRA task is to bring it up to date with other ASF project's web page. The existing website is here: https://svn.apache.org/repos/asf/lucene/lucene.net/site/ See http://www.apache.org/dev/project-site.html to get started. It would be best to start by cloning an existing ASF project's website and adopting it for Lucene.Net. Some examples, https://svn.apache.org/repos/asf/lucene/pylucene/site/ and https://svn.apache.org/repos/asf/lucene/java/site/ -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (LUCENENET-379) Clean up Lucene.Net website
[ https://issues.apache.org/jira/browse/LUCENENET-379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12995595#comment-12995595 ] Troy Howard commented on LUCENENET-379: --- The staging site and CMS Web UI are working now and ready for us to get in there and edit content/layout/etc.. I set this up with a really basic template copied from the Lucy project, which is copied from the default Apache site. Browse here to see the staging site: http://lucene.net.staging.apache.org/lucene.net/ And here to edit content using CMS Web UI: https://cms.apache.org/lucene.net/ Clean up Lucene.Net website --- Key: LUCENENET-379 URL: https://issues.apache.org/jira/browse/LUCENENET-379 Project: Lucene.Net Issue Type: Task Reporter: George Aroush Attachments: Lucene.zip, New Logo Idea.jpg, asfcms.zip, asfcms_1.patch The existing Lucene.Net home page at http://lucene.apache.org/lucene.net/ is still based on the incubation, out of date design. This JIRA task is to bring it up to date with other ASF project's web page. The existing website is here: https://svn.apache.org/repos/asf/lucene/lucene.net/site/ See http://www.apache.org/dev/project-site.html to get started. It would be best to start by cloning an existing ASF project's website and adopting it for Lucene.Net. Some examples, https://svn.apache.org/repos/asf/lucene/pylucene/site/ and https://svn.apache.org/repos/asf/lucene/java/site/ -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira
