hi
The problem has been resolved
Thanks for helping me~!!
2013/2/25 Matthieu Morel
> Indeed something is messing up the maven repo.
>
> Let me suggest the following:
> - delete the problematic dependency in your local maven repository (here
> it seems to be findbugs - just delete the directory
Indeed something is messing up the maven repo.
Let me suggest the following:
- delete the problematic dependency in your local maven repository (here it
seems to be findbugs - just delete the directory)
- in the main s4 build file, place mavenCentral() before mavenLocal()
- the FAQ has also some
Hi,
this problem has occurred when i installed s4 with storm.
i think, it seems to be maven repository conflict problem .
but i don't know, how to solve the problem
following the output : ./gradlew installS4R -b path/to/the/build/file/for/**
your/project
16:32:22.273 [DEBUG]
[org.gradle.cache.i
Hi,
you sent a Gimp file - can you send an image in a more common format? (jpeg,png
or something like that)
Also, you should follow up on your own thread, I don't think this is related to
s4r creation.
Anyway, coming back to your initial issue, you mentioned having 4 keys and 4
hosts. There i
Hi,
You can get more information by running the underlying gradle build
command directly:
"./gradlew installS4R -b path/to/the/build/file/for/your/project"
and you can add options -info or -debug to get more insight about
what may be going wrong.
With that info, you might be able to solve the is
hello ~
when i try to create s4r archive file for deploying apps, it was failed
with following output:
Selected primary task 'installS4R'
64 Tasks to be executed: [task ':compileJava', task ':processResources',
task ':classes', task ':jar', task ':buildProjectJar', task
':cleanBuildProjectJar',
