versioning

How to: database versioning with maven2?

送分小仙女□ 提交于 2019-12-04 11:12:04
问题 I am finding any maven plugin for versioning database changes. 回答1: There are a few plugins that offer some support for this task: Maven LiquiBase Plugin Maven Database Migration Plugin DbMaintain Maven Plugin (a plugin for DbMaintain, the famous tool from Unitils) I don't have much experience with them, we currently use a custom tool to apply our change scripts. But the Maven Database Migration Plugin is a serious candidate to replace it. LiquiBase is pretty famous but also different,

Basic version control for MySQL table

别等时光非礼了梦想. 提交于 2019-12-04 10:57:28
I'm trying to setup a (I thought) fairly simple versioning system for static html pages on a site. The goal is to keep previous versions of the content, then restore to them if needed (I guess basically creating a new version that's a duplicate of an old one), and optionally to toss out data older than X versions ago. The table's setup is fairly straightforward: id reference_id (string/used to determine what page the item pertains to) content (document/html page sized amount of data) e_user (user who changed it last) e_timestamp (when it was changed) I just want to have something setup to

PaperTrail: info_for_paper_trail outside the context of a controller

佐手、 提交于 2019-12-04 10:53:42
I am using the paper_trail gem for versioning my models. So far, my model depends on the info_for_paper_trail method in ApplicationController : class ApplicationController < ActionController::Base # Extra columns to store along with PaperTrail `versions` def info_for_paper_trail { revision_id: @revision.id, revision_source_id: @revision_source.id } end end This works great in context of the controller, but is there a way that I can replicate this sort of thing outside the context of the controller (e.g., a delayed job)? I tried creating a virtual attribute called revision and passing a proc

Web Api 2 API not recognizing Multiple Attributes for Routing (Versioning)

穿精又带淫゛_ 提交于 2019-12-04 10:33:11
问题 I'm trying to implement both Attribute Routing and the VersionedRoute from RoutingConstaints Sample but when I use both on a controller, the versioned attribute no longer works. What would I need to modify on the attribute to get it to play nice with Attribute Routing? For code example download the sample project (or just look at the few files from the above link) and then modify the routes as such: // When I use the RoutePrefix, VersionedRoute no longer works (Sending "Api-Version" through

How to make version autoincrement in the latest .NET Core tooling?

时光总嘲笑我的痴心妄想 提交于 2019-12-04 10:16:23
I am using the latest (as of today) .NET Core tooling. There, you specify version in an <Version> MSBuild property. However, unlike [assembly:AssemblyVersion], this does not appear to support wildcards. How do I make version increment automatically in the same way? Explaining why this is a bad idea, and what should be done instead would also be a good answer. natemcmaster The Version property in MSBuild does not support asterisks (wildcard) format as project.json did. However, with MSBuild you can compute a version in other ways. There is no one right way to do it, but here is one approach. We

How to remove local git history after a commit?

一个人想着一个人 提交于 2019-12-04 09:59:15
I would like to switch from Dropbox to the open source Sparkleshare. It uses git for the syncing and versioning. If say I had a 1GB file I deleted in my folder, it stays within the history of the local .git folder. But I would like to have this kind of heavy data on the server and not the client. How can I commit my repository and delete the local one with git? Many thanks! Solution removing the history git fetch --depth=1 to prune the old commits. This makes the old commits and their objects unreachable. git reflog expire --expire-unreachable=now --all . To expire all old commits and their

Clearing App Data on update

大憨熊 提交于 2019-12-04 09:39:31
I need to clear(equivalent to Clear Data in App Settings ) all the old data in the app programmatically when the user updates the app from Google Play Store or any other sources. This is because I don't need any of the existing data from the old app since I have changed everything in the new app compared to the old one. I thought of implementing a version check at the app startup, but I can't find a way to get the app's previous versionCode or versionName . The only way I figured out to clear the data is to check the lastUpdateTime at the time of publishing the app. But it's not reliable since

Maven artifact version for patches

烂漫一生 提交于 2019-12-04 09:37:35
问题 I'm currently working on Maven tools for Project Dash. One of the open issues is how to handle mistakes. Maven central says: Nothing published ever changes. This is because Maven never tries to figure out whether a release has changed (unlike for SNAPSHOTs). But I might have to create a new "release" of, say, part of Eclipse 3.6.2. Which version number should I use? 3.6.2.1 , 3.6.2-1 , 3.6.2_1 , 3.6.2pl1 ? Why? 回答1: The convention for version numbers is major.minor.build . major is

What version number scheme for poorly planned, branched, and schizophrenic application

99封情书 提交于 2019-12-04 07:52:30
I'm looking for a version numbering scheme/pattern/system for an application that is currently branched into several versions with shell game style release dates. This has made versioning a nightmare. I'd like to just use the typical Major.Minor.Revision however this will break down for me quickly the way things are presently run around here. Here is my inventory... 1.0.0 - Production version. 1.0.1 - Production revision version with bug fixes. 1.1.0 - Production minor version with new features due in July (regulations compliance, must be done). 1.2.0 - Production minor version with new

Simple “check for update” library in java

送分小仙女□ 提交于 2019-12-04 07:31:44
I'm using Eclipse RCP, but, mainly because i have total control of the UI (removed all contributions, made Preferences from scratch, etc) i just cannot accept the complexity and demand of the included UPDATE MANAGER (also, i use PLUGINS not features, and the app Plugin must be EXTRACTED - though i could get arround this last issue). Anyway, on a first approach i just want to check IF there is a newer version of the app available. The logical way would be to check against a file (xml?) on a server. Is there a good library and example out there? Thanks. Eclipse now supports p2, a much more