I did a successful build starting with empty local repository on Linux.
On 19.06.2014 16:49, Cristiano Costantini wrote: > Hi Gert, > >> For your Akka test problem, I think you're bumping into >> https://issues.apache.org/jira/browse/SM-2255. I have not been able >> to reproduce that locally for a while, so it would be great if you >> could attach the test output and report, as well as the log file to >> the JIRA issue. >> > yes it seems really that issue, it is 100% reproducible on the computers I > use, a Windows 7 and Mac Os X Mavericks; > I will attach the output to the issue, and I give availability to support > its resolution (if you work on it, just drop me an email and I run it again > to check if the fixes work). > > Unfortunately I don't know scala and can't dig into the problem, but tell > me if you need more info and I'll provide them. > > > > >> For the eclipse osgi jar - it looks like the same artifact is already >> available in Central repo as >> >> http://search.maven.org/#artifactdetails%7Corg.eclipse%7Corg.eclipse.osgi%7C3.8.0.v20120529-1548%7Cjar >> , >> so perhaps we should just raise a JIRA issue for Karaf to switch to >> the new artifact location? That way, whenever we switch to the next >> version of Karaf, this issue would be resolved as well. >> > it took me some time to figure out the differences: > org.eclipse:osgi:jar:3.8.0.v20120529-1548 used by Karaf > vs > org.eclipse:org.eclipse.osgi:3.8.0.v20120529-1548 available on Central Repo > > Ok, I agree did you already opened the issue on Karaf? > If you didn't, I can try opening it. > > Regards > Cristiano > > > >> Regards, >> >> Gert Vanthienen >> >> >> On Thu, Jun 19, 2014 at 9:35 AM, Cristiano Costantini >> <[email protected]> wrote: >>> Hi, >>> I don't want to make entropy on the vote, so I report here the issues I >> had >>> while trying to build SMX 5.0.2 (and the same I had with SMX 5.0.1 and >>> 5.1.0). >>> >>> Let me anticipate that these issues are dependent on my environment >> where I >>> have some limitations, mainly I use maven behind an internal Repository >>> Mirror that limits access to external repos. >>> >>> >>> >>> On my Windows and my Mac, it fails the build of the "Akka Camel" Example >>> and "Assembly". >>> >>> [INFO] Apache ServiceMix :: Examples :: Akka :: Akka Camel FAILURE >>> [18.551s] >>> [...] >>> [INFO] Apache ServiceMix :: Assembly ..................... FAILURE >>> [1:14.323s] >>> [...] >>> [INFO] Apache ServiceMix :: Integration Tests ............ SKIPPED >>> >>> >>> Assembly fails because it does not resolve >>> org.eclipse:osgi:jar:3.8.0.v20120529-1548: >>> >>> [ERROR] Failed to execute goal on project apache-servicemix: Could not >>> resolve dependencies for project >>> org.apache.servicemix:apache-servicemix:pom:5.0.2: Failure to find >>> org.eclipse:osgi:jar:3.8.0.v20120529-1548 in >>> http://192.168.3.10:9081/archiva/repository/public was cached in the >> local >>> repository, resolution will not be reattempted until the update interval >> of >>> public has elapsed or updates are forced -> [Help 1] >>> >>> as you can see I'm behind a Repository Mirror -> >>> http://192.168.3.10:9081/archiva/repository/public which has limited >> access >>> to remote repositories. >>> Can't org.eclipse:osgi:jar:3.8.0.v20120529-1548 be published to maven >>> central repo? >>> >>> >>> >>> For the example of Akka Camel, is there any prerequisite I'm ignoring? >>> The project Camel Akka Example fails due to this test: >>> ------------------------------------------------------- >>> T E S T S >>> ------------------------------------------------------- >>> Running org.apache.servicemix.examples.akka.RouteBuilderTest >>> Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 5.994 >> sec - >>> in org.apache.servicemix.examples.akka.RouteBuilderTest >>> Running org.apache.servicemix.examples.akka.StatsTest >>> Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 1.002 sec >>> <<< FAILURE! - in org.apache.servicemix.examples.akka.StatsTest >>> testCountAverageAndStddev(org.apache.servicemix.examples.akka.StatsTest) >>> Time elapsed: 1.002 sec <<< FAILURE! >>> java.lang.AssertionError: Did not receive reporting containing >>> ITEM1,2,15.0000,4.8990 >>> at org.junit.Assert.fail(Assert.java:88) >>> at >>> >> org.apache.servicemix.examples.akka.StatsTest.expectReport(StatsTest.scala:60) >>> at >>> >> org.apache.servicemix.examples.akka.StatsTest.expectReport(StatsTest.scala:61) >>> at >>> >> org.apache.servicemix.examples.akka.StatsTest.expectReport(StatsTest.scala:61) >>> at >>> >> org.apache.servicemix.examples.akka.StatsTest.expectReport(StatsTest.scala:61) >>> at >>> >> org.apache.servicemix.examples.akka.StatsTest.expectReport(StatsTest.scala:61) >>> at >>> >> org.apache.servicemix.examples.akka.StatsTest.expectReport(StatsTest.scala:61) >>> at >>> >> org.apache.servicemix.examples.akka.StatsTest.expectReport(StatsTest.scala:61) >>> at >>> >> org.apache.servicemix.examples.akka.StatsTest.expectReport(StatsTest.scala:61) >>> at >>> >> org.apache.servicemix.examples.akka.StatsTest.expectReport(StatsTest.scala:61) >>> at >>> >> org.apache.servicemix.examples.akka.StatsTest.expectReport(StatsTest.scala:61) >>> at >>> >> org.apache.servicemix.examples.akka.StatsTest.expectReport(StatsTest.scala:61) >>> at >>> >> org.apache.servicemix.examples.akka.StatsTest.expectReport(StatsTest.scala:56) >>> at >>> >> org.apache.servicemix.examples.akka.StatsTest.testCountAverageAndStddev(StatsTest.scala:50) >>> Results : >>> >>> Failed tests: >>> >>> >> StatsTest.testCountAverageAndStddev:50->expectReport:56->expectReport:61->expectReport:61->expectReport:61->expectReport:61->expectReport:61->expectReport:61->expectReport:61->ex >>> pectReport:61->expectReport:61->expectReport:61->expectReport:60 Did not >>> receive reporting containing ITEM1,2,15.0000,4.8990 >>> >>> Tests run: 2, Failures: 1, Errors: 0, Skipped: 0 >>> >>> About Akka problem, I don't know how much it is important and relevant, I >>> don't use Akka and don't know if the error is severe or not. >>> >>> About the missing dependency to build Assembly, it affects probably only >> me >>> and it is only a problem for building the sources, but I would appreciate >>> if we can do something as it will give more consistency to the source >> code. >>> Hope this helps >>> Thank you, >>> Cristiano >>> >>> >>> P.S Last time (smx 5.0.0) I had the same problem with the Assembly >> project, >>> I was able to reconfigure my environment to build skipping the internal >>> repo mirror and it did worked, however it is time consuming and I'm much >>> busy now to make the switch for testing the build... -- Krzysztof Sobkowiak JEE & OSS Architect | Technical Architect @ Capgemini Capgemini <http://www.pl.capgemini.com/> | Software Solutions Center <http://www.pl.capgemini-sdm.com/> | Wroclaw e-mail: [email protected] <mailto:[email protected]> | Twitter: @KSobkowiak Calendar: goo.gl/yvsebC
