Plugins "not detected"

Hi, and thank you for a great library 👍

I’m using most of you plugins in a PR I’m working on for our application (Universal Media Server) and it’s working great for me. However, there is one of our team members that has a strange issue. It simply looks like the TwelveMonkeys plugins isn’t there on his computer. We’ve obviously verified that they are, we’re using Maven and he can build the application without error. I’ve studied our log file and I can find no Exception being thrown or nothing else that can give me a clue as to what is going wrong.

What happens is that we can see that the “Sun” plugins are chosen instead where they exist, and for formats where no other plugin is available ImageIO simply fails to read the file. It doesn’t look like there’s a priority problem in other words, it seems like they simply never register.

It’s not uncommon that things that normally work fail to work on his computer, he has a somewhat antiquated computer running WinXP 32bit. His CPU is a Athlon 1700+ that doesn’t have MMX support. Both the 32 bit OS and the lack of SSE2 support have shown itself to cause problems some times, but generally our application works on his computer as well. He is running Java 7.

Is there anyway I can troubleshoot/debug the (plugin) registration process to get some more information about what is actually going on?

[Nadahar]

Ah, ok - was it SSE2 that was missing then?

[Nadahar]

In case it’s useful to someone else: I solved it using maven-assembly-plugin by putting the manually merged files in a folder outside the “normal Maven structure”. I used /src/main/external-resources/META-INF/services/ since we already have other things that doesn’t fit anywhere there.

In addition I edited the assembly file like this:

<assembly
	xmlns="http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.2"
	xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
	xsi:schemaLocation="http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.2 http://maven.apache.org/xsd/assembly-1.1.2.xsd">
	
	<id>jar-with-dependencies</id>
	<formats>
		<format>jar</format>
	</formats>
	<includeBaseDirectory>false</includeBaseDirectory>

	<dependencySets>
		<dependencySet>
			<outputDirectory>/</outputDirectory>
			<useProjectArtifact>true</useProjectArtifact>
			<unpack>true</unpack>
            <unpackOptions>
				<excludes>
					<exclude>META-INF/services/javax.imageio.spi.ImageReaderSpi</exclude>
					<exclude>META-INF/services/javax.imageio.spi.ImageWriterSpi</exclude>
				</excludes>
			</unpackOptions>
			<scope>runtime</scope>
		</dependencySet>
	</dependencySets>
	<files>
		<file>
			<source>${project.basedir}/src/main/external-resources/META-INF/services/javax.imageio.spi.ImageReaderSpi</source>
			<outputDirectory>META-INF/services</outputDirectory>
		</file>
		<file>
			<source>${project.basedir}/src/main/external-resources/META-INF/services/javax.imageio.spi.ImageWriterSpi</source>
			<outputDirectory>META-INF/services</outputDirectory>
		</file>
	</files>
</assembly>

@haraldk Thank you for your suggestions, I knew about maven-shade-plugin (I actually have a 1,5 year old PR about switching to that) but converting our POM with loads of undocumented “special cases” and custom handling isn’t that easy. To make it worse, the project is originally converted from ant and most of our POM is written by people that’s no longer involved. It’s doable, by all means, but I simply wanted to fix this without taking on that can of worms. Converting to the onejar plugins probably has more or less the same challenges in additon to that it looks abandoned.

Thank you again for all help, it seems like it’s working just fine now 😉