For Maven Plugin 0.9.20, the native:metadata-copy task cannot be executed normally
#403
Assignees
Labels
Comments
|
@alvarosanchez Is there any additional information I need to provide? |
Merged
6 tasks
|
@linghengqian can you please provide the whole profile block you used to setup agent (from |
|
@dnestoro Hi, this is located at https://github.com/linghengqian/maven-v0920-metadatacopy-test/blob/master/pom.xml which I mentioned above. <?xml version="1.0" encoding="UTF-8"?>
<project xmlns="http://maven.apache.org/POM/4.0.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
<modelVersion>4.0.0</modelVersion>
<groupId>com.lingh</groupId>
<artifactId>maven-v0920-metadatacopy-test</artifactId>
<version>1.0-SNAPSHOT</version>
<properties>
<maven.compiler.source>17</maven.compiler.source>
<maven.compiler.target>17</maven.compiler.target>
<project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
</properties>
<dependencies>
<dependency>
<groupId>org.apache.shardingsphere</groupId>
<artifactId>shardingsphere-db-protocol-core</artifactId>
<version>5.3.1</version>
</dependency>
<dependency>
<groupId>org.mockito</groupId>
<artifactId>mockito-core</artifactId>
<version>4.11.0</version>
<scope>test</scope>
</dependency>
<dependency>
<groupId>org.junit.vintage</groupId>
<artifactId>junit-vintage-engine</artifactId>
<version>5.9.2</version>
<scope>test</scope>
</dependency>
<dependency>
<groupId>junit</groupId>
<artifactId>junit</artifactId>
<version>4.13.2</version>
<scope>test</scope>
</dependency>
<dependency>
<groupId>org.projectlombok</groupId>
<artifactId>lombok</artifactId>
<version>1.18.26</version>
<optional>true</optional>
</dependency>
<dependency>
<groupId>ch.qos.logback</groupId>
<artifactId>logback-classic</artifactId>
<version>1.2.11</version>
</dependency>
</dependencies>
<build>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-surefire-plugin</artifactId>
<version>3.0.0-M8</version>
</plugin>
</plugins>
</build>
<profiles>
<profile>
<id>native</id>
<build>
<plugins>
<plugin>
<groupId>org.graalvm.buildtools</groupId>
<artifactId>native-maven-plugin</artifactId>
<version>0.9.20</version>
<extensions>true</extensions>
<configuration>
<agent>
<defaultMode>Conditional</defaultMode>
<modes>
<conditional>
<userCodeFilterPath>${project.basedir}/user-code-filter.json</userCodeFilterPath>
<parallel>true</parallel>
</conditional>
</modes>
<metadataCopy>
<disabledStages>
<stage>main</stage>
</disabledStages>
<merge>false</merge>
<outputDirectory>${project.basedir}/src/test/resources/test-output-dir</outputDirectory>
</metadataCopy>
</agent>
<metadataRepository>
<enabled>true</enabled>
</metadataRepository>
</configuration>
</plugin>
</plugins>
</build>
</profile>
</profiles>
</project> |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Before reporting
Describe the bug
A clear and concise description of what the bug is.
Make sure that you have read the documentation and that you are using the latest plugin version.
native:metadata-copytask cannot be executed normally. Although there is no error in the log, the final json file is not output to the customoutputDirectory.To Reproduce
When possible, provide a link to a repository which reproduces the issue, with instructions on how to use.
The reproducer must make use of either the Maven or Gradle plugin.
Steps to reproduce the behavior:
Please use backticks to properly format code.
If possible please attach a complete reproducer here (either as a zip file or as a link to public repository/branch).
Expected behavior
A clear and concise description of what you expected to happen.
Logs
Add logs to help explain your problem.
Please use backticks to properly format big logs. Example:
System Info (please complete the following information):
Windows]Linux22.0 CE]22.3.1 CE17]17native-gradle-plugin:0.9.10]native-maven-plugin:0.9.20Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: