lucenenet-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From wwb <...@git.apache.org>
Subject [GitHub] lucenenet issue #200: Adding nunit 3 console package to enable TeamCity to r...
Date Mon, 19 Dec 2016 03:27:47 GMT
Github user wwb commented on the issue:

    https://github.com/apache/lucenenet/pull/200
  
    If you are talking about [this one] (https://teamcity.jetbrains.com/viewType.html?buildTypeId=LuceneNet_Vs2015LuceneNetPortable)
-- I set that one up to wrap my head around what needed to change to run the new version of
the project. It still isn't quite perfect but it is getting there. Currently I am using build.ps1
to build things. I am still working on getting the tests to run successfully. It can easily
be made to accept the current versioning once we unify the codebase.
    
    The individual project builds and tests are at @synhershko 's request. Mechanically, the
[Lucene.net.core](https://teamcity.jetbrains.com/viewType.html?buildTypeId=LuceneNet_Core)
 build is the real build and test with the nightly generating the myget packages. At the end
of the day the build system has to take into account that we want individual packages for
the sub-projects.
    
    In terms of a path forward I suggest that we just get a clean build up with the core things
in place and then fix the tests -- as well as build out nuget packaging. How we want to build
it changes based on the new structure so we might as well get that in place and build on top
of it. 


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

Mime
View raw message