没有在twitter4j上使用mvn包

时间:2013-05-28 21:58:22

标签: maven heroku package twitter4j

我正在尝试将twitter4j项目部署到heroku。

当我运行以下命令时:

$ mvn package

这就是我得到的:

-------------------------------------------------------
 T E S T S
-------------------------------------------------------
Running twitter4j.auth.OAuthTest
Tests run: 15, Failures: 0, Errors: 15, Skipped: 0, Time elapsed: 0.072 sec <<< FAILURE!
Running twitter4j.AuthorizationTest
Tests run: 3, Failures: 0, Errors: 3, Skipped: 0, Time elapsed: 0.005 sec <<< FAILURE!
Running twitter4j.conf.ConfigurationTest
Tests run: 9, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.092 sec
Running twitter4j.DirectMessagesResourcesTest
Tests run: 2, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 0.003 sec <<< FAILURE!
Running twitter4j.FavoritesResourcesTest
Tests run: 2, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 0.004 sec <<< FAILURE!
Running twitter4j.FriendsFollowersResourcesTest
Tests run: 6, Failures: 0, Errors: 6, Skipped: 0, Time elapsed: 0.01 sec <<< FAILURE!
Running twitter4j.HelpResoursesTest
Tests run: 3, Failures: 0, Errors: 3, Skipped: 0, Time elapsed: 0.004 sec <<< FAILURE!
Running twitter4j.http.BASE64EncoderTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.002 sec
Running twitter4j.http.HttpClientTest
Tests run: 2, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 0.005 sec <<< FAILURE!
Running twitter4j.http.PostParameterTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.003 sec
Running twitter4j.internal.async.DispatcherTest

.
.
.

Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.334 sec
Running twitter4j.internal.json.HTMLEntityTest
Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.023 sec
Running twitter4j.internal.json.RateLimitStatusJSONImplTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.004 sec
Running twitter4j.internal.json.UserJSONImplTest
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.107 sec
Running twitter4j.internal.KryoSerializationTest
403 vs. 1522
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.042 sec
Running twitter4j.internal.util.ParseUtilTest
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.002 sec
Running twitter4j.internal.util.StringUtilTest
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.001 sec
Running twitter4j.ListResourcesTest
Tests run: 7, Failures: 0, Errors: 7, Skipped: 0, Time elapsed: 0.011 sec <<< FAILURE!
Running twitter4j.management.MBeansTest
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.014 sec
Running twitter4j.MBeansIntegrationTest
Tests run: 2, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 0.004 sec <<< FAILURE!
Running twitter4j.PagingTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.002 sec
Running twitter4j.PlaceGeoResourcesTest
Tests run: 3, Failures: 0, Errors: 3, Skipped: 0, Time elapsed: 0.005 sec <<< FAILURE!
Running twitter4j.SavedSearchesResourcesTest
Tests run: 2, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 0.004 sec <<< FAILURE!
Running twitter4j.SearchAPITest
Tests run: 4, Failures: 0, Errors: 4, Skipped: 0, Time elapsed: 0.005 sec <<< FAILURE!
Running twitter4j.SpamReportingResourceTest
Tests run: 2, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 0.003 sec <<< FAILURE!
Running twitter4j.SuggestedUsersResourcesTest
Tests run: 2, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 0.003 sec <<< FAILURE!
Running twitter4j.TimelineResourcesTest
Tests run: 5, Failures: 0, Errors: 5, Skipped: 0, Time elapsed: 0.007 sec <<< FAILURE!
Running twitter4j.TrendsResourcesTest
Tests run: 2, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 0.002 sec <<< FAILURE!
Running twitter4j.TweetsResourcesTest
Tests run: 6, Failures: 0, Errors: 6, Skipped: 0, Time elapsed: 0.006 sec <<< FAILURE!
Running twitter4j.TwitterExceptionTest
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.003 sec
Running twitter4j.TwitterTest
Tests run: 4, Failures: 0, Errors: 4, Skipped: 0, Time elapsed: 0.007 sec <<< FAILURE!
Running twitter4j.UndocumentedResourcesTest
Tests run: 2, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 0.003 sec <<< FAILURE!
Running twitter4j.UsersResourcesTest
Tests run: 9, Failures: 0, Errors: 9, Skipped: 0, Time elapsed: 0.01 sec <<< FAILURE!
Running twitter4j.util.CharacterUtilTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.002 sec
Running twitter4j.util.TimeSpanConverterTest
Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.024 sec

我做错了什么?

希望这是有用的信息..

2 个答案:

答案 0 :(得分:0)

通常在target / surefire-report下提供错误详细信息。从那里你可以尝试猜测错误的来源,并咨询twitter4j社区可能

如果你想削减角落(可能不是最明智的事情)。您可以通过添加跳过测试标志来跳过单元测试

mvn package -DskipTests

答案 1 :(得分:0)

如果您正在尝试部署基于twitter4j的应用程序 - 您希望确保首先通过单元测试。您需要修复测试才能继续。这是一个常规的开发周期。

如果您仍希望打包工件而忽略任何测试失败 - 您可以将以下属性添加到命令行:

-Dmaven.test.failure.ignore=true

请参阅此处的maven surefire插件文档:http://maven.apache.org/surefire/maven-surefire-plugin/test-mojo.html