That makes sense. We've been serving up the distributions from
~/lucene.net/site/download in our svn repo through the website. I
guess with this release, once it passes the IPMC vote, we can create a
lucene.net under http://www.apache.org/dist/incubator/ and serve from
there? Should we also move
I'm out of town this weekend, but I'm hoping to get one or two designs (likely
just screenshots) attached to the JIRA so people can give me some feedback.
I'll make it quick turn around and won't leave it open for feedback long
though. If anyone has ideas / thoughts, samples they like, comment
[
https://issues.apache.org/jira/browse/LUCENENET-403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12998248#comment-12998248
]
Prescott Nasser commented on LUCENENET-403:
---
Some sites that we are
On 2011-02-23, Troy Howard wrote:
That makes sense. We've been serving up the distributions from
~/lucene.net/site/download in our svn repo through the website.
Ah, understood. This is not the way you should do it - in fact you
should never have done. Releases are supposed to take advantage
Thanks,
I solved this problem. I found that if what i typed is lowercase, the result
is not case senstive, e.g. if search for database it would return
DATABASE, database. However, if what i typed is uppercase, the result is
case sensitive, e.g. if search for DATABASE, no results would return. So
Check that you're using the same analyzer that you indexed with to search
against that particular field. Also, wildcard queries don't really handle
spaces. I suggest using the query parser if you want to have multiple terms
to search the same field by. Considering your previous query, you'll
Troy,
I will start adding separate JIRA issues tonight. In the past do all the Java
Lucene issues translate into .Net issues?
Scott
On Wed, Feb 23, 2011at 2:20 PM ,Troy Howard [mailto:thowar...@gmail.com] wrote:
Scott,
I would say the first task would be to collect all the Java changes
[
https://issues.apache.org/jira/browse/LUCENENET-399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12998559#comment-12998559
]
Digy commented on LUCENENET-399:
{quote}
Scott,
I would say the first task would be to
[
https://issues.apache.org/jira/browse/LUCENENET-403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Prescott Nasser updated LUCENENET-403:
--
Attachment: layout1.zip
Based mostly on bitbucket.org. Takes some elements from
2.3.1-2.3.2 or 2.9.1 - 2.9.2 transitions were done with just a single
patch, for ex.
DIGY
-Original Message-
From: Lombard, Scott [mailto:slomb...@kingindustries.com]
Sent: Wednesday, February 23, 2011 11:36 PM
To: lucene-net-dev@lucene.apache.org
Subject: [Lucene.Net] JIRA issues for
In the time needed to create 10s of issues, half of the fixes could be done
:)
DIGY
-Original Message-
From: Lombard, Scott [mailto:slomb...@kingindustries.com]
Sent: Wednesday, February 23, 2011 11:36 PM
To: lucene-net-dev@lucene.apache.org
Subject: [Lucene.Net] JIRA issues for Java
You're probably right DIGY. I will take a look at issues and create JIRA
issues where the complexity deems it appropriate. I will comment or patch
otherwise.
Scott
-Original Message-
From: Digy [mailto:digyd...@gmail.com]
Sent: Wednesday, February 23, 2011 5:02 PM
To:
We can take,for ex, a namespace like Lucene.Net.Util(+test cases) and create
a single patch for all of the related issues.
(This approach needs to work on svn history, not on issues)
DIGY
-Original Message-
From: Lombard, Scott [mailto:slomb...@kingindustries.com]
Sent: Thursday,
Instead of looking at issues, use TortoiseSVN's compare revision utility.
Some issues seem to be complex but patches are really simple. See the fix
for 2 of 103 files below
DIGY
Index: Constants.cs
===
--- Constants.cs
[
https://issues.apache.org/jira/browse/LUCENENET-380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12998626#comment-12998626
]
Alex Thompson commented on LUCENENET-380:
-
That's worth a shot I guess.
Forum
On 2011-02-23, Troy Howard wrote:
Whenever we get our CI server setup, we should probably have a build
task which checks for licensing in code files and inserts it if it's
not there.
Buildbot http://ci.apache.org/buildbot.html can be set up to create
RAT reports, even for projects that use
16 matches
Mail list logo
