jesperfj

A better way to set up Java web apps

If you're building a Java web app that you yourself or your organization will be deploying then you can save yourself a lot of trouble by avoiding the whole build-to-war + deploy-to-server approach. Instead, you should build your web app as a normal Java application with an embedded web app server. Don't build a WAR, just compile the code and serve the files out of their source location. This has the following advantages:

• You can code and test iteratively because you don't have to copy files and create war packages every time you make a change. This is similar to what the mvn jetty:run command is being used for by many developers today.
• You run the same exact code in production as you do in development. Hopefully I don't have to elaborate on the advantages of that. Most developers today use mvn jetty:run or similar to achieve a quick, iterative dev cycle. But come time for deployment, they build a WAR and throw it over the wall to be deployed in some app server

brettporter

#!/usr/bin/env ruby

require 'tempfile'
require 'optparse'

def parse_version(text)
  if (text.match(/^\s*<version>\s*(.*?)\s*<\/version>\s*$/))
    $1
  else
    nil

JakeWharton

package com.squareup.example;

public abstract BaseActivity extends SherlockActivity {
  private final ScopedBus scopedBus = new ScopedBus();

  protected ScopedBus getBus() {
    return scopedBus;
  }

  @Override public void onPause() {

kellyrob99

import org.apache.maven.shared.dependency.analyzer.ClassAnalyzer
import org.apache.maven.shared.dependency.analyzer.DefaultClassAnalyzer
import org.apache.maven.shared.dependency.analyzer.DependencyAnalyzer
import org.apache.maven.shared.dependency.analyzer.ProjectDependencyAnalysis
import org.apache.maven.shared.dependency.analyzer.asm.ASMDependencyAnalyzer
import org.gradle.api.Project
import org.gradle.api.artifacts.ConfigurationContainer
import org.gradle.api.artifacts.ResolvedArtifact
import org.gradle.api.artifacts.ResolvedDependency

regis-leray

#!/bin/bash 

# How to perform a release with git & maven following the git flow conventions
# ----------------------------------------------------------------------------
# Finding the next version: you can see the next version by looking at the
#	version element in "pom.xml" and lopping off "-SNAPSHOT". To illustrate,
#	if the pom's version read "0.0.2-SNAPSHOT", the following instructions would
#	perform the release for version "0.0.2" and increment the development version
#	of each project to "0.0.3-SNAPSHOT".
#

chrismccoy

# alias to edit commit messages without using rebase interactive
# example: git reword commithash message
reword = "!f() {\n  GIT_SEQUENCE_EDITOR=\"sed -i 1s/^pick/reword/\" GIT_EDITOR=\"printf \\\"%s\\n\\\" \\\"$2\\\" >\" git rebase -i \"$1^\";\n git push -f;\n}; f"

# sort list of git repos with gh cli
gh repo list --limit 300 --json name -q '.[].name' | sort

# count total commits in a repo
git rev-list --all --count

hgomez

Scripted Jenkins Plugins install

Jenkins has a very rich catalog of plugins and it's quite easy to install and update them via UI. BTW, when you want to add tons of plugin via UI, it's a fairly long and boring procedure.

Hopefully, mass installation (or update) could be easy using a simple bash script (curl/python required) :

• https://raw.githubusercontent.com/hgomez/devops-incubator/master/forge-tricks/batch-install-jenkins-plugins.sh

Create a file containing plugins to be installed (or updated), ie iplugins :

chris95x8

dependencies {
    compile 'com.android.support:appcompat-v7:21.+'
    compile 'com.wrapp.floatlabelededittext:library:0.0.5'
}

dlew

<!-- You can change the parent around to whatever you normally use -->
<style name="DebugColors" parent="Theme.AppCompat">

    <!-- System colors -->
    <item name="android:windowBackground">@color/__debugWindowBackground</item>

    <item name="android:colorPressedHighlight">#FF4400</item>
    <item name="android:colorLongPressedHighlight">#FF0044</item>
    <item name="android:colorFocusedHighlight">#44FF00</item>
    <item name="android:colorActivatedHighlight">#00FF44</item>

seanhinkley

package com.boot;
import org.springframework.boot.autoconfigure.SpringBootApplication;
import org.springframework.boot.SpringApplication;
//make sure spring boot doesn't attempt 2.1 config
@SpringBootApplication(exclude={org.springframework.boot.autoconfigure.thymeleaf.ThymeleafAutoConfiguration.class} )
public class AppApplication {
	public static void main(String[] args) {
		SpringApplication.run(AppSecurityApplication.class, args);
	}
}