version

I'm looking for a grunt plugin that will automatically change the references to static assets (js/css) inside an html file like this: <link rel="stylesheet" type="text/css" href="style.css?v=12345678" /> <script src="script.js?v=12345678"></script> I searched at the gruntjs.com/plugins -> "version", but it seems that all of them change the actual version of the files instead of references to them. Am I missing it? Is there a plugin that can perform this task? For this I use grunt-filerev for the versionning and grunt-usemin for the automatic update of the references in source files. These two

This question already has an answer here: Is there way to use two PHP versions in XAMPP? 17 answers I made a backup file for my php projects then uninstall the old xampp(php 5.x.x) . After that, I try to install the latest xampp version(php 7.0.1) and put the backup file from my old xampp to run into the new one including its database. The problem is that, when I try to run my old file I encounter lot of errors. It seems there are lots of code that are obsolete to the new php version. What is the best way to run my old file again ? I think I might reinstall the old xampp but I also want to use

Normally we build android package in debug mode with the command ant debug and got the apk filename AppName-debug.apk . Is there any way to generate the apk file in the format of AppName-debug-<version-number>.apk directly without 'mv' command? Thanks. I have done this in an automated way, by using the info from the Android manifest. My approach was to modify the local project ant build.xml file to import a custom copy of the master build.xml file, in the latest version of the SDK the master file that is imported into your local file is located at <SDK>/tools/ant/build.xml (was android_rules

I used node.js for a development project a few years ago, and this app is somewhat "mothballed" for the time being — it needs to stay online, it needs to stay secure, but it shouldn't need much attention. It is currently running on node.js v0.10.32, but I would now like invest in a "final" migration to a Long Term Support (LTS) release so it will be easier to maintain for the foreseeable future. At first glance, the node.js homepage makes it look like v4.4.5 is obviously the only available LTS release: However if I click that LTS schedule link, it tells a different story. As far as I can tell,

I am trying to create a PHP script to get the app version from Android APK file. Extracting XML file from the APK (zip) file and then parsing XML is one way, but I guess it should be simpler. Something like PHP Manual , example #3. Any ideas how to create the script? Christopher Orr If you have the Android SDK installed on the server, you can use PHP's exec (or similar) to execute the aapt tool (in $ANDROID_HOME/platforms/android-X/tools ). $ aapt dump badging myapp.apk And the output should include: package: name='com.example.myapp' versionCode='1530' versionName='1.5.3' If you can't install

I'm trying to install lxml . I've had a look at the website, and version 2.2.8 looked reasonable to me but when I did easy_install lxml , it installed version 2.3.beta1 which is not really what I want I presume. What is the best way to fix this and how can I force easy_install to install a particular version? (Mac os x 10.6) I believe the way to specify a version would be like this: easy_install lxml==2.2.8 I (and most other Python users I suspect) stopped using easy_install and started using pip some time ago, so a solution in those terms is: easy_install pip pip install lxml==2.2.8 ( pip has

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

I am developing a desktop app using Java and Swing Application Framework. I have an application about box and I'd like to have that box contain some indication of what version is being tested. My preference is for that value to be changed in an automated fashion. I'm using CruiseControl to build the application triggered off the commits to SVN. What mechanism to others use to do this job? Is there an about box version number library or set of ant related tools that I can just drop in place in my build process? I'm not looking for deployment options or anyway to automatically check for updates