m2e is not copying resources anymore

[ahoehma]

Not sure but I noticed since a while that in my eclipse the resources/test-resources are not copied/filtered etc. anymore .
When I run cmdline maven everything is fine.

[HannesWell]

I noticed that recently as well that it did not Work recently.
Debugging revealed that, at least in my case, the reason was that M2E failed to load the Mojo or realm with an Exception.
Since it only happened ocasionally I assumed that it was only a local short-term (Network?) problem.
But maybe that was a false assumption.

Do you see any related entries in the Error-Log View?

[ahoehma]

I find nothing in the error-log :(

[laeubi]

Do you have a project to reproduce the issue?

[ahoehma]

Not really. Its a big reactor and under closed source. May you can tell me if you have some specific maven-plugins in mind which could be maybe wrong configured, like the resource-plugin etc. But I can swear it was working :)

[ahoehma]

I switched in the pom editor to "effective pom" and grabbed these "resources" stuff out of it:

<resources>
      <resource>
        <directory>D:\Dev\git\coc\spice-configuration-cluster\datamodel-adapter\src\main\resources</directory>
      </resource>
    </resources>
    <testResources>
      <testResource>
        <directory>D:\Dev\git\coc\spice-configuration-cluster\datamodel-adapter\src\test\resources</directory>
      </testResource>
    </testResources>

<plugin>
        <artifactId>maven-resources-plugin</artifactId>
        <version>3.3.0</version>
        <executions>
          <execution>
            <id>default-testResources</id>
            <phase>process-test-resources</phase>
            <goals>
              <goal>testResources</goal>
            </goals>
          </execution>
          <execution>
            <id>default-resources</id>
            <phase>process-resources</phase>
            <goals>
              <goal>resources</goal>
            </goals>
          </execution>
        </executions>
      </plugin>

looks pretty normal to me

[ahoehma]

I have also a lifecycle mapping in the module

<plugin>
          <groupId>org.eclipse.m2e</groupId>
          <artifactId>lifecycle-mapping</artifactId>
          <version>1.0.0</version>
          <configuration>
            <lifecycleMappingMetadata>
              <pluginExecutions>
                <pluginExecution>
                  <pluginExecutionFilter>
                    <groupId>com.github.victools</groupId>
                    <artifactId>jsonschema-maven-plugin</artifactId>
                    <versionRange>[4.18.0,)</versionRange>
                    <goals>
                      <goal>generate</goal>
                    </goals>
                  </pluginExecutionFilter>
                  <action>
                    <execute>
                      <runOnConfiguration>true</runOnConfiguration>
                      <runOnIncremental>false</runOnIncremental>
                    </execute>
                  </action>
                </pluginExecution>
              </pluginExecutions>
            </lifecycleMappingMetadata>
          </configuration>
        </plugin>

[tehrnhoefer]

FWIW, I am running into the same problem (took me quite a while to realize what's going on).
Running maven on the command line successfully copies resources, not so much in Eclipse.

M2E - Maven Integration for Eclipse 2.1.2.20221130-2239 org.eclipse.m2e.feature.feature.group Eclipse.org - m2e
Eclipse IDE for Java Developers 4.26.0.20221201-1200 epp.package.java Eclipse Packaging Project

[ahoehma]

@KaRkY aha ... I have .mvn in my root project folder :)

[egeorges92]

I had the same problem and found out that if you have ".mvn" folder at the root of the project it fails to copy resources.

Thank you for the tips. It's solved my issue. It stuck me for a while :-(

[ahoehma]

@egeorges92 do you removed the .mvn? Just asking. Because this is not an option for me I need .mvn for extensions.xml.

[egeorges92]

Hello @ahoehma , yes, I remove all of these {.mvn, mvnw, mvnw.cmd).
I don’t use enforcer plugin, it’s not an issue for me.
The only solution is to use the old way, have a look at Maven documentation : https://maven.apache.org/configure.html

[ahoehma]

@egeorges92 I'm using .mvn/extensions.xml to work with "maven-git-versioning-extension".