Yes, I’ve seen that. It has something to do with clojure tests and the maven 
lifecycle.

I typically just do `mvn clean install` to run the tests.

-Taylor

> On Oct 29, 2015, at 9:38 AM, Julien Nioche <[email protected]> 
> wrote:
> 
> Correction. 'mvn clean compile' worked but 'mvn clean test' actually fails
> on my machine (running linux mint)
> 
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Reactor Summary:
> [INFO]
> [INFO] Storm ............................................. SUCCESS [1.250s]
> [INFO] maven-shade-clojure-transformer ................... SUCCESS [2.564s]
> [INFO] Storm Core ........................................ FAILURE
> [4:36.961s]
> [INFO] storm-starter ..................................... SKIPPED
> [INFO] storm-kafka ....................................... SKIPPED
> [INFO] storm-hdfs ........................................ SKIPPED
> [INFO] storm-hbase ....................................... SKIPPED
> 
> 
> [ERROR] Failed to execute goal
> com.theoryinpractise:clojure-maven-plugin:1.3.18:test-with-junit
> (test-clojure) on project storm-core: Clojure failed. -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal com.theoryinpractise:clojure-maven-plugin:1.3.18:test-with-junit
> (test-clojure) on project storm-core: Clojure failed.
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:217)
> 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:84)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> 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)
> 
> 
> Clojure 1.4.0 is installed.
> 
> Can't see anything relevant in surefire-reports. Probably something
> misconfigured on my machine, has anyone seen this before?
> 
> Julien
> 
> 
> 
> On 29 October 2015 at 11:45, Julien Nioche <[email protected]>
> wrote:
> 
>> +1
>> 
>>   - 'mvn clean test' successfully on the source
>>   - storm-crawler compiled and worked fine using the artefacts in Nexus
>>   - installed the binary release on single node and ran a storm-crawler
>>   topology successfully
>> 
>> Thanks
>> 
>> Julien
>> 
>> On 28 October 2015 at 21:18, P. Taylor Goetz <[email protected]> wrote:
>> 
>>> This is a call to vote on releasing Apache Storm 0.9.6 (rc2).
>>> 
>>> Full list of changes in this release:
>>> 
>>> 
>>> https://git-wip-us.apache.org/repos/asf?p=storm.git;a=blob_plain;f=CHANGELOG.md;hb=90a97ad6101de3c01233384e3dd3eeff2dde2ba3
>>> 
>>> The tag/commit to be voted upon is v0.9.6:
>>> 
>>> 
>>> https://git-wip-us.apache.org/repos/asf?p=storm.git;a=tree;h=6f79e18f45d18350d377d98d085a17d2893c36e6;hb=90a97ad6101de3c01233384e3dd3eeff2dde2ba3
>>> 
>>> The source archive being voted upon can be found here:
>>> 
>>> 
>>> https://dist.apache.org/repos/dist/dev/storm/apache-storm-0.9.6-rc2//apache-storm-0.9.6-src.tar.gz
>>> 
>>> Other release files, signatures and digests can be found here:
>>> 
>>> https://dist.apache.org/repos/dist/dev/storm/apache-storm-0.9.6-rc2/
>>> 
>>> The release artifacts are signed with the following key:
>>> 
>>> 
>>> https://git-wip-us.apache.org/repos/asf?p=storm.git;a=blob_plain;f=KEYS;hb=22b832708295fa2c15c4f3c70ac0d2bc6fded4bd
>>> 
>>> The Nexus staging repository for this release is:
>>> 
>>> https://repository.apache.org/content/repositories/orgapachestorm-1026
>>> 
>>> Please vote on releasing this package as Apache Storm 0.9.6.
>>> 
>>> When voting, please list the actions taken to verify the release.
>>> 
>>> This vote will be open for at least 72 hours.
>>> 
>>> [ ] +1 Release this package as Apache Storm 0.9.6
>>> [ ]  0 No opinion
>>> [ ] -1 Do not release this package because...
>>> 
>>> Thanks to everyone who contributed to this release.
>>> 
>>> -Taylor
>>> 
>> 
>> 
>> 
>> --
>> 
>> *Open Source Solutions for Text Engineering*
>> 
>> http://www.digitalpebble.com
>> http://digitalpebble.blogspot.com/
>> #digitalpebble <http://twitter.com/digitalpebble>
>> 
> 
> 
> 
> --
> 
> *Open Source Solutions for Text Engineering*
> 
> http://www.digitalpebble.com
> http://digitalpebble.blogspot.com/
> #digitalpebble <http://twitter.com/digitalpebble>

Attachment: signature.asc
Description: Message signed with OpenPGP using GPGMail

Reply via email to