version

How can I sort file names by version numbers?

烂漫一生 提交于 2019-11-27 20:32:31
In the directory "data" are these files: command-1.9a-setup command-2.0a-setup command-2.0c-setup command-2.0-setup I would like to sort the files to get this result: command-1.9a-setup command-2.0-setup command-2.0a-setup command-2.0c-setup I tried this find /data/ -name 'command-*-setup' | sort --version-sort --field-separator=- -k2 but the output was command-1.9a-setup command-2.0a-setup command-2.0c-setup command-2.0-setup The only way I found that gave me my desired output was tree -v /data How could I get with sort the output in the wanted order? Edit: It turns out that Benoit was sort

How can I test when a feature was added to Perl?

橙三吉。 提交于 2019-11-27 20:28:22
Are there any services similar to codepad that will allow you to test Perl constructs on old versions of perl? Ideally, a system where you could enter an expression and it will tell you the oldest version of perl that it will work with. Of course it's possible to use CPANTS for this, but that seems like an abuse of the service (if only for making the BackPan bigger). And it could take several days/weeks to get decent test coverage on old versions. You might find Perl::MinimumVersion helpful. Use the provided perlver utility to scan your code. I think that if I was concerned, I'd build salient

Maven version with a property

痞子三分冷 提交于 2019-11-27 20:23:09
I have big Maven (Tycho) project witch about 400 plug-ins. We have specified version of application in each POM file. Is there a way how to specify the version for all POM:s only on one place? I would expect some think like: <properties> <buildVersion>1.1.2-SNAPSHOT</buildVersion> </properties> .... <version>${buildVersion}</version> We have parent pom.xml : <modelVersion>4.0.0</modelVersion> <groupId>company</groupId> <artifactId>build.parent</artifactId> <version>1.1.2-SNAPSHOT</version> <packaging>pom</packaging> Then in each POM is reference to parent POM: <parent> <artifactId>build.parent

Play Framework 2.1: Use play.api.Configuration in Build.scala

↘锁芯ラ 提交于 2019-11-27 19:31:26
In the top answer to Play Framework 2: Read the application version defined in Build.scala it's suggested that the application version number be specified in conf/application.conf and loaded in Build.scala through play.api.Configuration . I'm using Play 2.1-RC2 and getting the following error message when building: [error] [...]/project/Build.scala:7: object Configuration is not a member of package play.api [error] val conf = play.api.Configuration.load(new File(".")) I think this might be caused by the fact that with Play 2.1 build dependencies have to be specified as plugins to SBT, and play

Compile a version agnostic DLL in .NET

三世轮回 提交于 2019-11-27 19:11:39
Scenario I have two wrappers around Microsoft Office, one for 2003 and one for 2007. Since having two versions of Microsoft Office running side by side is "not officially possible" nor recommended by Microsoft, we have two boxes, one with Office 2003 and the other with Office 2007. We compile the wrappers separately. The DLLs are included in our solution, each box has the same checkout but with either Office 2003 or 2007 "unloaded" so it doesn't attempt to compile that particular DLL. Failure to do that will throw errors on compilation due to the Office COM DLLs not available. We use .NET 2.0

SVN / Subversion 1.7 and Eclipse Subversive & JavaHL

笑着哭i 提交于 2019-11-27 18:59:59
I have just upgraded to TortoiseSVN 1.6.99, Build 21709, (Subversion 1.7.0, -dev). I am having problem in my Eclipse Subversive 0.7.9.I20100512-1900 & JavaHL 1.6.15. Have tried to update my Eclipse plugins. Anyone have an solution? Error at Eclipse: Share project was failed. Unsupported working copy format svn: The path 'XXX' appears to be part of a Subversion 1.7 or greater working copy. Please upgrade your Subversion client to use this working copy. You are aware of the Subversion 1.7 state? It is currently a beta-2 state and not intended for production? Furthermore it couldn't work with the

Retrieving version of an MSI file (built with WiX)

怎甘沉沦 提交于 2019-11-27 18:28:16
问题 I've created an MSI file with WiX. The source WiX file contains the version information like this: <Product Id="..." Name="..." Language="1033" Version="1.0.0.1" Manufacturer="..." UpgradeCode="..."> The MSI file seem to work OK: it installs, it uninstalls, it upgrades when I increase the version number, etc. However, when I attempt to get the version information about this file by calling the MsiGetFileVersion() API, it returns error 1006 (ERROR_FILE_INVALID File does not contain version

Determine if O/S is Windows 7

你说的曾经没有我的故事 提交于 2019-11-27 18:17:17
问题 Working on a project and need to be able to determine whether the O/S is Windows 7, Vista or default to XP. I understand I could run into Win2K and earlier versions but let's just say that's not a concern as other code will catch that before it gets to this point. My application will be in C++ for the time being using VS2005. I've found articles and sample code alike but they seem way bloated for my uses. Just looking for a quick and dirty return. http://msdn.microsoft.com/en-us/library

How can I find the version of an installed Perl module?

三世轮回 提交于 2019-11-27 17:29:52
How do you find the version of an installed Perl module? This is in an answer down at the bottom, but I figure it important enough to live up here. With these suggestions, I create a function in my .bashrc function perlmodver { perl -M$1 -e 'print "Version " . $ARGV[0]->VERSION . " of " . $ARGV[0] . \ " is installed.\n"' $1 } Why are you trying to get the version of the module? Do you need this from within a program, do you just need the number to pass to another operation, or are you just trying to find out what you have? I have this built into the cpan (which comes with perl) with the -D

How to find the .NET framework version of a Visual Studio project?

别等时光非礼了梦想. 提交于 2019-11-27 17:21:59
I have a project in Visual Studio. How can I find out which .NET Framework version it's for? It depends which version of Visual Studio: In 2002 , all projects use .Net 1.0 In 2003 , all projects use .Net 1.1 In 2005 , all projects use .Net 2.0 In 2008 , projects use .Net 2.0, 3.0, or 3.5; you can change the version in Project Properties In 2010 , projects use .Net 2.0, 3.0, 3.5, or 4.0; you can change the version in Project Properties In 2012 , projects use .Net 2.0, 3.0, 3.5, 4.0 or 4.5; you can change the version in Project Properties Newer versions of Visual Studio support many versions of