jlengrand/moderne-docs
1
0
Fork 0
mirror of https://github.com/jlengrand/moderne-docs.git synced 2026-03-10 08:31:21 +00:00
Code Issues Packages Projects Releases Wiki Activity

GitBook: [#97] No subject

Browse Source
This commit is contained in:
Jonathan Schneider
2022-08-08 14:29:58 +00:00
committed by gitbook-bot
parent 47b996e0ea
commit 2512949ef6
1 changed files with 6 additions and 15 deletions
Download Patch File Download Diff File Expand all files Collapse all files

21
how-to/integrating-private-code.md
View File

@@ -20,7 +20,7 @@ In the pom.xml or build.gradle, add this entry to the `plugins` section to apply
<plugin>
<groupId>io.moderne</groupId>
<artifactId>moderne-maven-plugin</artifactId>
<version>0.16.0</version>
<version>0.18.0</version>
<configuration>
<!-- Supports all of the same functionality as the OpenRewrite plugin -->
<activeRecipes>
@@ -45,7 +45,7 @@ In the pom.xml or build.gradle, add this entry to the `plugins` section to apply
{% code title="build.gradle" %}
```groovy
plugins {
id("io.moderne.rewrite") version("0.17.0")
id("io.moderne.rewrite") version("0.18.0")
}
// OpenRewrite and recipe modules are published to Maven Central
@@ -58,12 +58,6 @@ rewrite {
// Supports all of the same functionality as the OpenRewrite plugin
}
```
In multi-project builds the behavior of the plugin will differ slightly depending on whether it is applied to the root project.
When applied to the root project, the plugin applies itself to all projects in the build.
When applied to a sub-project, the plugin applies itself only to that project.
So if you want only certain projects within your multi-project build to be searchable and refactorable in the Moderne SaaS, you can apply the plugin only to those projects.
{% endcode %}
{% endtab %}
{% endtabs %}
@@ -80,18 +74,16 @@ Gradle users can continue invoking `gradlew rewriteDryRun` and `gradlew rewriteR
## Step 2: Configure Publishing
The Moderne SaaS requires that the AST artifacts produced by the build plugin be published to your artifact repository.
This may require you to publish AST artifacts from projects that do not currently publish anything.
The Moderne SaaS requires that the AST artifacts produced by the build plugin be published to your artifact repository. This may require you to publish AST artifacts from projects that do not currently publish anything.
{% tabs %}
{% tab title="Maven" %}
Typically, no additional publishing configuration is required for Maven builds.
{% endtab %}
{% tab title="Gradle" %}
Each project the plugin is applied to will have a `Jar` task named `moderneJar` which produces the AST jar in the project's build folder.
This is the file that needs to be published to your artifact repository to enable Moderne SaaS integration.
Each project the plugin is applied to will have a `Jar` task named `moderneJar` which produces the AST jar in the project's build folder. This is the file that needs to be published to your artifact repository to enable Moderne SaaS integration.
{% code title="single project build" %}
```groovy
plugins {
@@ -116,7 +108,6 @@ publishing {
{% endtab %}
{% endtabs %}
## Step 3: Build and publish the next version of your project
Now whenever your project is published there will be a file with a "jar" extension and an "ast" classifier published alongside any other publications. So for a project named "example" publishing version "1.0", you can expect to see a file named `example-1.0-ast.jar` alongside the normal `example-1.0.jar`.