versioning

We are using PHPCI and composer. The server which runs PHPCI is on PHP 5.3. For a project we added the Facebook PHP SDK, using composer. It requires PHP 5.4. Composer gets triggered by PHPCI and get executed. But because the CI server just got PHP 5.3 composer failed with the error message: facebook/php-sdk-v4 4.0.9 requires php >=5.4.0 -> no matching package found. This let fail my build in PHPCI, of course. Is there a possibility to skip this requirement? Maybe by adding an option to composer.json? Or a parameter to composer.phar call? I've found the option: composer install --ignore

I am pretty new to Node.js and I am facing the following issue. My middleware started with the link api/v1/login and a bunch of endpoints. Then api/v1.1 introduced 2 more endpoints. api/v1.2 is now the last and got some new endpoints. How shall I handle this api versioning in an efficient way? How do you make endpoints from a version available to the next versions as well? First of all, if you are building a REST API and you have just started, you may want to consider using Restify instead of Express. While Express can certainly be used for this purpose, Restify has been designed with all the

Here's a fictional scenario with some populated data. For tax purposes, my fictional company must retain records of historical data. For this reason, I've included a version column to the table. TABLE EMPLOYEE: (with personal commentary) |ID | VERSION | NAME | Position | PAY | +---+---------+------------+----------+-----+ | 1 | 1 | John Doe | Owner | 100 | Started company | 1 | 2 | John Doe | Owner | 80 | Pay cut to hire a coder | 2 | 1 | Mark May | Coder | 20 | Hire said coder | 2 | 2 | Mark May | Coder | 30 | Productive coder gets raise | 3 | 1 | Jane Field | Admn Asst| 15 | Need office

I maintain an open source project and publish its releases to The Central Repository . I just published oshi-core-2.6 . The versioning in my pom.xml for that release reads: <groupId>com.github.dblock</groupId> <artifactId>oshi-core</artifactId> <version>2.6</version> My code requires Java 8 due to the Date/Time functions. To support a user's request, just prior to this release, I released a Java 7 compatible version using the threeten backport, with the following in its pom.xml : <groupId>com.github.dblock</groupId> <artifactId>oshi-core</artifactId> <version>2.6-m-java7</version> How Version

In my android application ,user has to register by agreeing the terms and condition giving their email id. If user upgrade the application to next version, I should not get the agreement page or email registration window. I am controlling it using global variables but if user upgrade application to newer version, global variables get reset, so user get the agreement page and registration window again. So how can I do this? Thanks for help in advance. You Have two ways to storing your data @ local media. Shared Preference SQLite Database When i should use Shared Preference ? If your number of

I'm a developer who has never needed to worry about the implementation of source control systems / branching / merging etc... I'm searching for book which explains these concepts but is aimed at clearcase users. From searching amazon - the book " IBM ClearCase 7.0: Master the Tools that Monitor, Analyze and Manage Software Configurations by Marc Girod and Tatiana Shpichko (26 Apr 2011) " seems to b a good read. Any recommendations ? Thanks. VonC You will find a good introduction regarding merges in ClearCase with " How files and directories are merged " The particularity of a merge with

I'm targeting the framework 4.0 and this works fine on the development machine, I can see at startup the form with the textbox displaying binded message in it. But when I deploy the executable on any other machine it won't work claiming that "cannot bind to the property or column Note on the DataSource". The very strange thing is that it works well on any machine if I compile targeting the 3.5 framework. Someone could explain this odd behaviour? What can be different between development environment and client machines? namespace Demo { public partial class Form1 : Form { private readonly

Near as I can tell, CouchDB revisions are not to be treated like revisions in the document versioning sense of the word. From glancing at other posts, they seem to be regarded as transient data that exists until a coarse-grained compact operation is called. My question is, if I am interested in using CouchDB to maintain documents, as well as a version-history of those documents, should I allow that to be handled natively by CouchDB revisions, or should I build a layer on-top that will survive a compact operation? I am thinking the latter, simply because Couch does not replicate revisions of

This is one of those "I know I shouldn't do this but it's oh so convenient." questions. Sorry about that. I plan to use CouchDB for storing a bunch of documents and keeping their entire revision history. CouchDB does the versioning automatically, but it is strongly discouraged for programmer's use : "You cannot rely on document revisions for any other purpose than concurrency control." From what I've found on the CouchDB wiki, the versions can get deleted either during compaction or during replication . As far as I can tell, Compaction must always be triggered manually and Replication occurs