- the combine.* attributes belong to the configuration elements child elements but in the child not the parent pom
- let's say we have a prepared configuration for some plugin build::pluginmanagement in the parent pom and the combine rules are applied
to some more specific configuration of this plugin inside a profile in the child pom then we need to specify this profile in the mvn call
to convince us:
mvn -Ptheprofile -f thesubmodule/pom.xml help:effective-pom| less
(use the search functionality/
andn
/SHIFT-n
to navigate to the right occurrences) - IMHO the
combine.children=append
rule doesn't really make sense for configuration elements that have children of heterogeneous names, i. e.systemPropertyVariables
, here the effect in case some entry already existed in the default configuration another one of the same name would be added i. e. you had<someEntrySays>this</someEntrySays>
(from parent pom) and[...]combine...="append"[...]that
(from child po
public class WicketJaasSession extends AuthenticatedWebSession { | |
public static final String ROLES_GROUP_NAME = "ROLES"; | |
public static final String ROLES_PREFIX = "ROLE_"; | |
public static final String APPLICATION_POLICY_NAME = "blog"; | |
private Subject subject; | |
private Roles roles = new Roles(); | |
@SuppressWarnings("deprecation") | |
public WicketJaasSession(AuthenticatedWebApplication app, Request request) { |
// Gremlin user-defined defined tree steps | |
// inTree() and outTree() | |
// by James Thornton, http://jamesthornton.com | |
// see https://groups.google.com/d/topic/gremlin-users/iCPUifiU_wk/discussion | |
// closure can't have the same name as the defined step | |
tree = { vertices -> | |
def results = [] |
#!/usr/bin/env python | |
import boto | |
from boto.route53.record import ResourceRecordSets | |
import logging | |
conn = boto.connect_ec2() | |
DNS_EXCLUSION_TAG = 'ExcludeFromDNS' # If this tag exists on an instance, no DNS values will be populated | |
DNS_TAGS = ['ShortName', 'Name'] # This is the list of instance tags we want to populate DNS entries from | |
DNS_SUFFIX = 'YOUR_SUBDOMAIN_HERE' # Suffix under which to create DNS records | |
ROUTE53_ZONE_ID = 'YOUR_ZONE_ID_HERE' # The zone id from route53 of the zone we will be adding these entries under |
#!/bin/bash | |
# CSV to JSON converter using BASH | |
# original script from http://blog.secaserver.com/2013/12/convert-csv-json-bash/ | |
# thanks SecaGuy! | |
# Usage ./csv2json.sh input.csv > output.json | |
input=$1 | |
[ -z $1 ] && echo "No CSV input file specified" && exit 1 | |
[ ! -e $input ] && echo "Unable to locate $1" && exit 1 |
package io.github.ajmath; | |
import io.dropwizard.logging.AbstractAppenderFactory; | |
import ch.qos.logback.classic.LoggerContext; | |
import ch.qos.logback.classic.spi.ILoggingEvent; | |
import ch.qos.logback.contrib.jackson.JacksonJsonFormatter; | |
import ch.qos.logback.contrib.json.classic.JsonLayout; | |
import ch.qos.logback.core.Appender; | |
import ch.qos.logback.core.ConsoleAppender; | |
import ch.qos.logback.core.Layout; |
/** | |
* See [Media Types](https://www.iana.org/assignments/media-types/media-types.xhtml) of IANA. | |
*/ | |
object MimeTypes { | |
enum class Application(val extensions: Array<String>, val mimeType: String) { | |
/** AbiWord document */ | |
ABI_WORD(arrayOf(".abw"), "application/x-abiword"), | |
/** Archive document (multiple files embedded) */ |
When a Spring Boot app starts up with default (INFO) logging, there are some noticeable gaps (pauses). It's worth focusing on the gaps when looking for efficiency savings because of the amount of time they take, and because no-one bothered to log anything, so the chances are the app is doing something repetitive. We can tweak the logging levels to try and fill in the gaps and find out what is going on in there.
Basic empty web app with actuators has three such gaps:
0 1410ms
|------|---------------------------|-----|------|---------|--------|--------|
| 578 | |144(5)| | 133(6) |
This is about documenting getting Linux running on the late 2016 and mid 2017 MPB's; the focus is mostly on the MacBookPro13,3 and MacBookPro14,3 (15inch models), but I try to make it relevant and provide information for MacBookPro13,1, MacBookPro13,2, MacBookPro14,1, and MacBookPro14,2 (13inch models) too. I'm currently using Fedora 27, but most the things should be valid for other recent distros even if the details differ. The kernel version is 4.14.x (after latest update).
The state of linux on the MBP (with particular focus on MacBookPro13,2) is also being tracked on https://github.com/Dunedan/mbp-2016-linux . And for Ubuntu users there are a couple tutorials (here and here) focused on that distro and the MacBook.
Note: For those who have followed these instructions ealier, and in particular for those who have had problems with the custom DSDT, modifying the DSDT is not necessary anymore - se
node { | |
echo 'Results included as an inline comment exactly how they are returned as of Jenkins 2.121, with $BUILD_NUMBER = 1' | |
echo 'No quotes, pipeline command in single quotes' | |
sh 'echo $BUILD_NUMBER' // 1 | |
echo 'Double quotes are silently dropped' | |
sh 'echo "$BUILD_NUMBER"' // 1 | |
echo 'Even escaped with a single backslash they are dropped' | |
sh 'echo \"$BUILD_NUMBER\"' // 1 | |
echo 'Using two backslashes, the quotes are preserved' | |
sh 'echo \\"$BUILD_NUMBER\\"' // "1" |