thegreystone / problematic-microservices Goto Github PK

Non Eclipse users like me need a Maven solution because at least on Windows the Maven starter scripts don't work due to too long CLASSPATH lines as already written in the README.

One solution would probably to use the appassembler-maven-plugin Booter mechanism - but it's hard to setup if you are not used to it.

An easier workaround, which however needs a slight manual change in the generated bat files would be

• add the repositoryLayout flat option to the configuration of the appassembler-maven-plugin

				<configuration>
					<extraJvmArguments>-Xms128m</extraJvmArguments>
					<assembleDirectory>target</assembleDirectory>
					<repositoryLayout>flat</repositoryLayout> <!-- NEW!!! -->
					<programs>
						<program>
							<mainClass>se.hirt.examples.robotshop.customerservice.Main</mainClass>
							<id>customerService</id>
						</program>
					</programs>
				</configuration>

This reduces the CLASSPATH length because you get rid of the package directories, but even this generated CLASSPATH becomes too long.
But now that all JARs reside flat in the repo directory, you can make use of the classpath option to add all JARs in a directory.

• change the "set CLASSPATH" command in the Maven generated bat files to
  set CLASSPATH="%BASEDIR%"\etc;"%REPO%"\*

A somehow ugly procedure but because you will normally do Maven build only once, it's a true workaround. Maybe you can add a comment like this to your README. I will come up with a little Pull Request.

I met the trouble below after run mvn package the project and ./target/bin/xxxService.
Did I miss something?

Failed to scan [file:/xxx/problematic-microservices/robotshop-order-service/target/repo/org/glassfish/jaxb/jaxb-jxc/2.4.0-b180725.0644/txw2-2.4.0-b180725.0644.jar] from classloader hierarchy