-
1. Re: visibility of CDI beans between deployment units
alesj Sep 27, 2012 10:09 AM (in response to peterfry)This should work.
But it could be that only today's :-) commit fixed this for good,
as this was a random/order-dependant bug which slipped by us for a long time.
Can you try latest Weld upstream master?
* https://github.com/weld/core
(simply build the project = mvn clean install, and replace the weld-core.jar in AS)
-
2. Re: visibility of CDI beans between deployment units
peterfry Sep 27, 2012 11:35 AM (in response to alesj)[ERROR] COMPILATION ERROR :
[INFO] -------------------------------------------------------------
[ERROR] \Projects\OPEN_ACCESS\weld-core-1.1.6.Final-106-g7437a60\weld-core-7437a60\impl\src\main\java\org\jboss\weld\introspector\jlr\WeldClassImpl.java:[604,31] type parameters of <T>T cannot be det
rmined; no unique maximal instance exists for type variable T with upper bounds S,java.lang.Object[ERROR] \Projects\OPEN_ACCESS\weld-core-1.1.6.Final-106-g7437a60\weld-core-7437a60\impl\src\main\java\org\jboss\weld\bean\proxy\DecorationHelper.java:[67,48] type parameters of <T>T cannot be determi
ed; no unique maximal instance exists for type variable T with upper bounds T,java.lang.Object[INFO] 2 errors
[INFO] -------------------------------------------------------------
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] Weld: Build Configuration ......................... SUCCESS [2.419s]
[INFO] Weld Parent ....................................... SUCCESS [1.311s]
[INFO] Weld Implementation ............................... FAILURE [3.432s]
[INFO] Weld Integration Tests - JBoss Test Harness (JBoss AS) SKIPPED
[INFO] Weld Porting Package for the CDI TCK .............. SKIPPED
[INFO] Weld Integration Tests (JBoss AS) ................. SKIPPED
[INFO] AtInject TCK runner for Weld ...................... SKIPPED
[INFO] CDI TCK runner for Weld (JBoss AS) ................ SKIPPED
[INFO] Weld SE (Core) .................................... SKIPPED
[INFO] Weld SE (Uber Jar) ................................ SKIPPED
[INFO] Weld Servlet Parent ............................... SKIPPED
[INFO] Weld Servlet Core ................................. SKIPPED
[INFO] Weld Servlet (Uber Jar) ........................... SKIPPED
[INFO] Weld Servlet Integration Tests (Base) ............. SKIPPED
[INFO] Weld Servlet Integration Tests (Tomcat) ........... SKIPPED
[INFO] Weld Servlet Integration Tests (Tomcat7) .......... SKIPPED
[INFO] Weld Servlet Integration Tests (Jetty) ............ SKIPPED
[INFO] Weld Servlet Integration Tests (Jetty7) ........... SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 7.817s
[INFO] Finished at: Thu Sep 27 16:17:17 BST 2012
[INFO] Final Memory: 26M/63M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:2.3.1:compile (default-compile) on project weld-core: Compilation failure: Compilation failure:
[ERROR] \Projects\OPEN_ACCESS\weld-core-1.1.6.Final-106-g7437a60\weld-core-7437a60\impl\src\main\java\org\jboss\weld\introspector\jlr\WeldClassImpl.java:[604,31] type parameters of <T>T cannot be det
rmined; no unique maximal instance exists for type variable T with upper bounds S,java.lang.Object
[ERROR]
[ERROR] \Projects\OPEN_ACCESS\weld-core-1.1.6.Final-106-g7437a60\weld-core-7437a60\impl\src\main\java\org\jboss\weld\bean\proxy\DecorationHelper.java:[67,48] type parameters of <T>T cannot be determi
ed; no unique maximal instance exists for type variable T with upper bounds T,java.lang.Object
[ERROR] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[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 :weld-coreVersion of Java is 1.6.0_23, do you have the issue number - I might be able to take a recent binary build?
-
3. Re: visibility of CDI beans between deployment units
peterfry Oct 4, 2012 5:02 AM (in response to alesj)Ales,
Can you provide the bug number so I can track which build of weld fixes it?
I think my compilation error when trying to build the snap shot is due to a bug in the version of the JDK that I am using.
Peter.
-
4. Re: visibility of CDI beans between deployment units
alesj Oct 4, 2012 5:19 AM (in response to peterfry)It's gonna be in next 1.1.10.Final release.