versioning

What should go in the 'default' branch of a Hg repository? [closed]

由 旧巷老猫 提交于 2019-11-30 17:38:08
问题 Closed . This question is opinion-based. It is not currently accepting answers. Want to improve this question? Update the question so it can be answered with facts and citations by editing this post. Closed 4 years ago . In large Libre Source software projects, versioned with Mercurial or similar DVCS tools, which of the following is considered to be more conventional: Keeping the latest "stable" version of the software in the default branch. Tagging each release in default so you know which

How do I share a label value between multiple CruiseControl.NET builds?

由 心不动则不痛 提交于 2019-11-30 15:35:55
I have two projects set up in CruiseControl.NET: CI build and nightly build. Both of them execute the same NAnt script, but with different parameters. The CruiseControl.NET label (currently generated by the DefaultLabeler ) is embedded into AssemblyInfo as the build part of the version (for example, MajorVersion.MinorVersion.CCNET_Label.SVN_Revision ). For more consistent versioning I would like both projects to share the same CruiseControl.NET label value. I have investigated the labelers that are available as part of the CruiseControl.NET installation, but I could not find one that does what

How to force re-download of Silverlight XAP file

由 人盡茶涼 提交于 2019-11-30 14:21:54
I'm trying to figure out how to force the browser to re-download a .xap file if the new version is available and yet the old one is still cached in the browser. I've seen the other thread: How do you force Firefox to not cache or re-download a Silverlight XAP file? The best solution seems to be: protected void Page_Load(object sender, EventArgs e) { var versionNumber = Assembly.GetExecutingAssembly().GetName().Version.ToString(); this.myApp.Source += "?" + versionNumber; } However, I don't get the this.myApp part. What kind of object is that? I'm sorry for re-opening this, but I wish people

How to insert version numbers in our java jars, that a user can access?

由 老子叫甜甜 提交于 2019-11-30 14:03:28
We have a library that gets released with a different version number every couple of weeks. The problem is that in order to store the version number in our jars we have a version.txt file that just contains the version number and then gets included into the build. This seems like the wrong way to do this but I can't come up with a better solution. What is a better way to store the version number in our jar's so that if a user calls me up I can easily find out the version of our product they are using? Firstly -- make sure your program or tool can some SHOW the version number. But where does it

Getting application version from pom

由 ￣綄美尐妖づ 提交于 2019-11-30 13:17:05
问题 I have a rest endpoint used to return information about application (so far only app version) But so far this info is hardcoded, and it's pretty easy to forget to change it. I will be better to retrieve app version from pom or manifest file. Is there any project that brings such functionality? 回答1: There is amazing project named Appinfo, please use it and enjoy! (It has an ugly page, I know - but it works :) AppInfo allows to automatically feed your application with a current version number,

Is there a 'Get Latest Version' preview in TFS? (Like VSS 'Get' command)

由 纵饮孤独 提交于 2019-11-30 12:48:32
My question relates to Team Foundation Server (TFS) and specifically, is there any way to know which files have changed on the server before doing a 'Get Latest Version (Recursive)? In Visual Source Safe (VSS), you could do a 'Get' (I think) which showed you all the files which were being considered for the update and which files we're changed on the server (an consequently would be updated during the get). This functionality seems to be completely missing! Also, when I do a 'Get Latest Version' in TFS, there doesn't seem to be any notification that any things occurred, other than the blur of

Easy REST resource versioning in JAX-RS based implementations?

由 别来无恙 提交于 2019-11-30 11:53:02
问题 Best practice for REST resource versioning is putting version information into Accept/Content-Type headers of HTTP request leaving URI intact. Here is the sample request/response to REST API for retrieving system information: ==> GET /api/system-info HTTP/1.1 Accept: application/vnd.COMPANY.systeminfo-v1+json <== HTTP/1.1 200 OK Content-Type: application/vnd.COMPANY.systeminfo-v1+json { “session-count”: 19 } Pay attention that version is specified in MIME type. Here is another request

SVN Revision Version in .NET Assembly w/ out CC.NET

由 ￣綄美尐妖づ 提交于 2019-11-30 10:26:44
问题 Is there any way to include the SVN repository revision number in the version string of a .NET assembly? Something like Major.Minor.SVNRev I've seen mention of doing this with something like CC.NET (although on ASP.NET actually), but is there any way to do it without any extra software? I've done similar things in C/C++ before using build batch scripts, but in was accomplished by reading the version number, then having the script write out a file called "ver.h" everytime with something to the

Version numbering basics? [closed]

由 两盒软妹~` 提交于 2019-11-30 10:26:25
问题 Closed . This question is opinion-based. It is not currently accepting answers. Want to improve this question? Update the question so it can be answered with facts and citations by editing this post. Closed 2 years ago . Suppose I have a web application with some basic functions. I want to market it. So I would like to assign a version number - something like 0.0.1. What I want to know is are there any constraints that should apply to that numbering system? Hope you understood my question,

ASP.NET API versioning

由 六眼飞鱼酱① 提交于 2019-11-30 10:24:52
I'm new to ASP.NET but I'm looking to implement some versioning for a new API I'm about to start. I'm not even sure if what I'm looking for is possible but I'm after a very clean version method using a header variable. Ideally I want to be able to have a versions folder within the code structure and different folders containing the different API versions within that. Each version folder would contain a full copy of the core API code so I'd know there would never be any conflicts etc. I know this would inflate the code but it's worth to keep it very clean and there would only be over 2-3
订阅 versioning