Skip to content
This repository has been archived by the owner on Jul 23, 2020. It is now read-only.

'GreetingServiceTest' from wildfly booster is failing in Che #2152

Open
ibuziuk opened this issue Feb 1, 2018 · 27 comments
Open

'GreetingServiceTest' from wildfly booster is failing in Che #2152

ibuziuk opened this issue Feb 1, 2018 · 27 comments

Comments

@ibuziuk
Copy link
Collaborator

ibuziuk commented Feb 1, 2018

Steps to reproduce:

  • start workspace with wildfly booster quickstart
  • execute build command
[INFO] Running io.openshift.booster.GreetingServiceTest
[ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 1.184 s <<< FAILURE! - in io.openshift.booster.GreetingServiceTest
[ERROR] io.openshift.booster.GreetingServiceTest  Time elapsed: 1.183 s  <<< ERROR!
org.jboss.arquillian.container.spi.client.container.DeploymentException: WFSWARM0012: Cannot identify FileSystemLayout for given path: /projects/xzxz
Caused by: java.lang.IllegalArgumentException: WFSWARM0012: Cannot identify FileSystemLayout for given path: /projects/xzxz
@lordofthejars
Copy link
Collaborator

I found this issue running on openshift.io. If I run mvn clean install locally it runs correctly this test that is failing on Che.

@ghost
Copy link

ghost commented Feb 2, 2018

Resolving 0 out of 596 artifacts
Fri Feb 02 08:24:20 UTC 2018 INFO [org.wildfly.swarm.bootstrap] (main) Dependencies not bundled; resolving from M2REPO.
[ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 10.037 s <<< FAILURE! - in io.openshift.booster.GreetingServiceTest
[ERROR] io.openshift.booster.GreetingServiceTest  Time elapsed: 10.036 s  <<< ERROR!
org.jboss.arquillian.container.spi.client.container.DeploymentException: Process failed to start
Caused by: org.jboss.arquillian.container.spi.client.container.DeploymentException: Process failed to start

I get a different error when running mvn clean install from the terminal or as a command. The default command is scl enable rh-maven33 'mvn clean install -f ${current.project.path}'

@bartoszmajsak
Copy link
Contributor

@eivantsov is that the whole log you are getting? That's a bit blurry to reason what is really going on.

@ghost
Copy link

ghost commented Feb 2, 2018

scl enable rh-maven33 'cd ${current.project.path} && mvn clean install' if you try this command you will get past the error but hit another one.

As you can see, maven is invoked in root dir rather than path to pom.xml is passed as an arg

By the way, I have run mvn clean install locally, and tests get stuck ...

[INFO] Running io.openshift.booster.GreetingServiceTest
Resolving 263 out of 596 artifacts

But ended well in the end.

Same result when building locally in a Docker container. I suspect that the error has smth to do with permissions that an arbitrary user has in an OSO pod.

@bartoszmajsak
Copy link
Contributor

Provided more details in #2262 to only realize that it's a duplicate of this issue, so pasting it here to avoid looping through tabs:

Steps to reproduce

  1. Run GreetingServiceTest (either from the IDE or from Maven mvn test -Dtest=GreetingServiceTest)
Prerequisites if starting from scratch:
  1. Select WildFly Swarm Http Booster as a quickstart to import
  2. Optionally in Che: Comment out Cube dependency in the pom.xml
  3. Optionally in Che: Delete OpenshiftIT test (there is another potential issue with Cube on OSIO/Che we are investigating)

(alternatively, clone this repository https://github.com/lordofthejars/swarmq where all the steps are already applied)

Detailed stack traces

Error while running Che (after clean build of the project)
org.jboss.arquillian.container.spi.client.container.DeploymentException: Process failed to start
	at org.wildfly.swarm.arquillian.adapter.WildFlySwarmContainer.deploy(WildFlySwarmContainer.java:92)
	at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$3.call(ContainerDeployController.java:161)
	at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$3.call(ContainerDeployController.java:128)
	at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.executeOperation(ContainerDeployController.java:271)
	at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.deploy(ContainerDeployController.java:127)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:96)
	at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99)
	at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81)
	at org.jboss.arquillian.container.impl.client.ContainerDeploymentContextHandler.createDeploymentContext(ContainerDeploymentContextHandler.java:78)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:96)
	at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
	at org.jboss.arquillian.container.impl.client.ContainerDeploymentContextHandler.createContainerContext(ContainerDeploymentContextHandler.java:57)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:96)
	at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
	at org.jboss.arquillian.container.impl.client.container.DeploymentExceptionHandler.verifyExpectedExceptionDuringDeploy(DeploymentExceptionHandler.java:50)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:96)
	at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
	at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:145)
	at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116)
	at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67)
	at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$1.perform(ContainerDeployController.java:95)
	at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$1.perform(ContainerDeployController.java:80)
	at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.forEachDeployment(ContainerDeployController.java:263)
	at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.forEachManagedDeployment(ContainerDeployController.java:239)
	at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.deployManaged(ContainerDeployController.java:79)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:96)
	at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99)
	at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81)
	at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:145)
	at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116)
	at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67)
	at org.jboss.arquillian.container.test.impl.client.ContainerEventController.execute(ContainerEventController.java:101)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:96)
	at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99)
	at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81)
	at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:92)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:96)
	at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
	at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:73)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:96)
	at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
	at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:145)
	at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:116)
	at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.beforeClass(EventTestRunnerAdaptor.java:87)
	at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:202)
	at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:431)
	at org.jboss.arquillian.junit.Arquillian.access$200(Arquillian.java:55)
	at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:219)
	at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
	at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:167)
	at org.eclipse.che.junit.junit4.JUnit4TestReference.run(JUnit4TestReference.java:50)
	at org.eclipse.che.junit.junit4.CheJUnitCoreRunner.run(CheJUnitCoreRunner.java:56)
	at org.eclipse.che.junit.junit4.CheJUnitLauncher.main(CheJUnitLauncher.java:29)
Caused by: org.jboss.arquillian.container.spi.client.container.DeploymentException: Process failed to start
	at org.wildfly.swarm.arquillian.adapter.UberjarSimpleContainer.start(UberjarSimpleContainer.java:306)
	at org.wildfly.swarm.arquillian.adapter.WildFlySwarmContainer.deploy(WildFlySwarmContainer.java:79)
	... 84 more
Error while running from Maven (mvn test -Dtest=GreetingServiceTest)
[INFO] -------------------------------------------------------
[INFO]  T E S T S
[INFO] -------------------------------------------------------
[INFO] Running io.openshift.booster.GreetingServiceTest
Resolving 0 out of 563 artifacts
Wed Feb 14 10:45:11 UTC 2018 INFO [org.wildfly.swarm.bootstrap] (main) Dependencies not bundled; resolving from M2REPO.
[ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 10.323 s <<< FAILURE! - in io.openshift.booster.GreetingServiceTest
[ERROR] io.openshift.booster.GreetingServiceTest  Time elapsed: 10.322 s  <<< ERROR!
org.jboss.arquillian.container.spi.client.container.DeploymentException: Process failed to start
Caused by: org.jboss.arquillian.container.spi.client.container.DeploymentException: Process failed to start

@ghost
Copy link

ghost commented Apr 25, 2018

@ibuziuk I have run tests on Docker and OpenShift, without Che at all. Tests fail with exact same error.

Tests were held on a local Docker and Origin, as well as on OSO Pro. I can share OpenShift deployment yaml so that you can quickly test it locally as well.

It is interesting that commands:

mvn clean install in the project root
and
mvn clean install -f /path/to/project

cause different behavior. The former just makes tests hang with a message:

[INFO]  T E S T S
[INFO] -------------------------------------------------------
[INFO] Running io.openshift.booster.GreetingServiceTest
Resolving 271 out of 596 artifacts

We should probably get some input from arquillian team?

Update. On ORO Pro, the process is killed even though I have enough RAM to run such a test.

@l0rd
Copy link
Collaborator

l0rd commented Apr 25, 2018

@eivantsov That makes sense with what I have observed. It doesn't look like OpenShift kills the process because it's using too much memory (there would be an evidence in the openshfit events). What we should look at are the JAVA_OPTS memory settings more than the infrastructure configuration.

@l0rd
Copy link
Collaborator

l0rd commented Apr 25, 2018

We never really finished to tune JAVA_OPTS for workspaces redhat-developer/rh-che#451 and the time may have come to work on that.

@ibuziuk
Copy link
Collaborator Author

ibuziuk commented May 4, 2018

@slemeur this is the last P0 that is not addressed from che side. Are we ok to add flag for skipping tests in wildfly commands as a temp workaround ? I'm afraid we will not be able to provide better fix before summit

@slemeur
Copy link
Collaborator

slemeur commented May 4, 2018

Fine for me as a temporary solution.

@ghost
Copy link

ghost commented May 4, 2018

I never worked for me in Docker. We should probably ask for help from WildFly or Arquillian devs

@ibuziuk
Copy link
Collaborator Author

ibuziuk commented May 4, 2018

@maxandersen do you happen to know who is the wildfly quickstart mainatainer ?

@ibuziuk
Copy link
Collaborator Author

ibuziuk commented May 4, 2018

hmmm.. adding skipTests to the command results in OOME (works fine when executing from terminal):

INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 10.530 s
[INFO] Finished at: 2018-05-04T13:16:25+00:00
[INFO] Final Memory: 57M/64M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-war-plugin:3.1.0:war (default-war) on project app-test-1: Error assembling WAR: Problem creating war: Execution exception: Java heap space -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-war-plugin:3.1.0:war (default-war) on project app-test-1: Error assembling WAR: Problem creating war: Execution exception
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
Caused by: org.apache.maven.plugin.MojoExecutionException: Error assembling WAR: Problem creating war: Execution exception
at org.apache.maven.plugins.war.WarMojo.execute(WarMojo.java:213)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207)
... 20 more
Caused by: org.codehaus.plexus.archiver.ArchiverException: Problem creating war: Execution exception
at org.codehaus.plexus.archiver.AbstractArchiver.createArchive(AbstractArchiver.java:1010)
at org.apache.maven.archiver.MavenArchiver.createArchive(MavenArchiver.java:649)
at org.apache.maven.plugins.war.WarMojo.performPackaging(WarMojo.java:268)
at org.apache.maven.plugins.war.WarMojo.execute(WarMojo.java:197)
... 22 more
Caused by: java.io.IOException: Execution exception
at org.codehaus.plexus.archiver.zip.AbstractZipArchiver.close(AbstractZipArchiver.java:892)
at org.codehaus.plexus.archiver.AbstractArchiver.createArchive(AbstractArchiver.java:997)
... 25 more
Caused by: java.lang.OutOfMemoryError: Java heap space
at org.codehaus.plexus.archiver.zip.ByteArrayOutputStream.needNewBuffer(ByteArrayOutputStream.java:153)
at org.codehaus.plexus.archiver.zip.ByteArrayOutputStream.write(ByteArrayOutputStream.java:192)
at org.apache.commons.io.output.ThresholdingOutputStream.write(ThresholdingOutputStream.java:129)
at org.codehaus.plexus.archiver.zip.DeferredScatterOutputStream.writeOut(DeferredScatterOutputStream.java:44)
at org.apache.commons.compress.archivers.zip.StreamCompressor$ScatterGatherBackingStoreCompressor.writeOut(StreamCompressor.java:274)
at org.apache.commons.compress.archivers.zip.StreamCompressor.writeCounted(StreamCompressor.java:257)
at org.apache.commons.compress.archivers.zip.StreamCompressor.deflate(StreamCompressor.java:248)
at org.apache.commons.compress.archivers.zip.StreamCompressor.deflateUntilInputIsNeeded(StreamCompressor.java:241)
at org.apache.commons.compress.archivers.zip.StreamCompressor.writeDeflated(StreamCompressor.java:222)
at org.apache.commons.compress.archivers.zip.StreamCompressor.write(StreamCompressor.java:190)
at org.apache.commons.compress.archivers.zip.StreamCompressor.deflate(StreamCompressor.java:169)
at org.apache.commons.compress.archivers.zip.ScatterZipOutputStream.addArchiveEntry(ScatterZipOutputStream.java:97)
at org.apache.commons.compress.archivers.zip.ParallelScatterZipCreator$2.call(ParallelScatterZipCreator.java:175)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
[ERROR]
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException

@slemeur
Copy link
Collaborator

slemeur commented May 4, 2018

We figured out that even by skipping the test from the che command, we are not able to build the application.

See: #3463

@ibuziuk
Copy link
Collaborator Author

ibuziuk commented May 4, 2018

PR with updating wildfly recipe is send https://github.com/redhat-developer/che-dockerfiles/pull/35 let's see if it improve the situation

@slemeur
Copy link
Collaborator

slemeur commented May 4, 2018

Where is the PR ?

@ghost
Copy link

ghost commented May 4, 2018

https://github.com/redhat-developer/che-dockerfiles/pull/35? However, I don't see how it can help with oom when running maven build via exec...

@ibuziuk
Copy link
Collaborator Author

ibuziuk commented May 4, 2018

updated the comment

@ibuziuk
Copy link
Collaborator Author

ibuziuk commented May 4, 2018

Unfortumately, nothing changed after stack rebuilding :-(

@slemeur
Copy link
Collaborator

slemeur commented May 5, 2018

We would have a workaround provided in #3463 (comment)

@ibuziuk
Copy link
Collaborator Author

ibuziuk commented May 6, 2018

Workaround with disabling tests is already available on prod-preview - #3463 (comment)

@ibuziuk
Copy link
Collaborator Author

ibuziuk commented May 24, 2018

Adding area/launcher/runtime/wildfly label. Created a wildfly issue for failing tests when building using -f option https://issues.jboss.org/browse/WFARQ-45 cc: @gastaldi @kenfinnigan

@kenfinnigan
Copy link

Moved the issue to https://issues.jboss.org/browse/THORN-2049 as it's not to do with WildFly or Arquillian, it's to do with WildFly Swarm (now Thorntail)

@bartoszmajsak
Copy link
Contributor

@ibuziuk I provided PR for the -f issue. Not really sure which issues from this huge snowball it will fix, so can we sync on how to verify that in Che?

@dkranz
Copy link

dkranz commented Aug 7, 2018

Is there any way to work around this and continue with the Getting Started?

@ibuziuk
Copy link
Collaborator Author

ibuziuk commented Sep 19, 2018

@bartoszmajsak sorry for the late response. Basically, -f should fix the first part of the problem since thornail does not handles -f option. However, I see that PR is still not merged upstream so we still can not run the sample via che build command
@dkranz current workaround is executing the tests via run command which disables tests during the build or skipping tests via -DskipTests=true in terminal

@fabineri
Copy link

fabineri commented Nov 6, 2018

A solved passing system property and force a layout

System.setProperty("thorntail.filesystem.layout.class", "org.wildfly.swarm.internal.MavenFileSystemLayout");

A see the class FileSystemLayout.CUSTOM_LAYOUT_CLASS implementation. sorry my english

@ibuziuk ibuziuk removed their assignment Feb 6, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests