[weld-issues] [JBoss JIRA] (WELD-1056) Weld-servlet brings transitive dependency on weld-build-config
[
https://issues.jboss.org/browse/WELD-1056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12672473#comment-12672473
]
Lukáš Fryč commented on WELD-1056:
--
Pull request sent, build passes tests and checkstyle plugin seems to work fine:
https://github.com/weld/core/pull/158
Weld-servlet brings transitive dependency on weld-build-config
--
Key: WELD-1056
URL: https://issues.jboss.org/browse/WELD-1056
Project: Weld
Issue Type: Bug
Affects Versions: 1.1.4.Final
Reporter: Lukáš Fryč
This transitive dependency comes from {{weld-core-parent}}:
https://github.com/weld/core/blob/e20e1b9b7f5d22e2bff3d3f1d2812b1ff8f99b42/pom.xml#L501
Since this config currently contains only checkstyle definitions,
I suggest to remove this project dependency and use only
{{maven-checkstyle-plugin}} dependency (which is currently configured too):
https://github.com/weld/core/blob/e20e1b9b7f5d22e2bff3d3f1d2812b1ff8f99b42/pom.xml#L539
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
___
weld-issues mailing list
weld-issues@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-1007) Weld SE startup fails.
[
https://issues.jboss.org/browse/WELD-1007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12672587#comment-12672587
]
Sam Corbett commented on WELD-1007:
---
Apologies, the error was quite a way back up the log and I missed it. Our
offender is {{com.google.common.collect.LinkedListMultimap$ValueForKeyIterator}}
{code}12:17:27,400 TRACE [org.jboss.weld.ClassLoading] (MSC service thread 1-3)
Error loading class
'com.google.common.collect.LinkedListMultimap$ValueForKeyIterator' :
java.lang.ArrayIndexOutOfBoundsException: 1{code}
Weld SE startup fails.
--
Key: WELD-1007
URL: https://issues.jboss.org/browse/WELD-1007
Project: Weld
Issue Type: Bug
Components: Java SE Support
Affects Versions: 1.1.1.Final, 1.1.2.Final, 1.1.3.Final
Environment: Arch Linux, Linux kernel 3.0.7
java version 1.7.0_02-ea
Java(TM) SE Runtime Environment (build 1.7.0_02-ea-b11)
Java HotSpot(TM) Server VM (build 22.0-b08, mixed mode)
java version 1.6.0_26
Java(TM) SE Runtime Environment (build 1.6.0_26-b03)
Java HotSpot(TM) 64-Bit Server VM (build 20.1-b02, mixed mode)
Reporter: Konstantin Gribov
Attachments: weld-se-test.tar.gz
I use {{org.jboss.weld.environment.se.StartMain}} to bootstrap weld se
environment. Project is compiled and packaged by maven. When starting
assembly it fails with such stacktrace:
{quote}
Exception in thread main com.google.common.collect.ComputationException:
java.lang.ArrayIndexOutOfBoundsException: 3
at
com.google.common.collect.ComputingConcurrentHashMap.compute(ComputingConcurrentHashMap.java:218)
at
com.google.common.collect.ComputingConcurrentHashMap.apply(ComputingConcurrentHashMap.java:100)
at
com.google.common.collect.MapMaker$ComputingMapAdapter.get(MapMaker.java:515)
at
org.jboss.weld.resources.ClassTransformer.loadClass(ClassTransformer.java:183)
at
org.jboss.weld.introspector.jlr.WeldClassImpl.init(WeldClassImpl.java:128)
at
org.jboss.weld.introspector.jlr.WeldClassImpl.of(WeldClassImpl.java:98)
at
org.jboss.weld.resources.ClassTransformer$TransformTypeToWeldClass.apply(ClassTransformer.java:54)
at
org.jboss.weld.resources.ClassTransformer$TransformTypeToWeldClass.apply(ClassTransformer.java:42)
at
com.google.common.collect.ComputingConcurrentHashMap.compute(ComputingConcurrentHashMap.java:206)
at
com.google.common.collect.ComputingConcurrentHashMap.apply(ComputingConcurrentHashMap.java:100)
at
com.google.common.collect.MapMaker$ComputingMapAdapter.get(MapMaker.java:515)
at
org.jboss.weld.resources.ClassTransformer.loadClass(ClassTransformer.java:183)
at
org.jboss.weld.introspector.jlr.WeldClassImpl.init(WeldClassImpl.java:128)
at
org.jboss.weld.introspector.jlr.WeldClassImpl.of(WeldClassImpl.java:98)
at
org.jboss.weld.resources.ClassTransformer$TransformTypeToWeldClass.apply(ClassTransformer.java:54)
at
org.jboss.weld.resources.ClassTransformer$TransformTypeToWeldClass.apply(ClassTransformer.java:42)
at
com.google.common.collect.ComputingConcurrentHashMap.compute(ComputingConcurrentHashMap.java:206)
at
com.google.common.collect.ComputingConcurrentHashMap.apply(ComputingConcurrentHashMap.java:100)
at
com.google.common.collect.MapMaker$ComputingMapAdapter.get(MapMaker.java:515)
at
org.jboss.weld.resources.ClassTransformer.loadClass(ClassTransformer.java:183)
at
org.jboss.weld.bootstrap.BeanDeployer.addClass(BeanDeployer.java:95)
at
org.jboss.weld.bootstrap.BeanDeployer.addClasses(BeanDeployer.java:134)
at
org.jboss.weld.bootstrap.BeanDeployment.createBeans(BeanDeployment.java:191)
at
org.jboss.weld.bootstrap.WeldBootstrap.deployBeans(WeldBootstrap.java:368)
at org.jboss.weld.environment.se.Weld.initialize(Weld.java:92)
at org.jboss.weld.environment.se.StartMain.go(StartMain.java:46)
at org.jboss.weld.environment.se.StartMain.main(StartMain.java:59)
Caused by: java.lang.ArrayIndexOutOfBoundsException: 3
at
org.jboss.weld.introspector.jlr.WeldConstructorImpl.init(WeldConstructorImpl.java:113)
at
org.jboss.weld.introspector.jlr.WeldConstructorImpl.of(WeldConstructorImpl.java:70)
at
org.jboss.weld.introspector.jlr.WeldClassImpl.init(WeldClassImpl.java:210)
at
org.jboss.weld.introspector.jlr.WeldClassImpl.of(WeldClassImpl.java:98)
at
org.jboss.weld.resources.ClassTransformer$TransformTypeToWeldClass.apply(ClassTransformer.java:54)
at
org.jboss.weld.resources.ClassTransformer$TransformTypeToWeldClass.apply(ClassTransformer.java:42)
at
[weld-issues] [JBoss JIRA] (WELD-1007) Weld SE startup fails.
[
https://issues.jboss.org/browse/WELD-1007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12672597#comment-12672597
]
Ales Justin commented on WELD-1007:
---
Is this easily reproducible?
Weld SE startup fails.
--
Key: WELD-1007
URL: https://issues.jboss.org/browse/WELD-1007
Project: Weld
Issue Type: Bug
Components: Java SE Support
Affects Versions: 1.1.1.Final, 1.1.2.Final, 1.1.3.Final
Environment: Arch Linux, Linux kernel 3.0.7
java version 1.7.0_02-ea
Java(TM) SE Runtime Environment (build 1.7.0_02-ea-b11)
Java HotSpot(TM) Server VM (build 22.0-b08, mixed mode)
java version 1.6.0_26
Java(TM) SE Runtime Environment (build 1.6.0_26-b03)
Java HotSpot(TM) 64-Bit Server VM (build 20.1-b02, mixed mode)
Reporter: Konstantin Gribov
Attachments: weld-se-test.tar.gz
I use {{org.jboss.weld.environment.se.StartMain}} to bootstrap weld se
environment. Project is compiled and packaged by maven. When starting
assembly it fails with such stacktrace:
{quote}
Exception in thread main com.google.common.collect.ComputationException:
java.lang.ArrayIndexOutOfBoundsException: 3
at
com.google.common.collect.ComputingConcurrentHashMap.compute(ComputingConcurrentHashMap.java:218)
at
com.google.common.collect.ComputingConcurrentHashMap.apply(ComputingConcurrentHashMap.java:100)
at
com.google.common.collect.MapMaker$ComputingMapAdapter.get(MapMaker.java:515)
at
org.jboss.weld.resources.ClassTransformer.loadClass(ClassTransformer.java:183)
at
org.jboss.weld.introspector.jlr.WeldClassImpl.init(WeldClassImpl.java:128)
at
org.jboss.weld.introspector.jlr.WeldClassImpl.of(WeldClassImpl.java:98)
at
org.jboss.weld.resources.ClassTransformer$TransformTypeToWeldClass.apply(ClassTransformer.java:54)
at
org.jboss.weld.resources.ClassTransformer$TransformTypeToWeldClass.apply(ClassTransformer.java:42)
at
com.google.common.collect.ComputingConcurrentHashMap.compute(ComputingConcurrentHashMap.java:206)
at
com.google.common.collect.ComputingConcurrentHashMap.apply(ComputingConcurrentHashMap.java:100)
at
com.google.common.collect.MapMaker$ComputingMapAdapter.get(MapMaker.java:515)
at
org.jboss.weld.resources.ClassTransformer.loadClass(ClassTransformer.java:183)
at
org.jboss.weld.introspector.jlr.WeldClassImpl.init(WeldClassImpl.java:128)
at
org.jboss.weld.introspector.jlr.WeldClassImpl.of(WeldClassImpl.java:98)
at
org.jboss.weld.resources.ClassTransformer$TransformTypeToWeldClass.apply(ClassTransformer.java:54)
at
org.jboss.weld.resources.ClassTransformer$TransformTypeToWeldClass.apply(ClassTransformer.java:42)
at
com.google.common.collect.ComputingConcurrentHashMap.compute(ComputingConcurrentHashMap.java:206)
at
com.google.common.collect.ComputingConcurrentHashMap.apply(ComputingConcurrentHashMap.java:100)
at
com.google.common.collect.MapMaker$ComputingMapAdapter.get(MapMaker.java:515)
at
org.jboss.weld.resources.ClassTransformer.loadClass(ClassTransformer.java:183)
at
org.jboss.weld.bootstrap.BeanDeployer.addClass(BeanDeployer.java:95)
at
org.jboss.weld.bootstrap.BeanDeployer.addClasses(BeanDeployer.java:134)
at
org.jboss.weld.bootstrap.BeanDeployment.createBeans(BeanDeployment.java:191)
at
org.jboss.weld.bootstrap.WeldBootstrap.deployBeans(WeldBootstrap.java:368)
at org.jboss.weld.environment.se.Weld.initialize(Weld.java:92)
at org.jboss.weld.environment.se.StartMain.go(StartMain.java:46)
at org.jboss.weld.environment.se.StartMain.main(StartMain.java:59)
Caused by: java.lang.ArrayIndexOutOfBoundsException: 3
at
org.jboss.weld.introspector.jlr.WeldConstructorImpl.init(WeldConstructorImpl.java:113)
at
org.jboss.weld.introspector.jlr.WeldConstructorImpl.of(WeldConstructorImpl.java:70)
at
org.jboss.weld.introspector.jlr.WeldClassImpl.init(WeldClassImpl.java:210)
at
org.jboss.weld.introspector.jlr.WeldClassImpl.of(WeldClassImpl.java:98)
at
org.jboss.weld.resources.ClassTransformer$TransformTypeToWeldClass.apply(ClassTransformer.java:54)
at
org.jboss.weld.resources.ClassTransformer$TransformTypeToWeldClass.apply(ClassTransformer.java:42)
at
com.google.common.collect.ComputingConcurrentHashMap.compute(ComputingConcurrentHashMap.java:206)
{quote}
When I try to run this project in IntelliJ IDEA it works fine with such exec
command:
{quote}
/home/gross/soft/jdk1.7.0_02/bin/java -Didea.launcher.port=7537
-Didea.launcher.bin.path=/opt/idea/bin -Dfile.encoding=UTF-8 -classpath
[weld-issues] [JBoss JIRA] (WELD-27) Consider using JBoss maven plugin, not ant for example builds
[ https://issues.jboss.org/browse/WELD-27?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ales Justin resolved WELD-27. - Fix Version/s: 1.2.0.Beta1 (was: TBC) Resolution: Done Consider using JBoss maven plugin, not ant for example builds - Key: WELD-27 URL: https://issues.jboss.org/browse/WELD-27 Project: Weld Issue Type: Task Components: Examples Reporter: Pete Muir Assignee: Ales Justin Fix For: 1.2.0.Beta1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-989) #{conversation.id} instead of #{javax.enterprise.context.conversation.id} mentioned in the reference guide
[
https://issues.jboss.org/browse/WELD-989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marek Schmidt reassigned WELD-989:
--
Assignee: Ales Justin (was: Marek Schmidt)
https://github.com/weld/core/pull/163
#{conversation.id} instead of #{javax.enterprise.context.conversation.id}
mentioned in the reference guide
--
Key: WELD-989
URL: https://issues.jboss.org/browse/WELD-989
Project: Weld
Issue Type: Bug
Components: Documentation
Affects Versions: 1.1.2.Final
Reporter: Marek Schmidt
Assignee: Ales Justin
http://docs.jboss.org/weld/reference/latest/en-US/html/scopescontexts.html#d0e1884
on the line a href=/addProduct.jsp?cid=#{conversation.id}Add Product/a
and in the sentence The unique identifier of the conversation may be
obtained from the Conversation object, which has the EL bean name
conversation.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
___
weld-issues mailing list
weld-issues@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-989) #{conversation.id} instead of #{javax.enterprise.context.conversation.id} mentioned in the reference guide
[
https://issues.jboss.org/browse/WELD-989?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12672672#comment-12672672
]
Marek Schmidt edited comment on WELD-989 at 3/1/12 9:28 AM:
https://github.com/weld/core/pull/163
What is the proper way to also fix the translations?
was (Author: maschmid):
https://github.com/weld/core/pull/163
#{conversation.id} instead of #{javax.enterprise.context.conversation.id}
mentioned in the reference guide
--
Key: WELD-989
URL: https://issues.jboss.org/browse/WELD-989
Project: Weld
Issue Type: Bug
Components: Documentation
Affects Versions: 1.1.2.Final
Reporter: Marek Schmidt
Assignee: Ales Justin
http://docs.jboss.org/weld/reference/latest/en-US/html/scopescontexts.html#d0e1884
on the line a href=/addProduct.jsp?cid=#{conversation.id}Add Product/a
and in the sentence The unique identifier of the conversation may be
obtained from the Conversation object, which has the EL bean name
conversation.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
___
weld-issues mailing list
weld-issues@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-1007) Weld SE startup fails.
[
https://issues.jboss.org/browse/WELD-1007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12672675#comment-12672675
]
Sam Corbett commented on WELD-1007:
---
In as much as there's two projects (sharing a codebase) we're unable to deploy,
yes. I'll try to put together a small example.
Weld SE startup fails.
--
Key: WELD-1007
URL: https://issues.jboss.org/browse/WELD-1007
Project: Weld
Issue Type: Bug
Components: Java SE Support
Affects Versions: 1.1.1.Final, 1.1.2.Final, 1.1.3.Final
Environment: Arch Linux, Linux kernel 3.0.7
java version 1.7.0_02-ea
Java(TM) SE Runtime Environment (build 1.7.0_02-ea-b11)
Java HotSpot(TM) Server VM (build 22.0-b08, mixed mode)
java version 1.6.0_26
Java(TM) SE Runtime Environment (build 1.6.0_26-b03)
Java HotSpot(TM) 64-Bit Server VM (build 20.1-b02, mixed mode)
Reporter: Konstantin Gribov
Attachments: weld-se-test.tar.gz
I use {{org.jboss.weld.environment.se.StartMain}} to bootstrap weld se
environment. Project is compiled and packaged by maven. When starting
assembly it fails with such stacktrace:
{quote}
Exception in thread main com.google.common.collect.ComputationException:
java.lang.ArrayIndexOutOfBoundsException: 3
at
com.google.common.collect.ComputingConcurrentHashMap.compute(ComputingConcurrentHashMap.java:218)
at
com.google.common.collect.ComputingConcurrentHashMap.apply(ComputingConcurrentHashMap.java:100)
at
com.google.common.collect.MapMaker$ComputingMapAdapter.get(MapMaker.java:515)
at
org.jboss.weld.resources.ClassTransformer.loadClass(ClassTransformer.java:183)
at
org.jboss.weld.introspector.jlr.WeldClassImpl.init(WeldClassImpl.java:128)
at
org.jboss.weld.introspector.jlr.WeldClassImpl.of(WeldClassImpl.java:98)
at
org.jboss.weld.resources.ClassTransformer$TransformTypeToWeldClass.apply(ClassTransformer.java:54)
at
org.jboss.weld.resources.ClassTransformer$TransformTypeToWeldClass.apply(ClassTransformer.java:42)
at
com.google.common.collect.ComputingConcurrentHashMap.compute(ComputingConcurrentHashMap.java:206)
at
com.google.common.collect.ComputingConcurrentHashMap.apply(ComputingConcurrentHashMap.java:100)
at
com.google.common.collect.MapMaker$ComputingMapAdapter.get(MapMaker.java:515)
at
org.jboss.weld.resources.ClassTransformer.loadClass(ClassTransformer.java:183)
at
org.jboss.weld.introspector.jlr.WeldClassImpl.init(WeldClassImpl.java:128)
at
org.jboss.weld.introspector.jlr.WeldClassImpl.of(WeldClassImpl.java:98)
at
org.jboss.weld.resources.ClassTransformer$TransformTypeToWeldClass.apply(ClassTransformer.java:54)
at
org.jboss.weld.resources.ClassTransformer$TransformTypeToWeldClass.apply(ClassTransformer.java:42)
at
com.google.common.collect.ComputingConcurrentHashMap.compute(ComputingConcurrentHashMap.java:206)
at
com.google.common.collect.ComputingConcurrentHashMap.apply(ComputingConcurrentHashMap.java:100)
at
com.google.common.collect.MapMaker$ComputingMapAdapter.get(MapMaker.java:515)
at
org.jboss.weld.resources.ClassTransformer.loadClass(ClassTransformer.java:183)
at
org.jboss.weld.bootstrap.BeanDeployer.addClass(BeanDeployer.java:95)
at
org.jboss.weld.bootstrap.BeanDeployer.addClasses(BeanDeployer.java:134)
at
org.jboss.weld.bootstrap.BeanDeployment.createBeans(BeanDeployment.java:191)
at
org.jboss.weld.bootstrap.WeldBootstrap.deployBeans(WeldBootstrap.java:368)
at org.jboss.weld.environment.se.Weld.initialize(Weld.java:92)
at org.jboss.weld.environment.se.StartMain.go(StartMain.java:46)
at org.jboss.weld.environment.se.StartMain.main(StartMain.java:59)
Caused by: java.lang.ArrayIndexOutOfBoundsException: 3
at
org.jboss.weld.introspector.jlr.WeldConstructorImpl.init(WeldConstructorImpl.java:113)
at
org.jboss.weld.introspector.jlr.WeldConstructorImpl.of(WeldConstructorImpl.java:70)
at
org.jboss.weld.introspector.jlr.WeldClassImpl.init(WeldClassImpl.java:210)
at
org.jboss.weld.introspector.jlr.WeldClassImpl.of(WeldClassImpl.java:98)
at
org.jboss.weld.resources.ClassTransformer$TransformTypeToWeldClass.apply(ClassTransformer.java:54)
at
org.jboss.weld.resources.ClassTransformer$TransformTypeToWeldClass.apply(ClassTransformer.java:42)
at
com.google.common.collect.ComputingConcurrentHashMap.compute(ComputingConcurrentHashMap.java:206)
{quote}
When I try to run this project in IntelliJ IDEA it works fine with such exec
command:
{quote}
/home/gross/soft/jdk1.7.0_02/bin/java -Didea.launcher.port=7537
-Didea.launcher.bin.path=/opt/idea/bin
[weld-issues] [JBoss JIRA] (WELD-999) Interceptor binding transitivity broken
[ https://issues.jboss.org/browse/WELD-999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12672685#comment-12672685 ] Pete Muir commented on WELD-999: resolveInterceptors should resolve transitive interceptors, if that is what you are asking. Interceptor binding transitivity broken --- Key: WELD-999 URL: https://issues.jboss.org/browse/WELD-999 Project: Weld Issue Type: Bug Components: Interceptors and Decorators Affects Versions: 1.1.2.Final Reporter: Jozef Hartinger Assignee: Marko Lukša Fix For: 1.2.0.Beta1 See org.jboss.weld.tests.interceptors.binding.transitivity.InterceptorBindingTransitivityTest -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-926) Weld Servlet still uses old Google Collections instead of Guava
[ https://issues.jboss.org/browse/WELD-926?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ales Justin resolved WELD-926. -- Assignee: Ales Justin Fix Version/s: 1.2.0.Beta1 Resolution: Done Updated Guava to 11.0.2. Weld Servlet still uses old Google Collections instead of Guava --- Key: WELD-926 URL: https://issues.jboss.org/browse/WELD-926 Project: Weld Issue Type: Bug Components: Servlet Container Support Affects Versions: 1.1.1.Final Reporter: Sebastian Schaffert Assignee: Ales Justin Fix For: 1.2.0.Beta1 Even though WELD-564 is fixed, the latest version of Weld Servlet still includes the old Google Collections code. I think it should not contain the code at all and instead use a dependency on the library. Or at least update to the latest version of Guava. The problem is that it makes it impossible to use Guava in the same classpath as Weld. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-1068) Weld conversation crash when used in portlet
[ https://issues.jboss.org/browse/WELD-1068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12672712#comment-12672712 ] John Doyle commented on WELD-1068: -- Hi Marko Yep that solves it, thanks very much. Is there anywhere I can update (there's no weld wiki afaik) so other can find that filter too? Weld conversation crash when used in portlet Key: WELD-1068 URL: https://issues.jboss.org/browse/WELD-1068 Project: Weld Issue Type: Bug Components: Conversations Affects Versions: 1.1.5.Final Environment: Windows XP, Tomcat 7.0.23, Liferay 6.1.0 Community Edition GA1, Mojarra 2.1.6, portletfaces-bridge 2.0.0 Reporter: John Doyle Assignee: Marko Strukelj Attachments: portlet-test.war, test1.zip When attempting to view a JSF2/Weld based portlet in a portal the following exception is thrown: 14:11:54,917 ERROR [render_portlet_jsp:154] java.lang.IllegalStateException: Must call associate() before calling activate() at org.jboss.weld.context.AbstractConversationContext.activate(AbstractConversationContext.java:200) at org.jboss.weld.jsf.WeldPhaseListener.activateConversations(WeldPhaseListener.java:108) at org.jboss.weld.jsf.WeldPhaseListener.beforePhase(WeldPhaseListener.java:85) at com.sun.faces.lifecycle.Phase.handleBeforePhase(Phase.java:228) at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:99) at com.sun.faces.lifecycle.RestoreViewPhase.doPhase(RestoreViewPhase.java:116) at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:118) at org.portletfaces.bridge.BridgeImpl.doFacesRequest(BridgeImpl.java:391) at org.portletfaces.bridge.GenericFacesPortlet.doView(GenericFacesPortlet.java:181) at javax.portlet.GenericPortlet.doDispatch(GenericPortlet.java:328) at javax.portlet.GenericPortlet.render(GenericPortlet.java:233) at com.liferay.portlet.FilterChainImpl.doFilter(FilterChainImpl.java:100) at com.liferay.portal.kernel.portlet.PortletFilterUtil.doFilter(PortletFilterUtil.java:64) at com.liferay.portal.kernel.servlet.PortletServlet.service(PortletServlet.java:93) at javax.servlet.http.HttpServlet.service(HttpServlet.java:722) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at com.liferay.portal.kernel.servlet.filters.invoker.InvokerFilterChain.doFilter(InvokerFilterChain.java:72) at com.liferay.portal.kernel.servlet.filters.invoker.InvokerFilter.doFilter(InvokerFilter.java:70) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) This happens on viewing a page which starts a conversation. I'll try and attach a little example app to aid reproducing the problem. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-1068) Weld conversation crash when used in portlet
[ https://issues.jboss.org/browse/WELD-1068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ales Justin resolved WELD-1068. --- Fix Version/s: 1.2.0.Beta1 Resolution: Done Weld conversation crash when used in portlet Key: WELD-1068 URL: https://issues.jboss.org/browse/WELD-1068 Project: Weld Issue Type: Bug Components: Conversations Affects Versions: 1.1.5.Final Environment: Windows XP, Tomcat 7.0.23, Liferay 6.1.0 Community Edition GA1, Mojarra 2.1.6, portletfaces-bridge 2.0.0 Reporter: John Doyle Assignee: Marko Strukelj Fix For: 1.2.0.Beta1 Attachments: portlet-test.war, test1.zip When attempting to view a JSF2/Weld based portlet in a portal the following exception is thrown: 14:11:54,917 ERROR [render_portlet_jsp:154] java.lang.IllegalStateException: Must call associate() before calling activate() at org.jboss.weld.context.AbstractConversationContext.activate(AbstractConversationContext.java:200) at org.jboss.weld.jsf.WeldPhaseListener.activateConversations(WeldPhaseListener.java:108) at org.jboss.weld.jsf.WeldPhaseListener.beforePhase(WeldPhaseListener.java:85) at com.sun.faces.lifecycle.Phase.handleBeforePhase(Phase.java:228) at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:99) at com.sun.faces.lifecycle.RestoreViewPhase.doPhase(RestoreViewPhase.java:116) at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:118) at org.portletfaces.bridge.BridgeImpl.doFacesRequest(BridgeImpl.java:391) at org.portletfaces.bridge.GenericFacesPortlet.doView(GenericFacesPortlet.java:181) at javax.portlet.GenericPortlet.doDispatch(GenericPortlet.java:328) at javax.portlet.GenericPortlet.render(GenericPortlet.java:233) at com.liferay.portlet.FilterChainImpl.doFilter(FilterChainImpl.java:100) at com.liferay.portal.kernel.portlet.PortletFilterUtil.doFilter(PortletFilterUtil.java:64) at com.liferay.portal.kernel.servlet.PortletServlet.service(PortletServlet.java:93) at javax.servlet.http.HttpServlet.service(HttpServlet.java:722) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at com.liferay.portal.kernel.servlet.filters.invoker.InvokerFilterChain.doFilter(InvokerFilterChain.java:72) at com.liferay.portal.kernel.servlet.filters.invoker.InvokerFilter.doFilter(InvokerFilter.java:70) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) This happens on viewing a page which starts a conversation. I'll try and attach a little example app to aid reproducing the problem. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-1070) WeldPhaseListener destroys conversation too soon
[ https://issues.jboss.org/browse/WELD-1070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12672720#comment-12672720 ] Lincoln Baxter III commented on WELD-1070: -- The proper JSF order is to change the specification to use a Servlet Filter instead of a Phase Listener. Otherwise, if Seam Catch is using a Phase Listener or Filter to handle these things, we're out of luck because if it's a: 1. PhaseListener - we could maybe use the order tag in faces-config.xml to change order relative to Weld ... but, well... Weld is provided by the container, and I'm not sure it works in that case. 2. ServletFilter - this is just flat out of reach of the JSF lifecycle, and the WeldPhaseListener has no choice but to close early. This is a defective / poorly thought out piece of the specification. I believe it's being addressed in 1.1. WeldPhaseListener destroys conversation too soon Key: WELD-1070 URL: https://issues.jboss.org/browse/WELD-1070 Project: Weld Issue Type: Bug Components: Conversations Affects Versions: 1.1.4.Final Environment: gentoo, java 1.6, AS7.1.0.Beta1, Seam 3.1.0.Final Reporter: Bernard Labno In JSF app when exception is thrown during RenderResponse phase then firstly there is a call to afterPhase and later to exception handlers. WeldPhaseListener.afterPhase is invoked before error handler (Seam Catch in my case). My error handler wants to promote conversation to long-running and do redirect to error page, but conversation context is not active anymore now. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-1007) Weld SE startup fails.
[
https://issues.jboss.org/browse/WELD-1007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12672812#comment-12672812
]
Sam Corbett commented on WELD-1007:
---
Thanks. It appears the problem remains in both 7.0.0 and 7.1.0. I also tried -
rather hopefully! - including Guava 11.0.1 as a module alongside r06, but no
luck.
Weld SE startup fails.
--
Key: WELD-1007
URL: https://issues.jboss.org/browse/WELD-1007
Project: Weld
Issue Type: Bug
Components: Java SE Support
Affects Versions: 1.1.1.Final, 1.1.2.Final, 1.1.3.Final
Environment: Arch Linux, Linux kernel 3.0.7
java version 1.7.0_02-ea
Java(TM) SE Runtime Environment (build 1.7.0_02-ea-b11)
Java HotSpot(TM) Server VM (build 22.0-b08, mixed mode)
java version 1.6.0_26
Java(TM) SE Runtime Environment (build 1.6.0_26-b03)
Java HotSpot(TM) 64-Bit Server VM (build 20.1-b02, mixed mode)
Reporter: Konstantin Gribov
Attachments: weld-se-test.tar.gz
I use {{org.jboss.weld.environment.se.StartMain}} to bootstrap weld se
environment. Project is compiled and packaged by maven. When starting
assembly it fails with such stacktrace:
{quote}
Exception in thread main com.google.common.collect.ComputationException:
java.lang.ArrayIndexOutOfBoundsException: 3
at
com.google.common.collect.ComputingConcurrentHashMap.compute(ComputingConcurrentHashMap.java:218)
at
com.google.common.collect.ComputingConcurrentHashMap.apply(ComputingConcurrentHashMap.java:100)
at
com.google.common.collect.MapMaker$ComputingMapAdapter.get(MapMaker.java:515)
at
org.jboss.weld.resources.ClassTransformer.loadClass(ClassTransformer.java:183)
at
org.jboss.weld.introspector.jlr.WeldClassImpl.init(WeldClassImpl.java:128)
at
org.jboss.weld.introspector.jlr.WeldClassImpl.of(WeldClassImpl.java:98)
at
org.jboss.weld.resources.ClassTransformer$TransformTypeToWeldClass.apply(ClassTransformer.java:54)
at
org.jboss.weld.resources.ClassTransformer$TransformTypeToWeldClass.apply(ClassTransformer.java:42)
at
com.google.common.collect.ComputingConcurrentHashMap.compute(ComputingConcurrentHashMap.java:206)
at
com.google.common.collect.ComputingConcurrentHashMap.apply(ComputingConcurrentHashMap.java:100)
at
com.google.common.collect.MapMaker$ComputingMapAdapter.get(MapMaker.java:515)
at
org.jboss.weld.resources.ClassTransformer.loadClass(ClassTransformer.java:183)
at
org.jboss.weld.introspector.jlr.WeldClassImpl.init(WeldClassImpl.java:128)
at
org.jboss.weld.introspector.jlr.WeldClassImpl.of(WeldClassImpl.java:98)
at
org.jboss.weld.resources.ClassTransformer$TransformTypeToWeldClass.apply(ClassTransformer.java:54)
at
org.jboss.weld.resources.ClassTransformer$TransformTypeToWeldClass.apply(ClassTransformer.java:42)
at
com.google.common.collect.ComputingConcurrentHashMap.compute(ComputingConcurrentHashMap.java:206)
at
com.google.common.collect.ComputingConcurrentHashMap.apply(ComputingConcurrentHashMap.java:100)
at
com.google.common.collect.MapMaker$ComputingMapAdapter.get(MapMaker.java:515)
at
org.jboss.weld.resources.ClassTransformer.loadClass(ClassTransformer.java:183)
at
org.jboss.weld.bootstrap.BeanDeployer.addClass(BeanDeployer.java:95)
at
org.jboss.weld.bootstrap.BeanDeployer.addClasses(BeanDeployer.java:134)
at
org.jboss.weld.bootstrap.BeanDeployment.createBeans(BeanDeployment.java:191)
at
org.jboss.weld.bootstrap.WeldBootstrap.deployBeans(WeldBootstrap.java:368)
at org.jboss.weld.environment.se.Weld.initialize(Weld.java:92)
at org.jboss.weld.environment.se.StartMain.go(StartMain.java:46)
at org.jboss.weld.environment.se.StartMain.main(StartMain.java:59)
Caused by: java.lang.ArrayIndexOutOfBoundsException: 3
at
org.jboss.weld.introspector.jlr.WeldConstructorImpl.init(WeldConstructorImpl.java:113)
at
org.jboss.weld.introspector.jlr.WeldConstructorImpl.of(WeldConstructorImpl.java:70)
at
org.jboss.weld.introspector.jlr.WeldClassImpl.init(WeldClassImpl.java:210)
at
org.jboss.weld.introspector.jlr.WeldClassImpl.of(WeldClassImpl.java:98)
at
org.jboss.weld.resources.ClassTransformer$TransformTypeToWeldClass.apply(ClassTransformer.java:54)
at
org.jboss.weld.resources.ClassTransformer$TransformTypeToWeldClass.apply(ClassTransformer.java:42)
at
com.google.common.collect.ComputingConcurrentHashMap.compute(ComputingConcurrentHashMap.java:206)
{quote}
When I try to run this project in IntelliJ IDEA it works fine with such exec
command:
{quote}
/home/gross/soft/jdk1.7.0_02/bin/java -Didea.launcher.port=7537
[weld-issues] [JBoss JIRA] (WELD-1007) Weld SE startup fails.
[
https://issues.jboss.org/browse/WELD-1007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12672832#comment-12672832
]
Ales Justin commented on WELD-1007:
---
Doesn't 7.1.0.Final already use 10.0.1?
* https://github.com/jbossas/jboss-as/blob/master/pom.xml
I'll try to put together a small example.
That would be helpful, thanks.
Weld SE startup fails.
--
Key: WELD-1007
URL: https://issues.jboss.org/browse/WELD-1007
Project: Weld
Issue Type: Bug
Components: Java SE Support
Affects Versions: 1.1.1.Final, 1.1.2.Final, 1.1.3.Final
Environment: Arch Linux, Linux kernel 3.0.7
java version 1.7.0_02-ea
Java(TM) SE Runtime Environment (build 1.7.0_02-ea-b11)
Java HotSpot(TM) Server VM (build 22.0-b08, mixed mode)
java version 1.6.0_26
Java(TM) SE Runtime Environment (build 1.6.0_26-b03)
Java HotSpot(TM) 64-Bit Server VM (build 20.1-b02, mixed mode)
Reporter: Konstantin Gribov
Attachments: weld-se-test.tar.gz
I use {{org.jboss.weld.environment.se.StartMain}} to bootstrap weld se
environment. Project is compiled and packaged by maven. When starting
assembly it fails with such stacktrace:
{quote}
Exception in thread main com.google.common.collect.ComputationException:
java.lang.ArrayIndexOutOfBoundsException: 3
at
com.google.common.collect.ComputingConcurrentHashMap.compute(ComputingConcurrentHashMap.java:218)
at
com.google.common.collect.ComputingConcurrentHashMap.apply(ComputingConcurrentHashMap.java:100)
at
com.google.common.collect.MapMaker$ComputingMapAdapter.get(MapMaker.java:515)
at
org.jboss.weld.resources.ClassTransformer.loadClass(ClassTransformer.java:183)
at
org.jboss.weld.introspector.jlr.WeldClassImpl.init(WeldClassImpl.java:128)
at
org.jboss.weld.introspector.jlr.WeldClassImpl.of(WeldClassImpl.java:98)
at
org.jboss.weld.resources.ClassTransformer$TransformTypeToWeldClass.apply(ClassTransformer.java:54)
at
org.jboss.weld.resources.ClassTransformer$TransformTypeToWeldClass.apply(ClassTransformer.java:42)
at
com.google.common.collect.ComputingConcurrentHashMap.compute(ComputingConcurrentHashMap.java:206)
at
com.google.common.collect.ComputingConcurrentHashMap.apply(ComputingConcurrentHashMap.java:100)
at
com.google.common.collect.MapMaker$ComputingMapAdapter.get(MapMaker.java:515)
at
org.jboss.weld.resources.ClassTransformer.loadClass(ClassTransformer.java:183)
at
org.jboss.weld.introspector.jlr.WeldClassImpl.init(WeldClassImpl.java:128)
at
org.jboss.weld.introspector.jlr.WeldClassImpl.of(WeldClassImpl.java:98)
at
org.jboss.weld.resources.ClassTransformer$TransformTypeToWeldClass.apply(ClassTransformer.java:54)
at
org.jboss.weld.resources.ClassTransformer$TransformTypeToWeldClass.apply(ClassTransformer.java:42)
at
com.google.common.collect.ComputingConcurrentHashMap.compute(ComputingConcurrentHashMap.java:206)
at
com.google.common.collect.ComputingConcurrentHashMap.apply(ComputingConcurrentHashMap.java:100)
at
com.google.common.collect.MapMaker$ComputingMapAdapter.get(MapMaker.java:515)
at
org.jboss.weld.resources.ClassTransformer.loadClass(ClassTransformer.java:183)
at
org.jboss.weld.bootstrap.BeanDeployer.addClass(BeanDeployer.java:95)
at
org.jboss.weld.bootstrap.BeanDeployer.addClasses(BeanDeployer.java:134)
at
org.jboss.weld.bootstrap.BeanDeployment.createBeans(BeanDeployment.java:191)
at
org.jboss.weld.bootstrap.WeldBootstrap.deployBeans(WeldBootstrap.java:368)
at org.jboss.weld.environment.se.Weld.initialize(Weld.java:92)
at org.jboss.weld.environment.se.StartMain.go(StartMain.java:46)
at org.jboss.weld.environment.se.StartMain.main(StartMain.java:59)
Caused by: java.lang.ArrayIndexOutOfBoundsException: 3
at
org.jboss.weld.introspector.jlr.WeldConstructorImpl.init(WeldConstructorImpl.java:113)
at
org.jboss.weld.introspector.jlr.WeldConstructorImpl.of(WeldConstructorImpl.java:70)
at
org.jboss.weld.introspector.jlr.WeldClassImpl.init(WeldClassImpl.java:210)
at
org.jboss.weld.introspector.jlr.WeldClassImpl.of(WeldClassImpl.java:98)
at
org.jboss.weld.resources.ClassTransformer$TransformTypeToWeldClass.apply(ClassTransformer.java:54)
at
org.jboss.weld.resources.ClassTransformer$TransformTypeToWeldClass.apply(ClassTransformer.java:42)
at
com.google.common.collect.ComputingConcurrentHashMap.compute(ComputingConcurrentHashMap.java:206)
{quote}
When I try to run this project in IntelliJ IDEA it works fine with such exec
command:
{quote}
/home/gross/soft/jdk1.7.0_02/bin/java -Didea.launcher.port=7537
[weld-issues] [JBoss JIRA] (WELD-999) Interceptor binding transitivity broken
[ https://issues.jboss.org/browse/WELD-999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12672838#comment-12672838 ] Marius Bogoevici commented on WELD-999: --- AFAICT the current implementation is wrong and resolveInterceptors should take into account the transitive closure of the interceptor binding set passed as an argument. Interceptor binding transitivity broken --- Key: WELD-999 URL: https://issues.jboss.org/browse/WELD-999 Project: Weld Issue Type: Bug Components: Interceptors and Decorators Affects Versions: 1.1.2.Final Reporter: Jozef Hartinger Assignee: Marko Lukša Fix For: 1.2.0.Beta1 See org.jboss.weld.tests.interceptors.binding.transitivity.InterceptorBindingTransitivityTest -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-666) Write tests for WeldServletBeanManagerProvider
[ https://issues.jboss.org/browse/WELD-666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ales Justin resolved WELD-666. -- Assignee: (was: Aslak Knutsen) Fix Version/s: (was: 1.2.0.Beta1) Resolution: Out of Date Handled by Seam3 and now DeltaSpike. Write tests for WeldServletBeanManagerProvider -- Key: WELD-666 URL: https://issues.jboss.org/browse/WELD-666 Project: Weld Issue Type: Bug Components: Servlet Container Support Reporter: Pete Muir -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-1049) BeanManager.createInjectionTarget() does not support interception
[ https://issues.jboss.org/browse/WELD-1049?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ales Justin reassigned WELD-1049: - Assignee: (was: Ales Justin) BeanManager.createInjectionTarget() does not support interception - Key: WELD-1049 URL: https://issues.jboss.org/browse/WELD-1049 Project: Weld Issue Type: Bug Components: Interceptors and Decorators Affects Versions: 1.1.5.Final Reporter: Jozef Hartinger Fix For: 1.2.0.Beta1, 2.0.0.Alpha2 SimpleInjectionTarget does not have support for interceptors nor decorators. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-760) Duplicate interceptor: More than one jar
[ https://issues.jboss.org/browse/WELD-760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ales Justin reassigned WELD-760: Assignee: Marko Lukša Duplicate interceptor: More than one jar Key: WELD-760 URL: https://issues.jboss.org/browse/WELD-760 Project: Weld Issue Type: Bug Components: Interceptors and Decorators, Weld SPI Affects Versions: 1.1.0.Beta2 Environment: JBoss 6 M5 Reporter: Robson Saraiva Ximenes Assignee: Marko Lukša Fix For: 1.2.0.Beta1 Like discribed in forum i have the same problem but one diference; I have several jar... when i the interceptor should intercept an class from a x.jar and this class extends another from y.jar cause the problem -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-1056) Weld-servlet brings transitive dependency on weld-build-config
[
https://issues.jboss.org/browse/WELD-1056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12672998#comment-12672998
]
Lukáš Fryč commented on WELD-1056:
--
Nothing have changed in the plugin configuration.
I have checked the Maven output during build, no formal verification done
though.
If the checkstyle plugin won't find the configuration on
{{weld-checkstyle/checkstyle.xml}}, it will fail (from my experience).
Weld-servlet brings transitive dependency on weld-build-config
--
Key: WELD-1056
URL: https://issues.jboss.org/browse/WELD-1056
Project: Weld
Issue Type: Bug
Affects Versions: 1.1.4.Final
Reporter: Lukáš Fryč
Assignee: Ales Justin
Fix For: 1.2.0.Beta1
This transitive dependency comes from {{weld-core-parent}}:
https://github.com/weld/core/blob/e20e1b9b7f5d22e2bff3d3f1d2812b1ff8f99b42/pom.xml#L501
Since this config currently contains only checkstyle definitions,
I suggest to remove this project dependency and use only
{{maven-checkstyle-plugin}} dependency (which is currently configured too):
https://github.com/weld/core/blob/e20e1b9b7f5d22e2bff3d3f1d2812b1ff8f99b42/pom.xml#L539
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
___
weld-issues mailing list
weld-issues@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/weld-issues
