[
https://issues.apache.org/jira/browse/LUCENENET-328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12791007#action_12791007
]
runenur edited comment on LUCENENET-328 at 12/15/09 10:5
[
https://issues.apache.org/jira/browse/LUCENENET-328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12791007#action_12791007
]
runenur commented on LUCENENET-328:
---
At least it fails when building the solu
[
https://issues.apache.org/jira/browse/LUCENENET-328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
runenur updated LUCENENET-328:
--
Attachment: LUCENENET-328.patch
> Test solution build fails after revision 888
Reporter: runenur
The change in revision 888204 causes the test solution build to fail, and
should be reversed. What was the motivation behind this change?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Hey,
The check-in in revision 888204 removed the Lucene.Net.dll reference in
the test project, which makes the build fail here. Why was the reference
removed?
I've created an issue in Jira and attached a patch.
https://issues.apache.org/jira/browse/LUCENENET-317
On Sun, Nov 29, 2009 at 1:31 PM, runenur wrote:
> Hey,
>
> I noticed that the only thing you changed in your fix was the output
> directory. There are a few other things tha
ing this a while back; I just committed a fix.
> However, I don't see "Allow unsafe code" set (per your previous email).
>
> -- George
>
> -----Original Message-
> From: runenur [mailto:rune...@gmail.com]
> Sent: Thursday, November 26, 2009 6:57 PM
> To: luc
I'm sorry, I meant the project file. Also, the output directory is
incorrect. It is currently set to bin/Debug both in the debug and the
release configuration.
- Rune
Hey,
I just noticed that the Lucene.Net.sln file is not configured correctly. The
Release configuration has "Define DEBUG constant" and "Allow unsafe code"
checked, but they should be unchecked. The way it is configured now, the
release build is exactly the same as the debug build, which could lea
Hey guys,
I just tried to do a clean compile of the code base, and notices that
there's a dependency to the SharpZipLib assembly. If this is a
necessary dependency, why is the assembly not included in the svn
repository? It is considered best practice to have all dependencies
checked into the repo
ch as NHibernate, Ninject, and Structure Map
have already been added. Using such a CI server, a build can be made
every time code has been commit, the test suite can be run, and emails
can be sent to the mailing list when build errors or errors in a test
run occur.
runenur
On Fri, Jul 31, 2009 at 4:17
not remember
the details behind the bugs, but I will bring them to attention at a
later time).
Is this patch something you would be interested in applying?
PS: I have noticed that trunk has started to show signs of the 2.4.0
conversion, which is good news. Nice work!
runenur
On Fri, Jul 24, 2009
th best regards,
runenur
13 matches
Mail list logo
