December 2009 - weld-issues - Jboss List Archives

[JBoss JIRA] Created: (CDITCK-61) Some tests have dependencies with jsr299-tck-api.jar and jsr299-tck-impl.jar

by Santiago Pericas-Geertsen (JIRA)

Some tests have dependencies with jsr299-tck-api.jar and jsr299-tck-impl.jar ---------------------------------------------------------------------------- Key: CDITCK-61 URL: https://jira.jboss.org/jira/browse/CDITCK-61 Project: CDI TCK Issue Type: Bug Security Level: Public (Everyone can see) Components: Tests Affects Versions: 1.0.1.CR1 Environment: Solaris x86 / JDK 16u6 / GF v3 Reporter: Santiago Pericas-Geertsen We have found that certain TCK test load classes from jsr299-tck-api.jar and jsr299-tck-impl.jar, but these jars are not normally included in the generated application bundles. An example of such a test is: *.deployment.packaging.installedLibrary.WarInstalledLibraryTest.test which looks for: org/jboss/jsr299/tck/tests/deployment/packaging/installedLibrary/Bar This test fails with GF as these classes are not available to applications. Should jsr299-tck-api.jar and jsr299-tck-impl.jar be bundled with apps? (We can provide a complete list of tests that depend on these TCK jars if needed). -- 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

12 years, 10 months

3
8
0 / 0

[JBoss JIRA] Created: (CDITCK-64) Add test for abstract decorators.

by Marius Bogoevici (JIRA)

Add test for abstract decorators. --------------------------------- Key: CDITCK-64 URL: https://jira.jboss.org/jira/browse/CDITCK-64 Project: CDI TCK Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Tests Affects Versions: 1.0.0.GA Reporter: Marius Bogoevici >From 8.1.3: "A decorator may be an abstract Java class, and is not required to implement every method of every decorated type." -- 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

12 years, 10 months

3
3
0 / 0

[JBoss JIRA] Created: (CDITCK-81) Switch to using specialized ObjectInputStream/ObjectOutputStream for serialization tests

by Pete Muir (JIRA)

Switch to using specialized ObjectInputStream/ObjectOutputStream for serialization tests ---------------------------------------------------------------------------------------- Key: CDITCK-81 URL: https://jira.jboss.org/jira/browse/CDITCK-81 Project: CDI TCK Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Tests 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

12 years, 10 months

2
1
0 / 0

[JBoss JIRA] Created: (WELD-358) InjectionPoint parameter on disposer method is null

by David Allen (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

13 years

4
7
0 / 0

[JBoss JIRA] Created: (WELD-347) META-INF/beans.xml not sufficient to activate CDI in WAR

by Dan Allen (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

13 years, 2 months

3
5
0 / 0

[JBoss JIRA] Created: (WELDX-34) Split out user API for SE module, and move to the api project/BOM

by Pete Muir (JIRA)

Split out user API for SE module, and move to the api project/BOM ----------------------------------------------------------------- Key: WELDX-34 URL: https://jira.jboss.org/jira/browse/WELDX-34 Project: Weld Extensions Issue Type: Feature Request Components: Java SE Reporter: Pete Muir We maintain a separate API project (SVN trunk etc.), BOM etc. Any developer-visible API for the SE extension (so perhaps any non-spec events you can observe?) should go here -- 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

13 years, 4 months

3
6
0 / 0

[JBoss JIRA] Created: (WELDX-51) Create a single jar file for Weld SE that includes all dependencies

by Pete Muir (JIRA)

Create a single jar file for Weld SE that includes all dependencies ------------------------------------------------------------------- Key: WELDX-51 URL: https://jira.jboss.org/jira/browse/WELDX-51 Project: Weld Extensions Issue Type: Feature Request Components: Java SE Reporter: Pete Muir Fix For: Java SE 1.0.0.CR3 To make using Weld SE easy, we should create a single jar (primarily for use at runtime, at compile time you would depend just on cdi-api of course) * cdi-api * weld-api * weld-spi * weld-core * weld-se -- 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

13 years, 4 months

5
14
0 / 0

[JBoss JIRA] Created: (CDITCK-44) Test coverage files are generated in directory from which maven is run

by Karel Piwko (JIRA)

Test coverage files are generated in directory from which maven is run ---------------------------------------------------------------------- Key: CDITCK-44 URL: https://jira.jboss.org/jira/browse/CDITCK-44 Project: CDI TCK Issue Type: Bug Security Level: Public (Everyone can see) Components: Infrastructure Affects Versions: 1.0.0.CR2 Reporter: Karel Piwko When running maven target (install) from another directory than cdi-tck root, test coverage is generated in directory from which maven was fired. This caused unexpected FileNotFound when artifacts are to be installed: [trunk]$ mvn cdi-tck/pom.xml -Dtck-audit=true clean install [INFO] Installing /home/kpiwko/devel/weld/trunk/cdi-tck/target/coverage-cdi.html to /home/kpiwko/.m2/repository/org/jboss/jsr299/tck/jsr299-tck-impl/1.0.0-SNAPSHOT/jsr299-tck-impl-1.0.0-SNAPSHOT-coverage-cdi.html [INFO] ------------------------------------------------------------------------ [ERROR] BUILD ERROR [INFO] ------------------------------------------------------------------------ [INFO] Error installing artifact: File /home/kpiwko/devel/weld/trunk/cdi-tck/target/coverage-cdi.html does not exist Target directory is generated in trunk. This bug causes problems with automatized testing on Hudson. -- 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

13 years, 7 months

3
6
0 / 0

[JBoss JIRA] Created: (WELD-323) XSD missing enable element

by Jason Porter (JIRA)

XSD missing enable element -------------------------- Key: WELD-323 URL: https://jira.jboss.org/jira/browse/WELD-323 Project: Weld Issue Type: Bug Affects Versions: 1.0.0.GA Reporter: Jason Porter Section 12.3 says there's an enable element, it's not there in the XSD. -- 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

13 years, 10 months

2
6
0 / 0

[JBoss JIRA] Created: (WELD-211) Tests which exercise an SPI implementation

by Pete Muir (JIRA)

Tests which exercise an SPI implementation ------------------------------------------ Key: WELD-211 URL: https://jira.jboss.org/jira/browse/WELD-211 Project: Weld Issue Type: Feature Request Components: Testing Infrastructure (Mocks and Harness Integration) Reporter: Pete Muir Fix For: 1.0.1.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

13 years, 11 months

1
5
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

weld-issues December 2009