[
https://issues.apache.org/jira/browse/LUCENENET-337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12843812#action_12843812
]
Michael Garski commented on LUCENENET-337:
--
There is an alternate way to avoid
Yup, I agree that there's no such thing as a "safe" warning. They are
there for a reason. However, if we are going to consistently ignore
the ones we currently have (ie LUCENENET-320 is also closed) then I
think it's useful to have some method of filtering the warnings we do
get so that we can iden
Yep, I can open in VS08 now.
It still wants to convert Lucene.Net to the newer format. I'm sure I
remember a discussion about this. The opinion seemed to be that that
wasn't desirable. Has that changed now? +1 from me
On 10 March 2010 19:47, Digy wrote:
> It's OK now.
> DIGY.
>
> -Original Me
It's OK now.
DIGY.
-Original Message-
From: Michael Garski [mailto:mgar...@myspace-inc.com]
Sent: Wednesday, March 10, 2010 9:25 PM
To: lucene-net-dev@lucene.apache.org
Subject: RE: How do you open Contrib.net?
I re-created the solution file and verified I was able to open it from Window
I re-created the solution file and verified I was able to open it from Windows
Explorer and committed the change. Let me know if this corrects the issue.
Michael
-Original Message-
From: Digy [mailto:digyd...@gmail.com]
Sent: Wednesday, March 10, 2010 9:58 AM
To: lucene-net-dev@lucene.
There was a disccusion on these warnings previously.
https://issues.apache.org/jira/browse/LUCENENET-202 .
DIGY.
-Original Message-
From: Andy Pook [mailto:andy.p...@gmail.com]
Sent: Wednesday, March 10, 2010 12:38 PM
To: lucene-net-dev@lucene.apache.org
Subject: Re: More compiler warnin
> Windows Explorer does not recognise it as a VS solutions file
I have the same problem too.
DIGY
-Original Message-
From: Michael Garski [mailto:mgar...@myspace-inc.com]
Sent: Wednesday, March 10, 2010 7:09 PM
To: lucene-net-dev@lucene.apache.org
Subject: RE: How do you open Contrib.net
[
https://issues.apache.org/jira/browse/LUCENENET-348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Digy resolved LUCENENET-348.
Resolution: Fixed
Thank Andy. I committed the patch.
DIGY
> Avoidable compiler warning
> -
Andy,
I have no problems in opening the solution in VS2008 and I'm not sure
why the icon is different. You are correct in that the solution
contains a reference to the Lucene.Net project in the solution as
opposed to an assembly reference, and it will convert the Lucene.Net
project to a VS2008 pr
I've raised a ticket for the warning (LUCENENET-348). But I don't
think it makes sense to log a bug for the build scripts. So I'll just
list them here.
Clean Debug build ignoring "doc" and other "unimportant" warnings
msbuild -p:NoWarn="0168,0169,0414,0612,0618,0649,1572,1573,1574,1580,1587,1591"
[
https://issues.apache.org/jira/browse/LUCENENET-348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Pook updated LUCENENET-348:
Attachment: CustomScoreQuery.patch
remove reader member. So use inherited member from ancestor
Avoidable compiler warning
--
Key: LUCENENET-348
URL: https://issues.apache.org/jira/browse/LUCENENET-348
Project: Lucene.Net
Issue Type: Bug
Reporter: Andy Pook
Compiler warning that can be easier avoid
Sounds like a dumb question...
Windows Explorer does not recognise it as a VS solutions file. The
icon has the VS symbol (lower right) but not the version number
(usually top right).
Using File|Open in VS shows the Conversion wizard. The report at the
end says that it has converted Lucene.Net.cspr
13 matches
Mail list logo
