Hi Rupert, Thank you very much for your help.
I also run " mvn eclipse:eclipse" and it worked fine. I got the following: [INFO] ------------------------------------------------------------------------ [INFO] BUILD SUCCESS [INFO] ------------------------------------------------------------------------ [INFO] Total time: 9:24.378s [INFO] Finished at: Sun Feb 05 14:28:38 GMT 2012 [INFO] Final Memory: 129M/247M [INFO] ------------------------------------------------------------------------ mckm236975:stanbol ca3533$ Many Thanks, Cheers, Carlo On 5 Feb 2012, at 14:11, Rupert Westenthaler wrote: > Hi Carlo > > You can safely ignore this issue. Even if the integration-tests fail > like this the launchers are already build. You can find them in the > /launcher/[stable|full|full-war]/target directory. > > Some more information about the Error you encountered: > > This error is sometimes triggered by the lazy initialization of the > Solr server used by the Entityhub. Basically this means that your > computer needs more time to copy/iniialize the ~100MByte big index > from the launcher jar than the test environment to set up. This > typically affects the two "HttpQueryHeader" as they are executed > first. We are aware of this issue and have already discussed possible > solution in December. But this would require considerable changes to > the configuration/initialization process of the Entityhub. > > Under normal usage condition this will not affect you because > typically user Requests will not be issued to a Stanbol server during > the startup. > > > best > Rupert > > On Sun, Feb 5, 2012 at 2:18 PM, Carlo Allocca <[email protected]> wrote: >> Hi Rupert, all >> >> Thank you very much for your help. The following steps helped me: >> >> >>> Based on this observation I think the problem we need to solve is to >>> force Maven to download "org.apache:apache:9" form >>> "http://repo1.maven.org/maven2/";. >>> >>> The following things might help with that >>> >>> 1) you can try to call "mvn -U clean" and than try to "mvn install" again. >>> >>> This might help because >>> >>> -U,--update-snapshots Forces a check for updated >>> releases and snapshots on remote >>> >>> 2) you can try to manually delete the folder >>> "/Users/ca3533/.m2/repository/org/apache/apache/9/" in your local >>> cache >> >> Sorry for bothering you and all of you. I think that with your help I am >> making progress to built Stanbol. >> I have another issue. >> >> After, I did the above steps, I tried to "mvn install" again. As result, I >> got the following as Error: >> >> >> [INFO] >> ------------------------------------------------------------------------ >> [INFO] BUILD FAILURE >> [INFO] >> ------------------------------------------------------------------------ >> [INFO] Total time: 44:48.125s >> [INFO] Finished at: Sun Feb 05 12:19:51 GMT 2012 >> [INFO] Final Memory: 147M/415M >> [INFO] >> ------------------------------------------------------------------------ >> [ERROR] Failed to execute goal >> org.apache.maven.plugins:maven-surefire-plugin:2.10:test (default-test) on >> project org.apache.stanbol.integration-tests: There are test failures. >> [ERROR] >> [ERROR] Please refer to >> /Users/ca3533/Desktop/DATAMIProjectDev/stanbol/integration-tests/target/surefire-reports >> for the individual test results. >> [ERROR] -> [Help 1] >> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute >> goal org.apache.maven.plugins:maven-surefire-plugin:2.10:test (default-test) >> on project org.apache.stanbol.integration-tests: There are test failures. >> >> Please refer to >> /Users/ca3533/Desktop/DATAMIProjectDev/stanbol/integration-tests/target/surefire-reports >> for the individual test results. >> at >> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:213) >> 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:319) >> 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:39) >> at >> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) >> at java.lang.reflect.Method.invoke(Method.java:597) >> at >> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290) >> at >> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230) >> at >> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409) >> at >> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352) >> Caused by: org.apache.maven.plugin.MojoFailureException: There are test >> failures. >> >> Please refer to >> /Users/ca3533/Desktop/DATAMIProjectDev/stanbol/integration-tests/target/surefire-reports >> for the individual test results. >> at >> org.apache.maven.plugin.surefire.SurefireHelper.reportExecution(SurefireHelper.java:87) >> at >> org.apache.maven.plugin.surefire.SurefirePlugin.writeSummary(SurefirePlugin.java:641) >> at >> org.apache.maven.plugin.surefire.SurefirePlugin.handleSummary(SurefirePlugin.java:615) >> at >> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:137) >> at >> org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:98) >> at >> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101) >> at >> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209) >> ... 19 more >> [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/MojoFailureException >> [ERROR] >> [ERROR] After correcting the problems, you can resume the build with the >> command >> [ERROR] mvn <goals> -rf :org.apache.stanbol.integration-tests >> mckm236975:stanbol ca3533$ >> >> >> >> As the message suggested to refer to " >> /Users/ca3533/Desktop/DATAMIProjectDev/stanbol/integration-tests/target/surefire-reports" >> for the individual test results, I found that the following files are the >> ones which contain the exceptions: >> >> 1) org.apache.stanbol.commons.httpqueryheaders.it.HttpQueryHeaderPostTest.txt >> 2) org.apache.stanbol.commons.httpqueryheaders.it.HttpQueryHeaderGetTest.txt >> >> I attached the above files just in case they can help to clarify/figure out >> the source of the error . >> >> >> Any idea/help/? >> >> Many Thanks in advance, >> >> Best, >> Carlo >> >> >> >> On 5 Feb 2012, at 07:37, Rupert Westenthaler wrote: >> >>> Hi Carlo ,all >>> >>> >>> On Sat, Feb 4, 2012 at 10:43 PM, Carlo Allocca <[email protected]> wrote: >>>> Hi Rupert, >>>> >>>> I have just found that related to the [FATAL] >>>> >>>> [FATAL] Non-resolvable parent POM for >>>> org.apache.stanbol:stanbol-parent:0.9.0-incubating-SNAPSHOT: Could not >>>> transfer artifact org.apache:apache:pom:9 from/to apache >>>> (http://repository.apache.org/snapshots/): Error transferring file: >>>> Connection refused and 'parent.relativePath' points at no local POM @ >>>> org.apache.stanbol:stanbol-parent:0.9.0-incubating-SNAPSHOT, >>>> /Users/ca3533/Desktop/DATAMIProjectDev/stanbol/parent/pom.xml, line 15, >>>> column 11 >>>> >>>> there is something which may be not correct and it can also be the source >>>> of the error: >>>> I opened the file >>>> /Users/ca3533/Desktop/DATAMIProjectDev/stanbol/parent/pom.xml and the >>>> parent.relativePath is empty. >>>> >>>> <parent> >>>> <groupId>org.apache</groupId> >>>> <artifactId>apache</artifactId> >>>> <version>9</version> >>>> <relativePath> </relativePath> >>>> </parent> >>>> >>> >>> The empty relativePath is intended, because this POM file MUST BE >>> downloaded from a remote maven server. >>> >>> Based on the debug level log provided by your previous logs it should >>> be downloaded from >>> >>> >>>> Downloading: http://repo1.maven.org/maven2/org/apache/apache/9/apache-9.pom >>>> [DEBUG] Reading resolution tracking file >>>> /Users/ca3533/.m2/repository/org/apache/apache/9/apache-9.pom.lastUpdated >>>> [DEBUG] Writing resolution tracking file >>>> /Users/ca3533/.m2/repository/org/apache/apache/9/apache-9.pom.lastUpdated >>> >>> but this does - for some reason i do not know - not work on your machine. >>> >>> Note that the Error: >>> >>>> [FATAL] Non-resolvable parent POM for >>>> org.apache.stanbol:stanbol-parent:0.9.0-incubating-SNAPSHOT: Could not >>>> transfer artifact org.apache:apache:pom:9 from/to apache >>>> (http://repository.apache.org/snapshots/): Error transferring file: >>>> Connection refused and 'parent.relativePath' points at no local POM @ >>>> org.apache.stanbol:stanbol-parent:0.9.0-incubating-SNAPSHOT, >>>> /Users/ca3533/Desktop/DATAMIProjectDev/stanbol/parent/pom.xml, line 15, >>>> column 11 >>> >>> This basically says that the POM could not be downloaded form the >>> http://repository.apache.org/snapshots/ - what is true, because this >>> Repository does not contain org.apache:apache:9. However I think this >>> execution is only printed because this repository happens to be the >>> first in the list and the Artifact could not be found on any of the >>> listed Repositories. This is also supported by the DEBUG level >>> loggings that clearly show that all repositories are queried for the >>> the mentioned artifact. >>> >>> Based on this observation I think the problem we need to solve is to >>> force Maven to download "org.apache:apache:9" form >>> "http://repo1.maven.org/maven2/";. >>> >>> The following things might help with that >>> >>> 1) you can try to call "mvn -U clean" and than try to "mvn install" again. >>> >>> This might help because >>> >>> -U,--update-snapshots Forces a check for updated >>> releases and snapshots on remote >>> >>> 2) you can try to manually delete the folder >>> "/Users/ca3533/.m2/repository/org/apache/apache/9/" in your local >>> cache >>> >>> the .m2 folder contains you local cache. If you delete this cache (or >>> part of it) maven will download all missing artifacts on the next run. >>> This can solve problems like that in case the cache somehow contain >>> corrupted data. >>> >>> I hope this helps >>> best >>> Rupert >>> >>> >>> >>> -- >>> | Rupert Westenthaler [email protected] >>> | Bodenlehenstraße 11 ++43-699-11108907 >>> | A-5500 Bischofshofen >> >> >> -- >> The Open University is incorporated by Royal Charter (RC 000391), an exempt >> charity in England & Wales and a charity registered in Scotland (SC 038302). >> > > > > -- > | Rupert Westenthaler [email protected] > | Bodenlehenstraße 11 ++43-699-11108907 > | A-5500 Bischofshofen
