There are many ways to do this, but on Intel Edison I found that the easiest way is using the /etc/init.d directory.
Create a file in
/etc/init.d
cd /etc/init.d
#!/usr/bin/env bash | |
#################################################### | |
# Ubuntu Linux configuration for WSL 2 # | |
# Author: Dino Lupo # | |
# Release Date: 2020/08/30 # | |
#################################################### | |
# Install Ubuntu latest with WSL version 2 | |
# then launch it and copy this file in Ubuntu with | |
# |
{ | |
"$schema": "https://aka.ms/terminal-profiles-schema", | |
"alwaysShowTabs": true, | |
"defaultProfile": "{61c54bbd-c2c6-5271-96e7-009a87ff44bf}", | |
"initialCols": 120, | |
"initialRows": 30, | |
"requestedTheme": "dark", | |
"keybindings": [ | |
{ "command": "closeTab", "keys": ["ctrl+w"] }, | |
{ "command": "newTab", "keys": ["ctrl+t"] }, |
Keeping your site up to date with the GitHub Pages gem
bundle update github-pages
Build your local Jekyll site
bundle exec jekyll serve
Here's an example of how to embed a Gist on GitHub Pages:
{% gist 5555251 %}
All you need to do is copy and paste the Gist's ID from the URL (here 5555251
), and add it to a gist
tag surrounded by {%
and %}
.
Car car1 = new Car(); | |
car1.setMake("Toyota"); | |
car1.setModel("Prius"); | |
car1.setStock("20"); | |
Car car2 = new Car(); | |
car2.setMake("Tesla"); | |
car2.setModel("Model S"); | |
car2.setStock("2"); | |
List<Car> inventory = new ArrayList<>(); |
JsonArray contacts = ...; | |
JsonArray femaleNames = | |
contacts.getValuesAs(JsonObject.class).stream() | |
.filter(x->"F".equals(x.getString("gender"))) | |
.map(x->(x.getString("name")) | |
.collect(JsonCollectors.toJsonArray()); |
import javax.ejb.ApplicationException; | |
import javax.ws.rs.WebApplicationException; | |
import javax.ws.rs.core.Response; | |
/** | |
* | |
* @author Dino Lupo | |
*/ | |
@ApplicationException(rollback = true) | |
public class TestWebException extends WebApplicationException { |
# When you’re using Maven in an IDE you often find the need for your IDE to resolve source code and Javadocs for your library dependencies. There’s an easy way to accomplish that goal. | |
mvn dependency:sources | |
mvn dependency:resolve -Dclassifier=javadoc | |
# The first command will attempt to download source code for each of the dependencies in your pom file. | |
# The second command will attempt to download the Javadocs. | |
# Maven is at the mercy of the library packagers here. So some of them won’t have source code packaged and many of them won’t have Javadocs. |