versioning

i would like to release a snapshot project 'foo-1.0-SNAPSHOT' using the maven release plugin. The project depends on a 3rd party module 'bar-1.0-SNAPSHOT' which is not released yet. I use the option 'allowTimestampedSnapshots' in my project's pom.xml to allow timestamped snapshots but i assume that the 3rd party module (bar) is not timestamped unless i build it myself as maven still complains about unresolved SNAPSHOT dependencies. Is there a way to release the project foo regardless of dependent SNAPSHOT projects and if not how could i add a timestamp to the 3rd party project? Gareth Davis

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, thanks in advance. Most places use something like this: Major Release.Minor Release.Hot Fix.Build Your version numbers would look like 1.5.0.15, etc. A lot of free software uses a three point system: X.Y.Z where X is for compatibility breaking releases. Y is for other releases, with even numbers being stable and odd numbers

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 effect of: #define MAJORVER 4 #define MINORVER 23 #define SOURCEVER 965 We would then use these

I'm looking for a version numbering scheme that expresses the extent of change, especially compatiblity. Apache APR , for example, use the well known version numbering scheme <major>.<minor>.<patch> example: 4.5.11 Maven suggests a similar but more detailed schema: <major>.<minor>.<patch>-<qualifier>-<build number> example: 4.5.11-RC1-3732 Where is the Maven versioning scheme defined? Are there conventions for qualifier and build number? Probably it is a bad idea to use maven but not to follow the Maven version scheme ... What other version numbering schemes do you know? What scheme would you

I have a new ASP/.NET Core project that I publish to NuGet. What's the recommended approach to keep the version tags in x.csproj and x.nuspec in sync when I publish a new package? With new .csproj format, you can add all of the information to generate NuGet packages in the .csproj file. There is no longer a reason to use a .nuspec file. <Project Sdk="Microsoft.NET.Sdk"> <PropertyGroup> <AssemblyTitle>My NuGet Project</AssemblyTitle> <Description>Something I decided to release on NuGet.</Description> <PackageTags>my;project;whatever;</PackageTags> <Authors>Me (who else)</Authors> <RepositoryUrl

If I need to go from this service contract: [ServiceContract(Namespace="http://api.x.com/Svc1")] public interface IService1 { [OperationContract(Name = "AddCustomer")] bool AddCustomer(DTOCustomer1 customer); } to this: [ServiceContract(Namespace="http://api.x.com/Svc1")] public interface IService1 { [OperationContract(Name = "AddCustomer")] bool AddCustomer(DTOCustomer2 customer); } and according to this good article: Versioning WCF I understand that when data contract is changed there is a need of defining a new vs of data contract in new namespace followed by defining a new vs of service

I'm using Json.Net to serialize some application data. Of course, the application specs have slightly changed and we need to refactor some of the business object data. What are some viable strategies to migrate previously serialized data to our new data format? For example, say we have orignally had a business object like: public class Owner { public string Name {get;set;} } public class LeaseInstrument { public ObservableCollection<Owner> OriginalLessees {get;set;} } We serialize an instance of a LeaseInstrument to a file with Json.Net. Now, we change our business objects to look like: public

I have a text file that contains only one line with a version number of my application. An example would be 1.0.0.1. I would like to increment the build number. Using my example I would get the output 1.0.0.2 in the same text file. How can I do it with PowerShell? Matt This might be over kill, but it shows the use of the type [version] which will save the need to do string manipulation. $file = "C:\temp\File.txt" $fileVersion = [version](Get-Content $file | Select -First 1) $newVersion = "{0}.{1}.{2}.{3}" -f $fileVersion.Major, $fileVersion.Minor, $fileVersion.Build, ($fileVersion.Revision + 1