1 2 3 4 Previous Next 47 Replies Latest reply on Oct 22, 2012 7:39 PM by Guillaume B

    weld-osgi Status?

    Harald Wellmann Novice

      What's the current status of the weld-osgi extension by Mathieu Ancelin et al.?

       

      I remember reading an announcement a few months ago it would soon be merged into an official Weld release, but I don't think that has happened yet, or has it?

       

      If not, which is the most up-to-date GitHub clone or branch of weld-osgi?

       

      Best regards,

      Harald

        • 1. Re: weld-osgi Status?
          Ales Justin Master

          Hey,

          What's the current status of the weld-osgi extension by Mathieu Ancelin et al.?

          I remember reading an announcement a few months ago it would soon be merged into an official Weld release, but I don't think that has happened yet, or has it?

          yes, not yet.

          It's my fault :-(, I need to find some proper time to do this.

          Just been too busy with other stuff + PTO.

           

          I'm back next week, and I'll try to do it then asap.

           

          If not, which is the most up-to-date GitHub clone or branch of weld-osgi?

           

          https://github.com/alesj/core/tree/osgi

           

          But this also requires new Weld API.

           

          https://github.com/alesj/api/tree/osgi

          • 2. Re: weld-osgi Status?
            Harald Wellmann Novice

            Thanks, Ales, I'll take a look...!

            • 3. Re: weld-osgi Status?
              anil halil Novice

              In the mean time i try build project by reading http://mathieuancelin.github.com/Dev/2012/05/01/how-to-build-weld-osgi/ post. But it failed. Is there any snapshot built of the branch? Like maven repo or something?Because i really give it a try

               

              Thank you in advance...

              • 4. Re: weld-osgi Status?
                Tang Yong Newbie

                Hi anil,

                 

                I want to know why you build failed,because I have not met any problem when building.

                http://mathieuancelin.github.com/Dev/2012/05/01/how-to-build-weld-osgi/

                • 5. Re: weld-osgi Status?
                  anil halil Novice

                  Hello tang sory for late reply,

                   

                  "api" built with success but building "core" with jdk 7 gives

                  [ERROR] COMPILATION ERROR :

                  [INFO] -------------------------------------------------------------

                  [ERROR] /home/capacman/programlama/java/builds/core/impl/src/main/java/org/jboss/weld/introspector/jlr/WeldAnnotationImpl.java:[54,59] error: name clash: <A>of(String,Class<A>,ClassTransformer) in WeldAnnotationImpl and <T>of(String,Class<T>,ClassTransformer) in WeldClassImpl have the same erasure, yet neither hides the other

                   

                  Then i tried with jdk 6 and this time "core" failed at tests

                  [INFO] Weld OSGi (Tester) ................................ FAILURE [28.133s]

                   

                  I can send surefire reports as well.

                  • 6. Re: weld-osgi Status?
                    Tang Yong Newbie

                    Hi Anil,

                     

                    Firstly I have not met the above errors on windows platform using jdk 6_31.

                     

                    Then , you may try "mvn -DskipTests=true clean install" to skip tests and see whether still having problems.

                     

                    However, I have not used jdk7.

                     

                    --Best Regard!

                    --Tang

                    • 7. Re: weld-osgi Status?
                      Ales Justin Master

                      I actually made some progress this week:

                       

                      (1) https://github.com/alesj/api/tree/osgi2

                       

                      (2) https://github.com/alesj/core/tree/osgi2

                       

                      (3) https://github.com/alesj/jboss-as/tree/osgi2

                       

                      This is the latest Weld-OSGi code.

                       

                      I still get some incontainer errors, but the rest should bi fine.

                      • 8. Re: weld-osgi Status?
                        Tang Yong Newbie

                        Ales Justin による書き込み:

                         

                        I actually made some progress this week:

                         

                        (1) https://github.com/alesj/api/tree/osgi2

                         

                        (2) https://github.com/alesj/core/tree/osgi2

                         

                        (3) https://github.com/alesj/jboss-as/tree/osgi2

                         

                        This is the latest Weld-OSGi code.

                         

                        I still get some incontainer errors, but the rest should bi fine.

                         

                        Hi Ales,

                         

                        Just Now, I cloned api and core projects, then built the two projects. While building core/osgi2 ("mvn clean install"), the following exception happened.

                         

                        ERROR: Bundle org.jboss.weld.osgi.weld-osgi-core-extension [16] Error starting mvn:org.jboss.weld.osgi/weld-osgi-core-extension/1.2.0-SNAPSHOT (org.osgi.framework.BundleException: Uses constraint violation. Unable to resolve bundle revision org.jboss.weld.osgi.weld-osgi-core-extension [16.0] because it is exposed to package 'javax.inject' from bundle revisions org.jboss.weld.osgi.weld-osgi-core-mandatory [13.0] and org.apache.geronimo.specs.

                         

                        Chain 1:

                        org.osgi.framework.BundleException: Uses constraint violation. Unable to resolve bundle revision org.jboss.weld.osgi.weld-osgi-core-extension [16.0] because it is exposed to package 'javax.inject' from bundle revisions org.jboss.weld.osgi.weld-osgi-core-mandatory [13.0] and org.apache.geronimo.specs.geronimo-atinject_1.0_spec [12.0] via two dependency chains.

                         

                        Chain 1:

                          org.jboss.weld.osgi.weld-osgi-core-extension [16.0]

                            import: (&(osgi.wiring.package=javax.inject)(version>=1.0.0))

                          org.jboss.weld.osgi.weld-osgi-core-extension [16.0]

                             |

                            export: osgi.wiring.package=javax.inject

                          org.jboss.weld.osgi.weld-osgi-core-mandatory [13.0]

                            import: (&(osgi.wiring.package=javax.inject)(version>=1.0.0))

                             |

                            export: osgi.wiring.package=javax.inject

                         

                        Chain 2:

                          org.jboss.weld.osgi.weld-osgi-core-mandatory [13.0]

                          org.jboss.weld.osgi.weld-osgi-core-extension [16.0]

                            import: (&(osgi.wiring.package=org.jboss.weld.environment.osgi.api.annotation)(version>=1.2.0.SNAPSHOT))

                             |

                            export: osgi.wiring.package=org.jboss.weld.environment.osgi.api.annotation; uses:=javax.inject

                          org.jboss.weld.osgi.weld-osgi-core-api [14.0]

                         

                            import: (osgi.wiring.package=javax.inject)

                             |

                        Chain 2:

                            export: osgi.wiring.package=javax.inject

                          org.jboss.weld.osgi.weld-osgi-core-extension [16.0]

                            import: (&(osgi.wiring.package=org.jboss.weld.environment.osgi.api.annotation)(version>=1.2.0.SNAPSHOT))

                             |

                            export: osgi.wiring.package=org.jboss.weld.environment.osgi.api.annotation; uses:=javax.inject

                          org.apache.geronimo.specs.geronimo-atinject_1.0_spec [12.0]

                                at org.apache.felix.framework.Felix.resolveBundleRevision(Felix.java:3832)

                                at org.apache.felix.framework.Felix.startBundle(Felix.java:1868)

                                at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1191)

                                at org.apache.felix.framework.FrameworkStartLevelImpl.run(FrameworkStartLevelImpl.java:295)

                                at java.lang.Thread.run(Thread.java:662)

                        org.osgi.framework.BundleException: Unresolved constraint in bundle org.jboss.weld.osgi.weld-osgi-core-integration [17]: Unable to resolve 17.0: missing requirement [17.0] osgi.wiring.package; (&(osgi.wiring.package=org.jboss.weld)(version>=1.2.0.SNAPSHOT))

                                at org.apache.felix.framework.Felix.resolveBundleRevision(Felix.java:3826)

                                at org.apache.felix.framework.Felix.startBundle(Felix.java:1868)

                                at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1191)

                                at org.apache.felix.framework.FrameworkStartLevelImpl.run(FrameworkStartLevelImpl.java:295)

                          org.jboss.weld.osgi.weld-osgi-core-api [14.0]

                            import: (osgi.wiring.package=javax.inject)

                                at java.lang.Thread.run(Thread.java:662)

                             |

                            export: osgi.wiring.package=javax.inject

                          org.apache.geronimo.specs.geronimo-atinject_1.0_spec [12.0])

                        ERROR: Bundle org.jboss.weld.osgi.weld-osgi-core-integration [17] Error starting mvn:org.jboss.weld.osgi/weld-osgi-core-integration/1.2.0-SNAPSHOT (org.osgi.framework.BundleException: Unresolved constraint in bundle org.jboss.weld.osgi.weld-osgi-core-integration [17]: Unable to resolve 17.0: missing requirement [17.0] osgi.wiring.package; (&(osgi.wiring.package=org.jboss.weld)(version>=1.2.0.SNAPSHOT)))

                        org.ops4j.pax.logging.pax-logging-api[org.ops4j.pax.swissbox.extender.BundleWatcher] : Scanning bundle [org.ops4j.pax.exam.invoker.junit]

                        ERROR: Bundle org.jboss.weld.osgi.tests.weld-osgi-bundle1 [20] Error starting mvn:org.jboss.weld.osgi.tests/weld-osgi-bundle1/1.2.0-SNAPSHOT (org.osgi.framework.BundleException: Uses constraint violation. Unable to resolve bundle revision org.jboss.weld.osgi.tests.weld-osgi-bundle1 [20.0] because it is exposed to package 'javax.inject' from bundle revisions org.jboss.weld.osgi.weld-osgi-core-mandatory [13.0] and org.apache.geronimo.specs.ger

                         

                        Chain 1:

                        org.osgi.framework.BundleException: Uses constraint violation. Unable to resolve bundle revision org.jboss.weld.osgi.tests.weld-osgi-bundle1 [20.0] because it is exposed to package 'javax.inject' from bundle revisions org.jboss.weld.osgi.weld-osgi-core-mandatory [13.0] and org.apache.geronimo.specs.geronimo-atinject_1.0_spec [12.0] via two dependency chains.

                         

                        Chain 1:

                          org.jboss.weld.osgi.tests.weld-osgi-bundle1 [20.0]

                            import: (osgi.wiring.package=javax.inject)

                             |

                          org.jboss.weld.osgi.tests.weld-osgi-bundle1 [20.0]

                            import: (osgi.wiring.package=javax.inject)

                             |

                            export: osgi.wiring.package=javax.inject

                            export: osgi.wiring.package=javax.inject

                          org.jboss.weld.osgi.weld-osgi-core-mandatory [13.0]

                         

                          org.jboss.weld.osgi.weld-osgi-core-mandatory [13.0]

                         

                        Chain 2:

                        Chain 2:

                          org.jboss.weld.osgi.tests.weld-osgi-bundle1 [20.0]

                            import: (&(osgi.wiring.package=org.jboss.weld.environment.osgi.api.events)(version>=1.2.0))

                          org.jboss.weld.osgi.tests.weld-osgi-bundle1 [20.0]

                            import: (&(osgi.wiring.package=org.jboss.weld.environment.osgi.api.events)(version>=1.2.0))

                             |

                             |

                            export: osgi.wiring.package=org.jboss.weld.environment.osgi.api.events; uses:=javax.inject

                            export: osgi.wiring.package=org.jboss.weld.environment.osgi.api.events; uses:=javax.inject

                          org.jboss.weld.osgi.weld-osgi-core-api [14.0]

                            import: (osgi.wiring.package=javax.inject)

                             |

                          org.jboss.weld.osgi.weld-osgi-core-api [14.0]

                            import: (osgi.wiring.package=javax.inject)

                             |

                            export: osgi.wiring.package=javax.inject

                            export: osgi.wiring.package=javax.inject

                          org.apache.geronimo.specs.geronimo-atinject_1.0_spec [12.0]

                          org.apache.geronimo.specs.geronimo-atinject_1.0_spec [12.0])

                                at org.apache.felix.framework.Felix.resolveBundleRevision(Felix.java:3832)

                                at org.apache.felix.framework.Felix.startBundle(Felix.java:1868)

                                at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1191)

                                at org.apache.felix.framework.FrameworkStartLevelImpl.run(FrameworkStartLevelImpl.java:295)

                                at java.lang.Thread.run(Thread.java:662)

                        org.osgi.framework.BundleException: Uses constraint violation. Unable to resolve bundle revision org.jboss.weld.osgi.tests.weld-osgi-bundle1 [20.0] because it is exposed to package 'javax.inject' from bundle revisions org.jboss.weld.osgi.weld-osgi-core-mandatory [13.0] and org.apache.geronimo.specs.geronimo-atinject_1.0_spec [12.0] via two dependency chains.

                         

                        ERROR: Bundle org.jboss.weld.osgi.tests.weld-osgi-bundle2 [21] Error starting mvn:org.jboss.weld.osgi.tests/weld-osgi-bundle2/1.2.0-SNAPSHOT (org.osgi.framework.BundleException: Uses constraint violation. Unable to resolve bundle revision org.jboss.weld.osgi.tests.weld-osgi-bundle1 [20.0] because it is exposed to package 'javax.inject' from bundle revisions org.jboss.weld.osgi.weld-osgi-core-mandatory [13.0] and org.apache.geronimo.specs.ger

                         

                        Chain 1:

                        Chain 1:

                          org.jboss.weld.osgi.tests.weld-osgi-bundle1 [20.0]

                          org.jboss.weld.osgi.tests.weld-osgi-bundle1 [20.0]

                            import: (osgi.wiring.package=javax.inject)

                             |

                            export: osgi.wiring.package=javax.inject

                            import: (osgi.wiring.package=javax.inject)

                          org.jboss.weld.osgi.weld-osgi-core-mandatory [13.0]

                             |

                         

                        Chain 2:

                          org.jboss.weld.osgi.tests.weld-osgi-bundle1 [20.0]

                            export: osgi.wiring.package=javax.inject

                            import: (&(osgi.wiring.package=org.jboss.weld.environment.osgi.api.events)(version>=1.2.0))

                          org.jboss.weld.osgi.weld-osgi-core-mandatory [13.0]

                             |

                            export: osgi.wiring.package=org.jboss.weld.environment.osgi.api.events; uses:=javax.inject

                          org.jboss.weld.osgi.weld-osgi-core-api [14.0]

                         

                            import: (osgi.wiring.package=javax.inject)

                             |

                        Chain 2:

                          org.jboss.weld.osgi.tests.weld-osgi-bundle1 [20.0]

                            export: osgi.wiring.package=javax.inject

                          org.apache.geronimo.specs.geronimo-atinject_1.0_spec [12.0])

                        ERROR: Bundle org.jboss.weld.osgi.tests.weld-osgi-bundle3 [22] Error starting mvn:org.jboss.weld.osgi.tests/weld-osgi-bundle3/1.2.0-SNAPSHOT (org.osgi.framework.BundleException: Uses constraint violation. Unable to resolve bundle revision org.jboss.weld.osgi.tests.weld-osgi-bundle1 [20.0] because it is exposed to package 'javax.inject' from bundle revisions org.jboss.weld.osgi.weld-osgi-core-mandatory [13.0] and org.apache.geronimo.specs.ger

                         

                            import: (&(osgi.wiring.package=org.jboss.weld.environment.osgi.api.events)(version>=1.2.0))

                             |

                            export: osgi.wiring.package=org.jboss.weld.environment.osgi.api.events; uses:=javax.inject

                          org.jboss.weld.osgi.weld-osgi-core-api [14.0]

                            import: (osgi.wiring.package=javax.inject)

                             |

                            export: osgi.wiring.package=javax.inject

                          org.apache.geronimo.specs.geronimo-atinject_1.0_spec [12.0]

                                at org.apache.felix.framework.Felix.resolveBundleRevision(Felix.java:3832)

                                at org.apache.felix.framework.Felix.startBundle(Felix.java:1868)

                        Chain 1:

                                at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1191)

                          org.jboss.weld.osgi.tests.weld-osgi-bundle1 [20.0]

                            import: (osgi.wiring.package=javax.inject)

                             |

                                at org.apache.felix.framework.FrameworkStartLevelImpl.run(FrameworkStartLevelImpl.java:295)

                                at java.lang.Thread.run(Thread.java:662)

                            export: osgi.wiring.package=javax.inject

                        org.osgi.framework.BundleException: Uses constraint violation. Unable to resolve bundle revision org.jboss.weld.osgi.tests.weld-osgi-bundle1 [20.0] because it is exposed to package 'javax.inject' from bundle revisions org.jboss.weld.osgi.weld-osgi-core-mandatory [13.0] and org.apache.geronimo.specs.geronimo-atinject_1.0_spec [12.0] via two dependency chains.

                         

                          org.jboss.weld.osgi.weld-osgi-core-mandatory [13.0]

                        Chain 1:

                          org.jboss.weld.osgi.tests.weld-osgi-bundle1 [20.0]

                            import: (osgi.wiring.package=javax.inject)

                             |

                         

                        Chain 2:

                            export: osgi.wiring.package=javax.inject

                          org.jboss.weld.osgi.weld-osgi-core-mandatory [13.0]

                         

                          org.jboss.weld.osgi.tests.weld-osgi-bundle1 [20.0]

                            import: (&(osgi.wiring.package=org.jboss.weld.environment.osgi.api.events)(version>=1.2.0))

                             |

                        Chain 2:

                          org.jboss.weld.osgi.tests.weld-osgi-bundle1 [20.0]

                            import: (&(osgi.wiring.package=org.jboss.weld.environment.osgi.api.events)(version>=1.2.0))

                             |

                            export: osgi.wiring.package=org.jboss.weld.environment.osgi.api.events; uses:=javax.inject

                          org.jboss.weld.osgi.weld-osgi-core-api [14.0]

                            import: (osgi.wiring.package=javax.inject)

                            export: osgi.wiring.package=org.jboss.weld.environment.osgi.api.events; uses:=javax.inject

                             |

                          org.jboss.weld.osgi.weld-osgi-core-api [14.0]

                            import: (osgi.wiring.package=javax.inject)

                             |

                            export: osgi.wiring.package=javax.inject

                            export: osgi.wiring.package=javax.inject

                          org.apache.geronimo.specs.geronimo-atinject_1.0_spec [12.0]

                          org.apache.geronimo.specs.geronimo-atinject_1.0_spec [12.0])

                                at org.apache.felix.framework.Felix.resolveBundleRevision(Felix.java:3832)

                                at org.apache.felix.framework.Felix.startBundle(Felix.java:1868)

                                at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1191)

                                at org.apache.felix.framework.FrameworkStartLevelImpl.run(FrameworkStartLevelImpl.java:295)

                                at java.lang.Thread.run(Thread.java:662)

                        16:53:30.375 [main] DEBUG o.o.p.e.n.i.NativeTestContainer - Installed bundle PAXEXAM-PROBE-8616bd14-0814-4508-89d8-6ca04917e6bc as Bundle ID 23

                        org.ops4j.pax.logging.pax-logging-api[org.ops4j.pax.swissbox.extender.BundleWatcher] : Scanning bundle [PAXEXAM-PROBE-8616bd14-0814-4508-89d8-6ca04917e6bc]

                        org.ops4j.pax.logging.pax-logging-api[org.ops4j.pax.swissbox.extender.BundleWatcher] : Found resources [ManifestEntry{ key=PaxExam-6b78324f-6850-4a19-baaf-4c5db9145e1f, value=org.jboss.weld.environment.osgi.tests.framework.UsageTest;launchTest }, ManifestEntry{ key=PaxExam-Executable, value=PaxExam-6b78324f-6850-4a19-baaf-4c5db9145e1f, }]

                        org.ops4j.pax.exam.extender.service[org.ops4j.pax.exam.raw.extender.intern.Probe] : Test PaxExam-6b78324f-6850-4a19-baaf-4c5db9145e1f to be in PaxExam-6b78324f-6850-4a19-baaf-4c5db9145e1f,

                        org.ops4j.pax.exam.extender.service[org.ops4j.pax.exam.raw.extender.intern.Probe] : Registering Service: org.ops4j.pax.exam.ProbeInvoker with Probe-Signature="PaxExam-6b78324f-6850-4a19-baaf-4c5db9145e1f" and expression="org.jboss.weld.environment.osgi.tests.framework.UsageTest;launchTest"

                        org.ops4j.pax.exam.extender.service[org.ops4j.pax.exam.raw.extender.intern.Probe] : Test PaxExam-Executable to be in PaxExam-6b78324f-6850-4a19-baaf-4c5db9145e1f,

                        org.ops4j.pax.exam.invoker.junit[org.ops4j.pax.exam.invoker.junit.internal.ContainerTestRunner] : running launchTest in reactor

                         

                         

                        My building env is as following:

                         

                        1. OS

                        Windows Xp

                         

                        2 JDK

                        jdk 1.6_31

                         

                        3 Maven

                        Maven 3.0.4

                         

                        However, while building core/osgi2 without testing, building will be successful.

                         

                        So, maybe some tests on windows platform have problems.

                         

                        --Best Regard!

                        --Tang

                        • 9. Re: weld-osgi Status?
                          Tang Yong Newbie

                          Hi Ales,

                           

                          I executed the core/osgi2 with tests again, although still failed, failed result is not same as the above thread.

                           

                          Results :

                           

                          Failed tests:

                            bundleLifeCycleTest:org.jboss.weld.environment.osgi.tests.framework.LifeCycleTest.bundleLifeCycleTest:NativeContainer:org.apache.felix.framework.FrameworkFactory@4d9ebf(org.jboss.weld.environment.osgi.tests.framework.LifeCycleTest)

                           

                          Tests run: 16, Failures: 1, Errors: 0, Skipped: 0

                           

                          And, the  failed test report is as following:

                           

                          -------------------------------------------------------------------------------

                          Test set: org.jboss.weld.environment.osgi.tests.framework.LifeCycleTest

                          -------------------------------------------------------------------------------

                          Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 8.938 sec <<< FAILURE!

                          bundleLifeCycleTest:org.jboss.weld.environment.osgi.tests.framework.LifeCycleTest.bundleLifeCycleTest:NativeContainer:org.apache.felix.framework.FrameworkFactory@4d9ebf(org.jboss.weld.environment.osgi.tests.framework.LifeCycleTest)  Time elapsed: 8.766 sec  <<< FAILURE!

                          java.lang.AssertionError: Wrong value (3) for field synchronousStartedEntrance expected:<2> but was:<4>

                              at org.junit.Assert.fail(Assert.java:93)

                              at org.junit.Assert.failNotEquals(Assert.java:647)

                              at org.junit.Assert.assertEquals(Assert.java:128)

                              at org.junit.Assert.assertEquals(Assert.java:472)

                              at org.jboss.weld.environment.osgi.tests.framework.LifeCycleTest.bundleLifeCycleTest(LifeCycleTest.java:165)

                              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.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44)

                              at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)

                              at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41)

                              at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20)

                              at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:263)

                              at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:69)

                              at org.ops4j.pax.exam.invoker.junit.internal.ContainerTestRunner.runChild(ContainerTestRunner.java:70)

                              at org.ops4j.pax.exam.invoker.junit.internal.ContainerTestRunner.runChild(ContainerTestRunner.java:37)

                              at org.junit.runners.ParentRunner$3.run(ParentRunner.java:231)

                              at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:60)

                              at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:229)

                              at org.junit.runners.ParentRunner.access$000(ParentRunner.java:50)

                              at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:222)

                              at org.junit.runners.ParentRunner.run(ParentRunner.java:292)

                              at org.junit.runner.JUnitCore.run(JUnitCore.java:157)

                              at org.junit.runner.JUnitCore.run(JUnitCore.java:136)

                              at org.ops4j.pax.exam.invoker.junit.internal.JUnitProbeInvoker.invokeViaJUnit(JUnitProbeInvoker.java:124)

                              at org.ops4j.pax.exam.invoker.junit.internal.JUnitProbeInvoker.findAndInvoke(JUnitProbeInvoker.java:94)

                              at org.ops4j.pax.exam.invoker.junit.internal.JUnitProbeInvoker.call(JUnitProbeInvoker.java:77)

                              at org.ops4j.pax.exam.nat.internal.NativeTestContainer.call(NativeTestContainer.java:95)

                              at org.ops4j.pax.exam.spi.reactors.AllConfinedStagedReactor.invoke(AllConfinedStagedReactor.java:74)

                              at org.ops4j.pax.exam.junit.JUnit4TestRunner$2.evaluate(JUnit4TestRunner.java:284)

                              at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:76)

                              at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50)

                              at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193)

                              at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52)

                              at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191)

                              at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42)

                              at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184)

                              at org.junit.runners.ParentRunner.run(ParentRunner.java:236)

                              at org.ops4j.pax.exam.junit.JUnit4TestRunner.run(JUnit4TestRunner.java:93)

                              at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:59)

                              at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:120)

                              at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:103)

                              at org.apache.maven.surefire.Surefire.run(Surefire.java:169)

                              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.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:350)

                              at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:1021)

                           

                           

                          --Tang

                          • 10. Re: weld-osgi Status?
                            Tang Yong Newbie

                            Hi Ales,

                             

                            After executing serveral "mvn clean install" again, the problem is still appeared on  "bundleLifeCycleTest:org.jboss.weld.environment.osgi.tests.framework.LifeCycleTest.bundleLifeCycleTest".

                             

                            -------------------------------------------------------------------------------

                            Test set: org.jboss.weld.environment.osgi.tests.framework.LifeCycleTest

                            -------------------------------------------------------------------------------

                            Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 6.265 sec <<< FAILURE!

                            bundleLifeCycleTest:org.jboss.weld.environment.osgi.tests.framework.LifeCycleTest.bundleLifeCycleTest:NativeContainer:org.apache.felix.framework.FrameworkFactory@2cef66(org.jboss.weld.environment.osgi.tests.framework.LifeCycleTest)  Time elapsed: 6.188 sec  <<< FAILURE!

                            java.lang.AssertionError: Wrong value (3) for field synchronousStartedEntrance expected:<2> but was:<4>

                                at org.junit.Assert.fail(Assert.java:93)

                                at org.junit.Assert.failNotEquals(Assert.java:647)

                                at org.junit.Assert.assertEquals(Assert.java:128)

                                at org.junit.Assert.assertEquals(Assert.java:472)

                                at org.jboss.weld.environment.osgi.tests.framework.LifeCycleTest.bundleLifeCycleTest(LifeCycleTest.java:165)

                                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.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44)

                                at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)

                                at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41)

                                at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20)

                                at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:263)

                                at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:69)

                                at org.ops4j.pax.exam.invoker.junit.internal.ContainerTestRunner.runChild(ContainerTestRunner.java:70)

                                at org.ops4j.pax.exam.invoker.junit.internal.ContainerTestRunner.runChild(ContainerTestRunner.java:37)

                                at org.junit.runners.ParentRunner$3.run(ParentRunner.java:231)

                                at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:60)

                                at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:229)

                                at org.junit.runners.ParentRunner.access$000(ParentRunner.java:50)

                                at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:222)

                                at org.junit.runners.ParentRunner.run(ParentRunner.java:292)

                                at org.junit.runner.JUnitCore.run(JUnitCore.java:157)

                                at org.junit.runner.JUnitCore.run(JUnitCore.java:136)

                                at org.ops4j.pax.exam.invoker.junit.internal.JUnitProbeInvoker.invokeViaJUnit(JUnitProbeInvoker.java:124)

                                at org.ops4j.pax.exam.invoker.junit.internal.JUnitProbeInvoker.findAndInvoke(JUnitProbeInvoker.java:94)

                                at org.ops4j.pax.exam.invoker.junit.internal.JUnitProbeInvoker.call(JUnitProbeInvoker.java:77)

                                at org.ops4j.pax.exam.nat.internal.NativeTestContainer.call(NativeTestContainer.java:95)

                                at org.ops4j.pax.exam.spi.reactors.AllConfinedStagedReactor.invoke(AllConfinedStagedReactor.java:74)

                                at org.ops4j.pax.exam.junit.JUnit4TestRunner$2.evaluate(JUnit4TestRunner.java:284)

                                at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:76)

                                at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50)

                                at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193)

                                at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52)

                                at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191)

                                at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42)

                                at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184)

                                at org.junit.runners.ParentRunner.run(ParentRunner.java:236)

                                at org.ops4j.pax.exam.junit.JUnit4TestRunner.run(JUnit4TestRunner.java:93)

                                at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:59)

                                at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:120)

                                at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:103)

                                at org.apache.maven.surefire.Surefire.run(Surefire.java:169)

                                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.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:350)

                                at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:1021)

                             

                            --Tang

                            • 11. Re: weld-osgi Status?
                              Ales Justin Master

                              Yeah. I got that one too, randomly.

                              Mathieu is back next week, so hopefully he'll be able to help.

                               

                              I also get some AS7 integration errors, which I'm looking into.

                               

                              But I guess you never get the resolution exception again?

                              As that one should be fixed, I removed one of the two same exports.

                              • 12. Re: weld-osgi Status?
                                Tang Yong Newbie

                                Ales Justin による書き込み:

                                 

                                Yeah. I got that one too, randomly.

                                Mathieu is back next week, so hopefully he'll be able to help.

                                 

                                I also get some AS7 integration errors, which I'm looking into.

                                 

                                But I guess you never get the resolution exception again?

                                As that one should be fixed, I removed one of the two same exports.

                                Yeah, I have not got the resolution exception again.

                                 

                                A question:

                                 

                                  Is there a plan for integration weld-osgi into AS7, for example, WELD-2.x.x?

                                 

                                --Tang

                                • 13. Re: weld-osgi Status?
                                  Ales Justin Master

                                    Is there a plan for integration weld-osgi into AS7, for example, WELD-2.x.x?

                                  Yes, we'll try to get 1.2.x - which will include OSGi integration - into AS7 asap.

                                  1 2 3 4 Previous Next