versioning

I've spent far too much time trying to figure this out. This should be the simplest thing and everyone who distributes Java applications in jars must have to deal with it. I just want to know the proper way to add versioning to my Java app so that I can access the version information when I'm testing, e.g. debugging in Eclipse and running from a jar. Here's what I have in my build.xml: <target name="jar" depends = "compile"> <property name="version.num" value="1.0.0"/> <buildnumber file="build.num"/> <tstamp> <format property="TODAY" pattern="yyyy-MM-dd HH:mm:ss" /> </tstamp> <manifest file="$

I'm looking for a plugin/act to allow versioning of my models. It's kind of difficult to find a list of the available solutions. So far I gathered: acts_as_versioned simply_versioned vestal_versions The last two solutions only require a single version table - this sounds nice, but I've got a bad feeling about how the ease of migrations will be affacted by this (because they serialize states as a string). On the other hand, acts_as_versioned is a little bit dusty (last commit in January). Are there any recent experiences with any of these? Or other solutions (or forks) I might have overlooked?

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/response for version 2: ==> GET /api/system-info HTTP/1.1 Accept: application/vnd.COMPANY.systeminfo-v2+json <

I have been given 2 pre-compiled dlls: Common.Data, Version=1.0.0.0, Culture=neutral, PublicKeyToken=f3b12eb6de839f43, processorArchitecture=MSIL Common.Data, Version=2.0.0.0, Culture=neutral, PublicKeyToken=f3b12eb6de839f43, processorArchitecture=MSIL Example of differences in API: And I'm trying to load both into a single project to do something like this: extern alias v10; extern alias v20; private static void UpgradeUser() { // Load old user var userOld = new v10::Common.Data.UserData(); userOld.loadData("user.dat"); // Create new user var userNew = new v20::Common.Data.UserData(); // Copy

Would the following be a viable strategy for implementing versioning(using "example" as a sample document type): Have one original document where the type field is named example_original. Subsequent changes to the document all have type example_change and the id of example_original document as a key. The change would also carry a timestamp. Keep one doc with type example_current that is the result of example_original with all example_change "applied". A new example_change document would automatically be applied to this document. Finding a specific version would consist in retrieving the

I am normally writing all parts of the code in C# and when writing protocols that are serialized I use FastSerializer that serializes/deserializes the classes fast and efficient. It is also very easy to use, and fairly straight-forward to do "versioning", ie to handle different versions of the serialization. The thing I normally use, looks like this: public override void DeserializeOwnedData(SerializationReader reader, object context) { base.DeserializeOwnedData(reader, context); byte serializeVersion = reader.ReadByte(); // used to keep what version we are using this.CustomerNumber = reader