This is an automated email from the ASF dual-hosted git repository. yishayw pushed a commit to branch develop in repository https://gitbox.apache.org/repos/asf/royale-compiler.git
commit f2889488c802fec307cc8b1f6d6a8aa60089bf52 Author: Yishay Weiss <[email protected]> AuthorDate: Fri Jul 24 08:52:31 2026 +0100 compiler-jburg-types: add royale-release profile (mirrors compiler-build-tools) --- compiler-jburg-types/pom.xml | 67 +++++++++++++++++++++++++++++++++++++++++++- 1 file changed, 66 insertions(+), 1 deletion(-) diff --git a/compiler-jburg-types/pom.xml b/compiler-jburg-types/pom.xml index 6990f8472..ae8010f05 100644 --- a/compiler-jburg-types/pom.xml +++ b/compiler-jburg-types/pom.xml @@ -171,7 +171,7 @@ <fileSet> <directory>${project.build.directory}</directory> <includes> - <include>royale-compiler-parent-${project.version}-source-release.zip</include> + <include>apache-royale-${project.artifactId}-${project.version}-source-release.zip</include> </includes> </fileSet> </fileSets> @@ -180,6 +180,71 @@ </plugins> </build> </profile> + <profile> + <id>royale-release</id> + <properties> + <!-- Ensure the royale-release plugin is enabled when running release:perform --> + <release-profiles>apache-release</release-profiles> + </properties> + + <!-- Redirect the deployment to a local directory --> + <!-- Note: using the 'altReleaseDeploymentRepository' and alike were ignored in the release:perform phase --> + <distributionManagement> + <repository> + <id>apache.releases.https</id> + <name>Apache Release Distribution Repository</name> + <!-- + 'maven.multiModuleProjectDirectory' is a property introduced with maven 3.3.1 ... + don't worry if your IDE is complaining. + Also this will be set to the 'target/checkout' directory the output will be in + 'target/local-release-dir'. + --> + <url>file://${maven.multiModuleProjectDirectory}/../local-release-dir</url> + </repository> + </distributionManagement> + + <build> + <plugins> + <!-- Generate the effective poms for this build --> + <plugin> + <groupId>org.apache.maven.plugins</groupId> + <artifactId>maven-help-plugin</artifactId> + <executions> + <execution> + <id>generate-effective-pom</id> + <phase>compile</phase> + <goals> + <goal>effective-pom</goal> + </goals> + <configuration> + <output>${project.build.directory}/effective.pom</output> + </configuration> + </execution> + </executions> + </plugin> + </plugins> + <pluginManagement> + <plugins> + <!-- We require the release manager to manually login an sign using his credentials --> + <plugin> + <groupId>org.apache.maven.plugins</groupId> + <artifactId>maven-gpg-plugin</artifactId> + <configuration> + <skip>true</skip> + </configuration> + </plugin> + <!-- We require the release manager to login and push the changes using his credentials --> + <plugin> + <groupId>org.apache.maven.plugins</groupId> + <artifactId>maven-release-plugin</artifactId> + <configuration> + <pushChanges>false</pushChanges> + </configuration> + </plugin> + </plugins> + </pluginManagement> + </build> + </profile> </profiles> </project>
