Bad format of sealed interfaces extending other interfaces about formatter-maven-plugin HOT 9 CLOSED

We haven't yet released a version of this plugin based on 2023-03. Can you try using a snapshot of this plugin, from the head commit of this repo's main branch?

from formatter-maven-plugin.

It would also be helpful to know what you've set your language compliance to in the plugin's configuration, or if you have set maven.compiler.release property at all.

from formatter-maven-plugin.

This is my plugin configuration, where ${formatter-maven-plugin.version} is 2.22.0:

<plugin>
	<groupId>net.revelc.code.formatter</groupId>
	<artifactId>formatter-maven-plugin</artifactId>
	<version>${formatter-maven-plugin.version}</version>
	<configuration>
		<configFile>${session.executionRootDirectory}/formatter.xml</configFile>
		<encoding>UTF-8</encoding>
		<lineEnding>LF</lineEnding>
	</configuration>
	<executions>
		<execution>
			<id>format</id>
			<goals>
				<goal>format</goal>
			</goals>
		</execution>
	</executions>
</plugin>

from formatter-maven-plugin.

Ok, you are right: I see here that Eclipse 4.27 is not supported yet. Heve you already defined a milestone for the new release?

from formatter-maven-plugin.

@mirkoscotti We are about to release... but I don't know if it will fix your issue. You could verify by trying a snapshot, as previously suggested, unless you just want to wait and see. Also consider looking at compiler compliance options to ensure your config is set up correctly. I had thought the options defaulted to maven.compiler.release, but it seems they might default to maven.compiler.source. See the config. It's possible that it does actually work, but you aren't setting the compliance level appropriate for the formatter to understand the correct version of the Java source.

from formatter-maven-plugin.

I added compilerCompliance to the configuration, but did not work, so I will wait for the new version

<plugin>
	<groupId>net.revelc.code.formatter</groupId>
	<artifactId>formatter-maven-plugin</artifactId>
	<version>${formatter-maven-plugin.version}</version>
	<configuration>
		<configFile>${session.executionRootDirectory}/formatter.xml</configFile>
		<encoding>UTF-8</encoding>
		<lineEnding>LF</lineEnding>
		<compilerCompliance>17</compilerCompliance>
	</configuration>
	<executions>
		<execution>
			<id>format</id>
			<goals>
				<goal>format</goal>
			</goals>
		</execution>
	</executions>
</plugin>

from formatter-maven-plugin.

I do not know if this can be useful, but my compiler configuration in pluginManagement is this:

<plugin>
	<groupId>org.apache.maven.plugins</groupId>
	<artifactId>maven-compiler-plugin</artifactId>
	<version>${maven-compiler-plugin.version}</version>
	<configuration>
		<release>${java.version}</release>
	</configuration>
</plugin>

where ${java.version} is 17

from formatter-maven-plugin.

This plugin definitely wouldn't be affected by the maven-compiler-plugin's configuration. However, an alternate way of setting maven-compiler-plugin's configuration is through the use of properties, some of which do also affect this plugin.

  <properties>
    <maven.compiler.release>11</maven.compiler.release>
    <maven.compiler.source>11</maven.compiler.source>
    <maven.compiler.target>11</maven.compiler.target>
  </properties>

I checked our source code, and it seems that we don't yet interpret the release one. It doesn't matter, though, if you set compilerCompliance explicitly in this plugin's config. I would try setting all three of ours: compilerCompliance, compilerSource, and compilerTargetPlatform. If that still doesn't work, then maybe when the new version is released, it will work.

from formatter-maven-plugin.

You can try using formatter-maven-plugin 2.23.0, which is based on the newer Eclipse, and I just released. I'll close this for now. Please comment here if it still doesn't work, so we can re-open and troubleshoot further.

from formatter-maven-plugin.