April 2010 - weld-issues - Jboss List Archives

[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

15 years, 7 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

15 years, 7 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

15 years, 7 months

1
1
0 / 0

[JBoss JIRA] Created: (WELD-481) Debug-level summary

by Nicklas Karlsson (JIRA)

Debug-level summary -------------------- Key: WELD-481 URL: https://jira.jboss.org/jira/browse/WELD-481 Project: Weld Issue Type: Feature Request Components: Bootstrap and Metamodel API Affects Versions: 1.0.1.Final Reporter: Nicklas Karlsson Assignee: Nicklas Karlsson Priority: Minor Fix For: 1.0.2.CR1 > It would be handy if Seam could be configured for full boot-time output that would include > * All modules present > * All enabled interceptors in correct ordering > * All enabled decorators in correct ordering > * All alternative beans and what they shade > * All effective beans and their effective execution path, i.e. the order of enabled interceptors and decorators that fire on the way to a method > (this would require a largeish resolve operation at the end of boot but can probably be a lifesaver when things go wrong) -- 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

15 years, 7 months

2
2
0 / 0

[JBoss JIRA] Created: (WELD-423) Make weld-numberguess-wicket run on GAE

by Pete Muir (JIRA)

Make weld-numberguess-wicket run on GAE --------------------------------------- Key: WELD-423 URL: https://jira.jboss.org/jira/browse/WELD-423 Project: Weld Issue Type: Task Components: Examples Reporter: Pete Muir Assignee: Shane Bryzak Fix For: 1.0.1.GA -- 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

15 years, 7 months

1
3
0 / 0

[JBoss JIRA] Created: (WELD-485) ProcessAnnotatedType event should be run for types added through BeforeBeanDiscovery.addAnnotatedType

by Stuart Douglas (JIRA)

ProcessAnnotatedType event should be run for types added through BeforeBeanDiscovery.addAnnotatedType ----------------------------------------------------------------------------------------------------- Key: WELD-485 URL: https://jira.jboss.org/jira/browse/WELD-485 Project: Weld Issue Type: Bug Affects Versions: 1.0.1.Final Reporter: Stuart Douglas 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/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 7 months

2
8
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

15 years, 7 months

1
3
0 / 0

[JBoss JIRA] Created: (WELD-455) @Observes(notifyObserver=IF_EXISTS) should be @Observes(receive=IF_EXISTS)

by Matthieu Chase Heimer (JIRA)

@Observes(notifyObserver=IF_EXISTS) should be @Observes(receive=IF_EXISTS) -------------------------------------------------------------------------- Key: WELD-455 URL: https://jira.jboss.org/jira/browse/WELD-455 Project: Weld Issue Type: Bug Components: CDI API, Events Affects Versions: 1.0.1.Final Environment: Windows XP SP3, NetBeans 6.8, GlassFish v3 Reporter: Matthieu Chase Heimer @Observes has an element named "notifyObserver" of type javax.enterprise.event.Reception but the name should be "receive". See page 75 of the CDI spec, 10.4.3. Conditional observer methods. -- 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

15 years, 7 months

3
5
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

15 years, 7 months

2
4
0 / 0

[JBoss JIRA] Created: (WELD-473) required meta-annotations for a qualifier specified differently in spec and API

by Wolfgang Frech (JIRA)

required meta-annotations for a qualifier specified differently in spec and API ------------------------------------------------------------------------------- Key: WELD-473 URL: https://jira.jboss.org/jira/browse/WELD-473 Project: Weld Issue Type: Bug Affects Versions: 1.0.1.Final Environment: n/a Reporter: Wolfgang Frech The specification and the API documentation differ on the required and optional meta-annotations of a qualfiier. JSR-299, 2.3.2 Defining new qualfier type specifies @Target(METHOD, FIELD, PARAMETER, TYPE} ("is") @Retention(RUNTIME) ("is") @Qualifier, but only optional ("may") API-Doc of Qualifier specifies @Qualifier @Retention(RUNTIME) @Documented (optional, typical) @Target optional, but various element types as targets possible Both agree on Retention only. As a third source I might have a look at the code and the implemented validity check. I have not so far. I am a bit fussy about this because a missing @Target of my first custom scope messed up the proxying. -- 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

15 years, 7 months

2
3
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

weld-issues April 2010