semantic-versioning

When writing bower.json you can specify version numbers in your dependencies. Sometimes I see people writing { ... "devDependencies" : { "grunt" : "~0.3.13", } } What exactly does the ~ mean? Why not write >=0.3.13? Is this some sort of best practice? It's semver and the notation is the same as >=0.3.13 <0.4.0 , which will match all patch releases after and including 0.3.13 , but not 0.4.0 . This means you'll get bug fixes ( patch ), but not new features ( minor ). >=0.3.13 is not recommended as it will match anything above which will at some point break. 来源： https://stackoverflow.com

Is it possible to get the major version ( <Major>.<Minor>.<Patch> ) of the project.version ? For example if my version is 1.3.4 , I'd like to get 1 to later use it in a configuration of the same pom.xml Something like: <configuration> <name>project_name.${project.version:major}</name> </configuration> If not, what are the alternatives? Yuriy Nemtsov Found it. The build-helper-maven-plugin has the ability to parse-out the components of the version. <build> <plugins> <plugin> <groupId>org.codehaus.mojo</groupId> <artifactId>build-helper-maven-plugin</artifactId> <version>1.5</version>

Bower enables me to specify version requirements for packages using the following syntax: "dependencies": { "<name>": "<version>", }, But I have not been able to find what is the syntax to use for the <version> . I know that I can specify versions to be: greater than a certain version with ">1.0.0" greater than or equal to a version: ">=1.0.0" or in some range: "1.0.0 - 2.0.0" . I also know that there is a common version syntax containing the tilde: "~1.0.0" . But I am not sure what it means and whether it is the same as "=1.0.0" . I am also interested to know whether I am able to specify