January 2010 - weld-issues - Jboss List Archives

[JBoss JIRA] Created: (WELDX-41) mvn install in extensions/trunk/se fails

by Martin Gencur (JIRA)

mvn install in extensions/trunk/se fails ---------------------------------------- Key: WELDX-41 URL: https://jira.jboss.org/jira/browse/WELDX-41 Project: Weld Extensions Issue Type: Bug Reporter: Martin Gencur Fix For: Spring integration 1.0.0.BETA1 When I check-out http://anonsvn.jboss.org/repos/weld/extensions/trunk/ and then run "mvn install" in /se subdirectory, maven outputs an error during compilation phase: (don't be confused with directory structure (Weld/weld-se/se... ) ....weld-se means trunk) [INFO] Compiling 14 source files to /home/mgencur/Java/Weld/weld-se/se/target/classes [INFO] ------------------------------------------------------------------------ [ERROR] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Compilation failure /home/mgencur/Java/Weld/weld-se/se/src/main/java/org/jboss/weld/environment/se/discovery/AbstractScanner.java:[21,25] package org.jboss.weld.log does not exist /home/mgencur/Java/Weld/weld-se/se/src/main/java/org/jboss/weld/environment/se/discovery/AbstractScanner.java:[22,25] package org.jboss.weld.log does not exist /home/mgencur/Java/Weld/weld-se/se/src/main/java/org/jboss/weld/environment/se/discovery/AbstractScanner.java:[35,24] cannot find symbol symbol : class LogProvider location: class org.jboss.weld.environment.se.discovery.AbstractScanner /home/mgencur/Java/Weld/weld-se/se/src/main/java/org/jboss/weld/environment/se/discovery/URLScanner.java:[32,25] package org.jboss.weld.log does not exist /home/mgencur/Java/Weld/weld-se/se/src/main/java/org/jboss/weld/environment/se/discovery/URLScanner.java:[33,25] package org.jboss.weld.log does not exist /home/mgencur/Java/Weld/weld-se/se/src/main/java/org/jboss/weld/environment/se/discovery/URLScanner.java:[46,24] cannot find symbol symbol : class LogProvider location: class org.jboss.weld.environment.se.discovery.URLScanner /home/mgencur/Java/Weld/weld-se/se/src/main/java/org/jboss/weld/environment/se/ShutdownManager.java:[26,25] package org.jboss.weld.log does not exist /home/mgencur/Java/Weld/weld-se/se/src/main/java/org/jboss/weld/environment/se/ShutdownManager.java:[27,25] package org.jboss.weld.log does not exist /home/mgencur/Java/Weld/weld-se/se/src/main/java/org/jboss/weld/environment/se/ShutdownManager.java:[33,18] cannot find symbol symbol : class LogProvider location: class org.jboss.weld.environment.se.ShutdownManager /home/mgencur/Java/Weld/weld-se/se/src/main/java/org/jboss/weld/environment/se/discovery/AbstractScanner.java:[35,42] cannot find symbol symbol : variable Logging location: class org.jboss.weld.environment.se.discovery.AbstractScanner /home/mgencur/Java/Weld/weld-se/se/src/main/java/org/jboss/weld/environment/se/discovery/URLScanner.java:[46,42] cannot find symbol symbol : variable Logging location: class org.jboss.weld.environment.se.discovery.URLScanner /home/mgencur/Java/Weld/weld-se/se/src/main/java/org/jboss/weld/environment/se/ShutdownManager.java:[33,36] cannot find symbol symbol : variable Logging location: class org.jboss.weld.environment.se.ShutdownManager [INFO] ------------------------------------------------------------------------ [INFO] For more information, run Maven with the -e switch [INFO] ------------------------------------------------------------------------ -- 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

14 years, 4 months

3
4
0 / 0

[JBoss JIRA] Created: (WELDX-50) Add new Weld() support for Java SE

by Pete Muir (JIRA)

Add new Weld() support for Java SE ---------------------------------- Key: WELDX-50 URL: https://jira.jboss.org/jira/browse/WELDX-50 Project: Weld Extensions Issue Type: Feature Request Reporter: Pete Muir Priority: Critical Fix For: Java SE 1.0.0.CR3 Add support for: Weld weld = new Weld().initialize(); weld.instance().select(Foo.class).get() weld.event().select(Bar.class).fire( new Bar() ); weld.shutdown(); -- 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

14 years, 4 months

2
3
0 / 0

[JBoss JIRA] Created: (WELDX-58) Modification to Weld Test to use SE Bootstrap

by Chris Pheby (JIRA)

Modification to Weld Test to use SE Bootstrap --------------------------------------------- Key: WELDX-58 URL: https://jira.jboss.org/jira/browse/WELDX-58 Project: Weld Extensions Issue Type: Patch Components: CDI Test, Java SE Affects Versions: Java SE 1.0.0.CR2, CDI Test 1.0.0.Beta1, CDI Test 1.0.0.Beta2 Environment: Windows Vista, Eclipse / Maven Reporter: Chris Pheby Fix For: CDI Test 1.0.0.Beta2 Thanks very much for Weld which is a great runtime evolved from the Seam framework, and thanks for Weld Test which brings JUnit testing in an elegant manner to the framework. My initial attempts to run Weld Test runtime were unsuccessful. Digging into the framework, I found it was very similar to the bootstrapping found in the SE runtime. Since the test framework runs out of container, it makes sense to reuse the SE runtime directly to benefit from the work going on there and reduce duplication. This patch is an effort to do that, and builds and executes the test using the SE runtime rather the Weld Test's own runtime. -- 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

14 years, 4 months

3
8
0 / 0

[JBoss JIRA] Created: (WELDX-47) BeanManager ELResolver should work even if JSF loads before Weld

by Dan Allen (JIRA)

BeanManager ELResolver should work even if JSF loads before Weld ---------------------------------------------------------------- Key: WELDX-47 URL: https://jira.jboss.org/jira/browse/WELDX-47 Project: Weld Extensions Issue Type: Feature Request Components: Servlet Containers Affects Versions: Servlet Containers 1.0.0.CR1 Reporter: Dan Allen Assignee: Dan Allen If the JSF listener starts before the Weld listener, then the BeanManager ELResolver was not making it into the JSF composite resolver chain. The problem is JSF impl specific, but we should safeguard against this problem anyway and use a forwarding ELResolver to accommodate. All details are provided in the linked issue WELDX-44, which is where the problem was discovered. -- 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

14 years, 4 months

2
2
0 / 0

[JBoss JIRA] Created: (WELDX-42) mvn install in extensions/trunk/ fails

by Martin Gencur (JIRA)

mvn install in extensions/trunk/ fails -------------------------------------- Key: WELDX-42 URL: https://jira.jboss.org/jira/browse/WELDX-42 Project: Weld Extensions Issue Type: Bug Reporter: Martin Gencur When I check-out http://anonsvn.jboss.org/repos/weld/extensions/trunk/ and then run "mvn install" in the root directory, maven outputs an error during compilation phase: (weld-se in the paths below means trunk/ ) [INFO] Scanning for projects... [INFO] ------------------------------------------------------------------------ [ERROR] FATAL ERROR [INFO] ------------------------------------------------------------------------ [INFO] Error building POM (may not be this project's POM). Project ID: org.jboss.weld.servlet:weld-servlet-int POM Location: /home/mgencur/Java/Weld/weld-se/servlet/int/pom.xml Validation Messages: [0] 'dependencies.dependency.version' is missing for org.jboss.weld:weld-logging Reason: Failed to validate POM for project org.jboss.weld.servlet:weld-servlet-int at /home/mgencur/Java/Weld/weld-se/servlet/int/pom.xml [INFO] ------------------------------------------------------------------------ [INFO] Trace org.apache.maven.reactor.MavenExecutionException: Failed to validate POM for project org.jboss.weld.servlet:weld-servlet-int at /home/mgencur/Java/Weld/weld-se/servlet/int/pom.xml at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:378) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:292) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) at org.apache.maven.cli.MavenCli.main(MavenCli.java:301) 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.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.project.InvalidProjectModelException: Failed to validate POM for project org.jboss.weld.servlet:weld-servlet-int at /home/mgencur/Java/Weld/weld-se/servlet/int/pom.xml at org.apache.maven.project.DefaultMavenProjectBuilder.processProjectLogic(DefaultMavenProjectBuilder.java:1107) at org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal(DefaultMavenProjectBuilder.java:877) at org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFileInternal(DefaultMavenProjectBuilder.java:505) at org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenProjectBuilder.java:197) at org.apache.maven.DefaultMaven.getProject(DefaultMaven.java:583) at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:461) at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:534) at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:534) at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:365) ... 11 more -- 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

14 years, 4 months

4
8
0 / 0

[JBoss JIRA] Created: (WELD-281) add ForwardingELResolver to SPI

by Dan Allen (JIRA)

add ForwardingELResolver to SPI ------------------------------- Key: WELD-281 URL: https://jira.jboss.org/jira/browse/WELD-281 Project: Weld Issue Type: Feature Request Components: Web Tier integration (JSF, JSP, EL and Servlet) Affects Versions: 1.0.0.CR1 Reporter: Dan Allen Assignee: Pete Muir Priority: Minor Fix For: 1.1.0.BETA1 Move ForwardingELResolver, which appears in both servlet-int and weld-int, to the SPI. -- 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

14 years, 4 months

2
1
0 / 0

[JBoss JIRA] Created: (WELD-401) Add getRemoteInterfaces() to EjbDescriptor

by Pete Muir (JIRA)

Add getRemoteInterfaces() to EjbDescriptor ------------------------------------------ Key: WELD-401 URL: https://jira.jboss.org/jira/browse/WELD-401 Project: Weld Issue Type: Feature Request Components: Weld SPI Reporter: Pete Muir Fix For: 1.1.0.BETA1 Needed to determine if a producer, disposer or observer method is part of the container view -- 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

14 years, 4 months

1
1
0 / 0

[JBoss JIRA] Created: (WELD-382) Move all classes which can be accessed by an integration to the SPI

by Pete Muir (JIRA)

Move all classes which can be accessed by an integration to the SPI ------------------------------------------------------------------- Key: WELD-382 URL: https://jira.jboss.org/jira/browse/WELD-382 Project: Weld Issue Type: Feature Request Reporter: Pete Muir Assignee: Pete Muir Fix For: 1.0.1.CR1 If it is required to have a class instance, options are to either reference the class name or delegate via reflection. Both are a bit eugh. Another option is to annotate the internal class and have a compiler plugin which picks up if it is moved. -- 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

14 years, 4 months

1
3
0 / 0

[JBoss JIRA] Created: (CDITCK-94) Route serialization/deserialization through SPI

by Pete Muir (JIRA)

Route serialization/deserialization through SPI ----------------------------------------------- Key: CDITCK-94 URL: https://jira.jboss.org/jira/browse/CDITCK-94 Project: CDI TCK Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Infrastructure Reporter: Pete Muir Fix For: 1.1.0.CR1 This allows a porting package to mirror the behavior of an app server which may provide special behavior 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

14 years, 4 months

2
4
0 / 0

[JBoss JIRA] Created: (WELDX-70) Automate testing of archetypes

by Steven Boscarine (JIRA)

Automate testing of archetypes ------------------------------ Key: WELDX-70 URL: https://jira.jboss.org/jira/browse/WELDX-70 Project: Weld Extensions Issue Type: Task Components: Archetypes Affects Versions: Archetypes 1.0.0-BETA1 Reporter: Steven Boscarine Assignee: Steven Boscarine This may be a difficult and funky task. I haven't been able to find examples of people automating maven calls. This may be a very pioneering task if done in Java. I do it presently with a shell script. Here's what needs to happen: An archetype needs to be built from source. (mvn clean install) A project needs to be created from the archetype. (mvn archetype:generate -DartifactId=myproject) The project's tests need to be run. (mvn clean test -f myproject/pom.xml) -- 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

14 years, 4 months

2
5
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

weld-issues January 2010