Rename master to main

Workflows, issue template link, release skill, issue triager and docs
now use main. README links to the sources are relative, so they no longer
point to the old fvarrui repo and package paths (404 since the 2.0.0
package rename).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

Author: fvarrui

.claude/agents/issue-triager.md

@@ -8,7 +8,7 @@ You triage GitHub issues of `javapackager/JavaPackager` (local clone, normally o
 
 ## Context
 
-JavaPackager is a hybrid Maven/Gradle plugin (Java 8) that packages Java apps as native Windows/macOS/GNU/Linux apps and installers. Before starting, read `.minispec/core/architecture.md` and `.minispec/core/conventions.md`. Released code is on `master`; unreleased work is on `devel`. List it with `git log --oneline origin/master..origin/devel` and inspect commits with `git show <sha>`.
+JavaPackager is a hybrid Maven/Gradle plugin (Java 8) that packages Java apps as native Windows/macOS/GNU/Linux apps and installers. Before starting, read `.minispec/core/architecture.md` and `.minispec/core/conventions.md`. Released code is on `main`; unreleased work is on `devel`. List it with `git log --oneline origin/main..origin/devel` and inspect commits with `git show <sha>`.
 
 ## For each issue
 

.claude/skills/release/SKILL.md

@@ -5,11 +5,11 @@ description: Prepare and publish a JavaPackager release to Maven Central and Git
 
 # Release
 
-Publishing a release is irreversible (Maven Central never deletes versions), so confirm with the user before each outward step: pushing to `master`, `releaseToCentral`, publishing the GitHub release, and closing issues.
+Publishing a release is irreversible (Maven Central never deletes versions), so confirm with the user before each outward step: pushing to `main`, `releaseToCentral`, publishing the GitHub release, and closing issues.
 
 ## 1. Release notes
 
-- Source: `git log --oneline --no-merges origin/master..origin/devel`, the `fix-*` notes in `.minispec/features/`, the ADRs, and `release-*.md`.
+- Source: `git log --oneline --no-merges origin/main..origin/devel`, the `fix-*` notes in `.minispec/features/`, the ADRs, and `release-*.md`.
 - Audience: plugin users. In English, following the user's Markdown rules, in the style of earlier releases (`gh release view <tag> --repo javapackager/JavaPackager`).
 - Sections, in this order: Breaking changes (with a "How to upgrade" section and ready-to-copy snippets), New features, Fixed issues (`#n` references), Maintenance.
 - Leave out regressions that only existed in `devel` and never reached a release.
@@ -27,7 +27,7 @@ Publishing a release is irreversible (Maven Central never deletes versions), so
 ## 3. Publish
 
 1. Set `version` in `build.gradle` to `X.Y.Z` (no `-SNAPSHOT`), update the sample's `javapackager.version`, commit.
-2. Merge `devel` into `master` and push (ask first). Point the draft release's target to `master`.
+2. Merge `devel` into `main` and push (ask first). Point the draft release's target to `main`.
 3. The user runs `./gradlew releaseToCentral`. It uploads through the Portal OSSRH Staging API in `user_managed` mode; then they review the deployment at https://central.sonatype.com/publishing/deployments and click **Publish**.
 4. Verify it's on Maven Central (it can take a while to appear):
 

.github/ISSUE_TEMPLATE/config.yml

@@ -1,5 +1,5 @@
 blank_issues_enabled: false
 contact_links:
   - name: Documentation
-    url: https://github.com/javapackager/JavaPackager/blob/master/README.md
+    url: https://github.com/javapackager/JavaPackager/blob/main/README.md
     about: Check the documentation before opening an issue.

.github/workflows/dependency-submission.yml

@@ -5,7 +5,7 @@ name: Dependency submission
 
 on:
   push:
-    branches: [ devel, master ]
+    branches: [ devel, main ]
   workflow_dispatch:
 
 permissions:

.github/workflows/smoke-tests.yml

@@ -2,9 +2,9 @@ name: Smoke tests
 
 on:
   push:
-    branches: [ devel, master ]
+    branches: [ devel, main ]
   pull_request:
-    branches: [ devel, master ]
+    branches: [ devel, main ]
   workflow_dispatch:
 
 jobs:

.minispec/features/dependabot-alerts.md

@@ -2,7 +2,7 @@
 
 ## Goal
 
-Clear the Dependabot alerts on `master`: fix the ones that reach users, and fix or dismiss with a reason the ones only in the plugin's own build.
+Clear the Dependabot alerts on `main`: fix the ones that reach users, and fix or dismiss with a reason the ones only in the plugin's own build.
 
 ## Context
 

CLAUDE.md

@@ -20,7 +20,7 @@ Use the wrapper (`./gradlew` or `gradlew.bat` on Windows).
 | `./gradlew updateNativeJavaApplicationStub` | Re-download the native macOS launchers (`nativeJavaApplicationStub*`) into `src/main/resources/mac` from a [javapackager/nativeJavaApplicationStub](https://github.com/javapackager/nativeJavaApplicationStub) release |
 | `./gradlew updateWhyJavaLauncher` | Re-download `JavaLauncher.exe` into `src/main/resources/windows` |
 
-There are no unit tests, so there is no way to run a single test. Changes are verified by the smoke tests in `.github/workflows/smoke-tests.yml`, which run on every push to `devel`/`master`: they package `samples/hello-world` (one sample with both `pom.xml` and `build.gradle`) with Maven on GNU/Linux, Windows and macOS (each `macStartup`) and with Gradle on each platform, and run `.github/scripts/check-*-app.sh`. Build with a JDK 17+ (a JRE can't compile).
+There are no unit tests, so there is no way to run a single test. Changes are verified by the smoke tests in `.github/workflows/smoke-tests.yml`, which run on every push to `devel`/`main`: they package `samples/hello-world` (one sample with both `pom.xml` and `build.gradle`) with Maven on GNU/Linux, Windows and macOS (each `macStartup`) and with Gradle on each platform, and run `.github/scripts/check-*-app.sh`. Build with a JDK 17+ (a JRE can't compile).
 
 `compileJava` triggers `generatePluginDescriptor`, which runs an embedded Maven against the generated POM to produce `META-INF/maven/plugin.xml` from the `@Mojo`/`@Parameter` annotations.
 

README.md

@@ -6,7 +6,7 @@
 JavaPackager is a hybrid plugin for **Maven** and **Gradle** which provides an easy way to package Java applications in native Windows, MacOS or GNU/Linux executables, and generate installers for them.
 
 > [!IMPORTANT] 
-> See [JavaPackager changes and fixes](https://github.com/fvarrui/JavaPackager/releases).
+> See [JavaPackager changes and fixes](https://github.com/javapackager/JavaPackager/releases).
 
 > [!WARNING]
 > Since 2.0.0 the plugin's `groupId` is `io.github.javapackager`, the Gradle plugin id is `io.github.javapackager` and the Gradle task type is `io.github.javapackager.gradle.PackageTask` (up to 1.7.6: `io.github.fvarrui`, `io.github.fvarrui.javapackager.plugin` and `io.github.fvarrui.javapackager.gradle.PackageTask`). Update them in your `pom.xml` or `build.gradle` when upgrading.
@@ -15,7 +15,7 @@ JavaPackager is a hybrid plugin for **Maven** and **Gradle** which provides an e
 
 This project has been actively maintained for many years, but due to lack of time, I can no longer dedicate the attention it deserves. To keep it alive and evolving, I’m looking for contributors to help with its maintenance.  
 
-:point_right: **[Join the discussion](https://github.com/fvarrui/JavaPackager/discussions/460)**  
+:point_right: **[Join the discussion](https://github.com/javapackager/JavaPackager/discussions/460)**  
 
 Any help is welcome! Thank you for your support.
 
@@ -177,7 +177,7 @@ By default it will generate next artifacts in `${outputDirectory} ` folder:
 | `displayName`              | :x:                | `${project.name}` or `${name}`                                                                                                                     | App name to show.                                                                                                                                                                         |
 | `envPath`                  | :x:                |                                                                                                                                                    | Defines PATH environment variable in GNU/Linux and MacOS startup scripts.                                                                                                                 |
 | `extra`                    | :x:                |                                                                                                                                                    | Map with extra properties to be used in customized Velocity templates, accesible through `$info.extra` variable.                                                                          |
-| `fileAssociations`         | :x:                | [`FileAssociation[]`](https://github.com/fvarrui/JavaPackager/blob/master/src/main/java/io/github/fvarrui/javapackager/model/FileAssociation.java) | Associate file extensions or MIME types to the app.                                                                                                                                       |
+| `fileAssociations`         | :x:                | [`FileAssociation[]`](src/main/java/io/github/javapackager/model/FileAssociation.java) | Associate file extensions or MIME types to the app.                                                                                                                                       |
 | `forceInstaller`           | :x:                | `false`                                                                                                                                            | If `true`, skips operating system check when generating installers.                                                                                                                       |
 | `generateInstaller`        | :x:                | `true`                                                                                                                                             | Generates an installer for the app.                                                                                                                                                       |
 | `jdkPath`                  | :x:                | `${java.home}`                                                                                                                                     | JDK used to generate a customized JRE. It allows to bundle customized JREs for different platforms.                                                                                       |
@@ -219,7 +219,7 @@ By default it will generate next artifacts in `${outputDirectory} ` folder:
 
 ### Plugin assets
 
-Any [asset used by JavaPackager](https://github.com/fvarrui/JavaPackager/tree/master/src/main/resources), such as application icons or templates, can be replaced just by placing a file with the same name in `${assetsDir}` folder organized by platform.
+Any [asset used by JavaPackager](src/main/resources), such as application icons or templates, can be replaced just by placing a file with the same name in `${assetsDir}` folder organized by platform.
 
 ```bash
 ${assetsDir}/
@@ -243,7 +243,7 @@ ${assetsDir}/
 ```
 
 > [!WARNING] 
-> If icon is not specified , it will use an [icon by default](https://raw.githubusercontent.com/fvarrui/JavaPackager/master/src/main/resources/linux/default-icon.png) for all platforms.
+> If icon is not specified , it will use an [icon by default](src/main/resources/linux/default-icon.png) for all platforms.
 
 #### Templates
 
@@ -276,9 +276,9 @@ ${assetsDir}/
     └── wxs.vtl                        # WiX Toolset WXS template to generate MSI
 ```
 
-An object called `info` of type [`PackagerSettings`](https://github.com/fvarrui/JavaPackager/blob/master/src/main/java/io/github/fvarrui/javapackager/packagers/PackagerSettings.java) is passed to all templates with all plugin properties.
+An object called `info` of type [`PackagerSettings`](src/main/java/io/github/javapackager/packagers/PackagerSettings.java) is passed to all templates with all plugin properties.
 
-You can use [default templates](https://github.com/fvarrui/JavaPackager/tree/master/src/main/resources) as examples to create your own templates, and use the `extra` map property to add your own properties in the plugin settings to use in your custom templates (e.g. `${info.extra["myProperty"]}`).
+You can use [default templates](src/main/resources) as examples to create your own templates, and use the `extra` map property to add your own properties in the plugin settings to use in your custom templates (e.g. `${info.extra["myProperty"]}`).
 
 ### Additional JVM options at runtime
 
@@ -405,7 +405,7 @@ cd JavaPackager
 > [!IMPORTANT]
 > Build the plugin with a JDK 17 or newer (a JRE is not enough). The plugin itself targets Java 8.
 
-Every push to `devel` and `master` runs the smoke tests (`.github/workflows/smoke-tests.yml`): they package [`samples/hello-world`](samples/hello-world) with the Maven and the Gradle plugin on GNU/Linux, Windows and macOS and check the generated apps and installers.
+Every push to `devel` and `main` runs the smoke tests (`.github/workflows/smoke-tests.yml`): they package [`samples/hello-world`](samples/hello-world) with the Maven and the Gradle plugin on GNU/Linux, Windows and macOS and check the generated apps and installers.
 
 ## How to publish the plugin to Maven Central