Fix <scm> so that release plugin transforms properly
----------------------------------------------------
Key: CDITCK-98
URL: https://jira.jboss.org/jira/browse/CDITCK-98
Project: CDI TCK
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Infrastructure
Reporter: Pete Muir
Fix For: 1.1.0.CR1
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
InjectionPoint parameter on disposer method is null
---------------------------------------------------
Key: WELD-358
URL: https://jira.jboss.org/jira/browse/WELD-358
Project: Weld
Issue Type: Bug
Components: Producers (Methods, Fields and Disposers)
Affects Versions: 1.0.0.GA
Reporter: David Allen
Adding a parameter of type InjectionPoint on a disposer method should inject the corresponding meta-data for the place where the bean had been injected; for the bean being destroyed.
See http://www.seamframework.org/Community/DisposingAndInjectionPointIntegrat... and the Weld test org.jboss.weld.tests.producer.method.DisposalMethodInjectionPointTest.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Provide sane toString() for classes
-----------------------------------
Key: WELD-374
URL: https://jira.jboss.org/jira/browse/WELD-374
Project: Weld
Issue Type: Feature Request
Reporter: Pete Muir
Priority: Critical
Fix For: 1.0.1.CR1
Currently these vary in quality, some providing good info (e.g. WeldClassImpl), some too little (e.g. WeldFieldImpl) and some are just crazy.
In general, the approach should be to delegate the toString to the Names class (see toString(Class<?> rawType, Set<Annotation> annotations, Type[] actualTypeArguments) for a good one).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Convert weld-core-tests test suite to use Arquillian
----------------------------------------------------
Key: WELD-493
URL: https://jira.jboss.org/jira/browse/WELD-493
Project: Weld
Issue Type: Task
Components: Testing Infrastructure (Mocks and Harness Integration)
Reporter: Aslak Knutsen
Assignee: Aslak Knutsen
Rewrite the weld-core-test suite to use Arquillian.
src/test/ -> rewrite to use Arquillian
src/main/ -> move to Arquillian weld container
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
META-INF/beans.xml not sufficient to activate CDI in WAR
--------------------------------------------------------
Key: WELD-347
URL: https://jira.jboss.org/jira/browse/WELD-347
Project: Weld
Issue Type: Bug
Components: GlassFish Integration
Affects Versions: 1.0.0.GA
Reporter: Dan Allen
Assignee: Dan Allen
Fix For: 1.0.1.CR1
In GlassFish V3, if a WAR is deployed containing WEB-INF/classes/META-INF/beans.xml, CDI does not get activated (no beans are detected). Activation only happens if the WAR contains WEB-INF/beans.xml. I'm not sure why GlassFish V3 is having a problem finding beans.xml in the META-INF directory of the WAR classpath. I can't tell if it is a problem in Weld or a problem in GlassFish V3 somewhere.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
StartMain should support shutdown
---------------------------------
Key: WELDX-88
URL: https://jira.jboss.org/jira/browse/WELDX-88
Project: Weld Extensions
Issue Type: Feature Request
Components: Weld Extensions
Affects Versions: Java SE 1.0.1
Environment: n/a
Reporter: Edvin Syse
Priority: Minor
When starting a project with org.jboss.weld.environment.se.StartMain, one would assume that weld.shutdown() would be run upon jvm shutdown, but it is not. This could easily be fixed with a minor adjustment. Please see the attached StartMain.java.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Provide warnings if AnnotatedType is not sensible
-------------------------------------------------
Key: WELD-407
URL: https://jira.jboss.org/jira/browse/WELD-407
Project: Weld
Issue Type: Feature Request
Components: Bootstrap and Metamodel API
Reporter: Pete Muir
Priority: Minor
Fix For: 1.0.2.CR1
For example, if there are no constructors specified at all, or if the javaMember doesn't belong to the actual class hierarchy of the annotatedType
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Fluent messages
---------------
Key: WELD-388
URL: https://jira.jboss.org/jira/browse/WELD-388
Project: Weld
Issue Type: Feature Request
Affects Versions: 1.0.0.GA
Reporter: Nicklas Karlsson
Priority: Minor
Make error messages read more fluent instead of the "Message : detail" format sometimes seen
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Upgrade Weld examples to use shared Jetty/Tomcat plugins
--------------------------------------------------------
Key: WELD-539
URL: https://jira.jboss.org/browse/WELD-539
Project: Weld
Issue Type: Task
Components: Examples
Reporter: Pete Muir
Fix For: 1.0.2.CR1
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Weld does not work in OSGI container's classloader (and lacks OSGI bundles by the way)
--------------------------------------------------------------------------------------
Key: WELD-520
URL: https://jira.jboss.org/jira/browse/WELD-520
Project: Weld
Issue Type: Bug
Components: OSGi support
Affects Versions: 1.0.1.Final
Environment: Java SE, Weld 1.01 SE, Felix 2.02
Reporter: Morten Christensen
Priority: Critical
Weld SE will does not work inside an OSGI bundle. If you try to start WeldSE from within a OSGI bundle, you will get.
Error loading Weld bootstrap, check that Weld is on the classpath
at org.jboss.weld.environment.se.Weld.<init>(Weld.java:59)
Looking at the cause, it seems org.jboss.weld.environment.se.util.Reflections only works with Thread context classloaders and plain Class.forname both of which are NO-NO in osgi.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira