生成的Maven属性MAVEN_NPM_AUTH在maven-resources-plugin中无法替换的原因

Great that you’ve already verified the property is visible outside the antrun plugin—let’s dig into why the resources plugin isn’t picking it up, and walk through fixes:

1. You haven’t enabled resource filtering (most common culprit!) #

By default, the maven-resources-plugin doesn’t replace ${...} placeholders in resource files. You need to explicitly enable filtering for the directory containing your file with the MAVEN_NPM_AUTH placeholder.

Check your pom’s <build> section—make sure filtering is turned on for the relevant resource set:

<build>
  <resources>
    <resource>
      <directory>src/main/resources</directory>
      <!-- This line is critical for property replacement -->
      <filtering>true</filtering>
      <!-- Optional: Narrow down to specific files if needed -->
      <includes>
        <include>**/your-file-with-auth-placeholder</include>
      </includes>
    </resource>
  </resources>
</build>

If filtering is disabled, the plugin will copy your files as-is without touching any placeholders.

2. Subtle property scope issues with Antrun #

Even with exportAntProperties=true, using project.setProperty() directly in the Ant JavaScript script can sometimes have scope quirks in Maven’s internal property system. The property might be visible in the console/debug output, but not properly propagated to later plugins like resources.

A more reliable approach is to write the property to a temporary file, then load it into Maven’s project context using the properties-maven-plugin:

Step 1: Update your antrun to write the property to a file #

<plugin>
  <artifactId>maven-antrun-plugin</artifactId>
  <executions>
    <execution>
      <id>encode-user-pass-base64</id>
      <phase>initialize</phase>
      <goals>
        <goal>run</goal>
      </goals>
      <configuration>
        <target>
          <script language="javascript">
          <![CDATA[
            // ... your existing code to generate base64data ...
            // Write the property to a temp file in the build directory
            var propsFile = new java.io.File(project.getBasedir(), "target/temp-auth.properties");
            var writer = new java.io.FileWriter(propsFile);
            writer.write("MAVEN_NPM_AUTH=" + base64data);
            writer.close();
          ]]>
          </script>
        </target>
      </configuration>
    </execution>
  </executions>
</plugin>

Step 2: Load the property with properties-maven-plugin #

Add this plugin right after your antrun configuration in the pom:

<plugin>
  <groupId>org.codehaus.mojo</groupId>
  <artifactId>properties-maven-plugin</artifactId>
  <executions>
    <execution>
      <id>load-temp-auth-properties</id>
      <phase>initialize</phase>
      <goals>
        <goal>read-project-properties</goal>
      </goals>
      <configuration>
        <files>
          <file>${project.build.directory}/temp-auth.properties</file>
        </files>
      </configuration>
    </execution>
  </executions>
</plugin>

This ensures the property is loaded directly into Maven’s core project property context, so the resources plugin will definitely see it.

3. Lifecycle phase misalignment (less likely, but worth checking) #

Your antrun is bound to initialize, which should run before process-resources (the default phase for maven-resources-plugin). But if you’ve customized the resources plugin’s execution phase to run before initialize, the property won’t exist yet when the resources plugin runs.

Double-check your resources plugin config for any custom phase settings. If you see something like this, adjust the phase to process-resources or later:

<plugin>
  <artifactId>maven-resources-plugin</artifactId>
  <executions>
    <execution>
      <phase>initialize</phase> <!-- This runs BEFORE your antrun! -->
      ...
    </execution>
  </executions>
</plugin>

4. Non-default property delimiters #

If your resource file uses non-standard delimiters (instead of ${MAVEN_NPM_AUTH}), the resources plugin won’t recognize the placeholder. Double-check that your placeholder matches the default format, or explicitly configure delimiters in the resources plugin:

<plugin>
  <artifactId>maven-resources-plugin</artifactId>
  <configuration>
    <delimiters>
      <delimiter>${*}</delimiter>
      <!-- Add other delimiters if you use them -->
    </delimiters>
  </configuration>
</plugin>

内容的提问来源于stack exchange，提问作者Ionut