[
https://issues.apache.org/jira/browse/LUCENENET-456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shad Storhaug resolved LUCENENET-456.
-------------------------------------
Resolution: Done
Assignee: Shad Storhaug (was: michael herndon)
Fix Version/s: (was: Lucene.Net 3.6)
Lucene.Net 4.8.0
This is now done here:
https://teamcity.jetbrains.com/viewType.html?buildTypeId=LuceneNet_PortableBuilds_LuceneNetRelease
This TeamCity build versions and packages everything into 2 release artifacts
as zip files and also labels the repository with the tag. It even creates a
custom build.bat file that only builds the specific version of the release.
>From there, you can download the files to your local system, sign them, and
>add them to the appropriate repositories.
> Create a Build Target that outputs compiled artifacts in apache release format
> ------------------------------------------------------------------------------
>
> Key: LUCENENET-456
> URL: https://issues.apache.org/jira/browse/LUCENENET-456
> Project: Lucene.Net
> Issue Type: Improvement
> Components: Lucene.Net Core
> Reporter: Prescott Nasser
> Assignee: Shad Storhaug
> Priority: Trivial
> Fix For: Lucene.Net 4.8.0
>
>
> When building in "release" the artifacts are sent to various folders. It
> would be great if we could model the output of the release to mirror the
> output we use when cutting a release (saving some time).
> /bin/Contrib/*files
> /bin/Demo/*files
> /bin/Lucene.Net.dll
> /doc/Contrib/*files
> /doc/Demo/*files
> /doc/Lucene.Net.xml
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
