KengoTODA

# .circleci/config.yml

orbs:
  jq: circleci/jq@2.2.0

jobs:
  upload_coverage_report:
    docker:
      - image: google/cloud-sdk
    steps:

KengoTODA

resource "google_artifact_registry_repository" "file_hosting" {
  location      = local.region
  repository_id = "file-hosting"
  description   = "Docker registry for the file hosting service"
  format        = "DOCKER"
}

resource "google_artifact_registry_repository_iam_policy" "file_hosting" {
  location    = local.region
  repository  = google_artifact_registry_repository.file_hosting.name

KengoTODA

To integrate the Flix language into existing JVM language projects, I want to try to make a Gradle plugin to build, test, and package source codes written in Flix. To judge its possibility, and design its API, I want to ask the following questions:

1. Is it encouraged to deploy .fpkg files onto Maven Central or other registries?

   • I guess it is not. The latest Packager provides an installation mechanism which relies on GitHub project.
   • Probably the Flix is going to provide a golang-like module system? If so, is there any file to manage dependencies like go.mod?

2. Will Flix build system supports multiple kinds of dependnecy scope?

   • Java build tools such as Maven and Gradle provides compile, runtime, provided, api, implementation, test, and system etc.

• It is complex but valuable to minimize API surface and to

KengoTODA

Classfile /Users/kengo/Downloads/PatternMatchingForSwitch.class
  Last modified Jun 13, 2021; size 2141 bytes
  MD5 checksum 5049ca7e9689aad18b98cb25608936e1
  Compiled from "PatternMatchingForSwitch.java"
public class PatternMatchingForSwitch
  minor version: 65535
  major version: 61
  flags: (0x0021) ACC_PUBLIC, ACC_SUPER
  this_class: #68                         // PatternMatchingForSwitch
  super_class: #2                         // java/lang/Object

KengoTODA

import java.util.Arrays;

public class HashcodeTest {
    /**
     * A simple Record with an int array.
     */
    record Record(int[] array) {}

    /**
     * {@code Record#hashCode()} invokes not {@link Arrays#hashCode(int[])} but {@code int[].hashCode()}.

KengoTODA

SpotBugs3.1.xの現状と内部実装が抱える問題発表後に起こった変化のまとめ。

実績

• Maven Cental で 482,726 dl/mo (2021年1月度実績)。2年前は 約100,000 dl/mo (2019年1月度実績)だったので5倍弱に増加
• Mavenプロジェクトでの利用状況はmaven-pmd-pluginの37,000+件, soanr-maven-pluginの22,000+件に続く7,000+件の利用。Errorproneの6,000件よりは多い
• Gradleプロジェクトでの利用状況はsonarqubeの13,500件, pmdの8,000+件に続く3,300+件の利用。Errorponeの3,400+件

KengoTODA

digraph first {
  rankdir = LR
  "入力" -> "処理（ビルド）" -> "出力"
  "処理（ビルド）" [shape=square];
}

KengoTODA

package edu.umd.cs.findbugs.sarif;

import java.util.HashMap;
import java.util.Map;
import com.fasterxml.jackson.annotation.JsonAnyGetter;
import com.fasterxml.jackson.annotation.JsonAnySetter;
import com.fasterxml.jackson.annotation.JsonIgnore;
import com.fasterxml.jackson.annotation.JsonInclude;
import com.fasterxml.jackson.annotation.JsonPropertyOrder;

KengoTODA

digraph Issue493 {
  subgraph cluster_method_1 {
    label="#method";
    graph[style=dotted];
    edge1_0 [label="ALOAD (1)"];
    edge1_1 [label="javax/sql/DataSource#getConnection()Ljava/sql/Connection;"];
    edge1_2 [label="ASTORE (2)"];
    edge1_3 [label="class org.objectweb.asm.tree.LabelNode"];
    edge1_4 [label="java/lang/System#out (Ljava/io/PrintStream;)"];
    edge1_5 [label="java/io/PrintStream#println()V"];

KengoTODA

diff --git a/jspecify/build.gradle b/jspecify/build.gradle
index 676ae28..3b21c79 100644
--- a/jspecify/build.gradle
+++ b/jspecify/build.gradle
@@ -1,13 +1,13 @@
 plugins {
     id 'java-library'
     id 'maven-publish'
-    id 'com.diffplug.gradle.spotless' version '3.28.1'
-    id 'net.ltgt.errorprone' version '1.1.1'