October 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-2193) Upgrade javax.json to version 1.0.3

by Shelly McGowan (JIRA)

[ https://issues.jboss.org/browse/WFLY-2193?page=com.atlassian.jira.plugin.... ] Shelly McGowan updated WFLY-2193: --------------------------------- Git Pull Request: https://github.com/wildfly/wildfly/pull/5187 > Upgrade javax.json to version 1.0.3 > ----------------------------------- > > Key: WFLY-2193 > URL: https://issues.jboss.org/browse/WFLY-2193 > Project: WildFly > Issue Type: Feature Request > Reporter: Shelly McGowan > Assignee: Shelly McGowan > Fix For: 8.0.0.CR1 > > > WildFly consumes org.glassfish:javax.json artifacts, version 1.0. This needs to be updated. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2156) Upgrade scannotation to 1.0.3

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFLY-2156?page=com.atlassian.jira.plugin.... ] Stuart Douglas updated WFLY-2156: --------------------------------- Assignee: Weinan Li (was: Stuart Douglas) > Upgrade scannotation to 1.0.3 > ----------------------------- > > Key: WFLY-2156 > URL: https://issues.jboss.org/browse/WFLY-2156 > Project: WildFly > Issue Type: Feature Request > Components: REST > Affects Versions: 8.0.0.Alpha4 > Reporter: Weinan Li > Assignee: Weinan Li > > RESTEasy has a dependency on 1.0.3 of scannotation. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2181) TempFileProviderService creates a static, non-daemon thread pool

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFLY-2181?page=com.atlassian.jira.plugin.... ] Stuart Douglas resolved WFLY-2181. ---------------------------------- Fix Version/s: 8.0.0.Beta1 Resolution: Done > TempFileProviderService creates a static, non-daemon thread pool > ---------------------------------------------------------------- > > Key: WFLY-2181 > URL: https://issues.jboss.org/browse/WFLY-2181 > Project: WildFly > Issue Type: Bug > Components: Server > Affects Versions: 8.0.0.Alpha4 > Reporter: Stuart Douglas > Assignee: Stuart Douglas > Fix For: 8.0.0.Beta1 > > > This can prevent the server from shutting down -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1913) CLI 'module add' command fail if a drive letter is specified in its resource path

by Ivo Studensky (JIRA)

[ https://issues.jboss.org/browse/WFLY-1913?page=com.atlassian.jira.plugin.... ] Ivo Studensky commented on WFLY-1913: ------------------------------------- Ah, nevermind. It needs a module add command included in the deploy.scr script. I will enhance the test case accordingly and fix the issue. > CLI 'module add' command fail if a drive letter is specified in its resource path > --------------------------------------------------------------------------------- > > Key: WFLY-1913 > URL: https://issues.jboss.org/browse/WFLY-1913 > Project: WildFly > Issue Type: Bug > Components: CLI > Affects Versions: 8.0.0.Alpha4 > Reporter: Ivo Studensky > Assignee: Ivo Studensky > Fix For: 8.0.0.Beta1 > > Attachments: install-mojarra-2.0.0.cli > > > If a drive letter is specified in the resource path the module add command fails on MS Windows. It cannot locate such a resource because of doubled drive letter in the translated path. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1913) CLI 'module add' command fail if a drive letter is specified in its resource path

by Ivo Studensky (JIRA)

[ https://issues.jboss.org/browse/WFLY-1913?page=com.atlassian.jira.plugin.... ] Ivo Studensky commented on WFLY-1913: ------------------------------------- I've hacked up a simple test case for the CLI deployment archive involving a simple war which works as expected. I will continue on this and test it with the archive you attached. https://github.com/istudens/wildfly/commit/411d60fa299484db688ccde747a04b... > CLI 'module add' command fail if a drive letter is specified in its resource path > --------------------------------------------------------------------------------- > > Key: WFLY-1913 > URL: https://issues.jboss.org/browse/WFLY-1913 > Project: WildFly > Issue Type: Bug > Components: CLI > Affects Versions: 8.0.0.Alpha4 > Reporter: Ivo Studensky > Assignee: Ivo Studensky > Fix For: 8.0.0.Beta1 > > Attachments: install-mojarra-2.0.0.cli > > > If a drive letter is specified in the resource path the module add command fails on MS Windows. It cannot locate such a resource because of doubled drive letter in the translated path. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-266) KIE resolving dependend artifacts issue

by Kurt Stam (JIRA)

[ https://issues.jboss.org/browse/DROOLS-266?page=com.atlassian.jira.plugin... ] Kurt Stam commented on DROOLS-266: ---------------------------------- expected output: ------------------------------------------------------ T E S T S ------------------------------------------------------- Running org.overlord.dtgov.dtgovworkflows.KieTest Reading your .m2 repo artifact=org.overlord.dtgov.issue266:dtgov-workflows:jar:2.0.0-SNAPSHOT 0 [main] WARN org.kie.scanner.MavenClassLoaderResolver - Dependency artifact not found for: org.jbpm:jbpm-bpmn2:${jbpm.version} 413 [main] WARN org.kie.scanner.MavenClassLoaderResolver - Dependency artifact not found for: org.jbpm:jbpm-shared-services:${jbpm.version} 753 [main] WARN org.kie.scanner.MavenClassLoaderResolver - Dependency artifact not found for: org.jbpm:jbpm-persistence-jpa:${jbpm.version} 1097 [main] WARN org.kie.scanner.MavenClassLoaderResolver - Dependency artifact not found for: org.jbpm:jbpm-runtime-manager:${jbpm.version} 1416 [main] WARN org.kie.scanner.MavenClassLoaderResolver - Dependency artifact not found for: org.drools:drools-core:${drools.version} 1751 [main] WARN org.kie.scanner.MavenClassLoaderResolver - Dependency artifact not found for: org.drools:drools-compiler:${drools.version} 2108 [main] WARN org.kie.scanner.MavenClassLoaderResolver - Dependency artifact not found for: org.kie:kie-api:${drools.version} 2458 [main] WARN org.kie.scanner.MavenClassLoaderResolver - Dependency artifact not found for: org.jboss.netty:netty:${drools.version} java.lang.NullPointerException at sun.net.util.URLUtil.urlNoFragString(URLUtil.java:47) at sun.misc.URLClassPath.getLoader(URLClassPath.java:321) at sun.misc.URLClassPath.access$000(URLClassPath.java:62) at sun.misc.URLClassPath$1.next(URLClassPath.java:221) at sun.misc.URLClassPath$1.hasMoreElements(URLClassPath.java:232) at java.net.URLClassLoader$3$1.run(URLClassLoader.java:583) at java.net.URLClassLoader$3$1.run(URLClassLoader.java:581) > KIE resolving dependend artifacts issue > --------------------------------------- > > Key: DROOLS-266 > URL: https://issues.jboss.org/browse/DROOLS-266 > Project: Drools > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 6.0.0.CR3 > Reporter: Kurt Stam > Assignee: Mario Fusco > Attachments: kie-load-from-maven-issue.tgz, kie-load-from-maven-issue.tgz > > > This happens when for a dependency the scope is > - set to 'provided' and > - a parameter (in the case ${jbpm.version}) is used in the version field. > So the relevant entry in the pom is: > <dependency> > <groupId>org.drools</groupId> > <artifactId>drools-core</artifactId> > <version>${drools.version}</version> > <scope>provided</scope> > </dependency> > which leads to > 11:15:02,584 WARN Dependency artifact not found for: org.jbpm:jbpm-bpmn2:${jbpm.version} > and then the NPE. I'm guessing the parameter is not being resolved. > 1. it probably should resolve parameters > 2. if a dependency is scoped as 'provided' I think it is supposed to locate it on the classpath and NOT from maven. However I'm not sure this is the way that works in testing anyway. > 3. if the dependency cannot be found it should probably stop and not even proceed rather then warn? > 4. it should be interesting to see why it gets the NPE. > If you change the dependency from 'provided' to 'test' things work fine. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2193) Upgrade javax.json to version 1.0.3

by Shelly McGowan (JIRA)

[ https://issues.jboss.org/browse/WFLY-2193?page=com.atlassian.jira.plugin.... ] Shelly McGowan reassigned WFLY-2193: ------------------------------------ Assignee: Shelly McGowan > Upgrade javax.json to version 1.0.3 > ----------------------------------- > > Key: WFLY-2193 > URL: https://issues.jboss.org/browse/WFLY-2193 > Project: WildFly > Issue Type: Feature Request > Reporter: Shelly McGowan > Assignee: Shelly McGowan > Fix For: 8.0.0.CR1 > > > WildFly consumes org.glassfish:javax.json artifacts, version 1.0. This needs to be updated. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1957) Upgrade Narayana to 5.0.0.M5

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/WFLY-1957?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated WFLY-1957: ----------------------------------- Fix Version/s: 8.0.0.Beta1 (was: 8.0.0.CR1) > Upgrade Narayana to 5.0.0.M5 > ---------------------------- > > Key: WFLY-1957 > URL: https://issues.jboss.org/browse/WFLY-1957 > Project: WildFly > Issue Type: Component Upgrade > Components: Transactions > Reporter: Paul Robinson > Assignee: Paul Robinson > Fix For: 8.0.0.Beta1 > > > In particular, needed for the fix to WFLY-1929. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1957) Upgrade Narayana to 5.0.0.M5

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/WFLY-1957?page=com.atlassian.jira.plugin.... ] Michael Musgrove reassigned WFLY-1957: -------------------------------------- Assignee: Michael Musgrove (was: Paul Robinson) > Upgrade Narayana to 5.0.0.M5 > ---------------------------- > > Key: WFLY-1957 > URL: https://issues.jboss.org/browse/WFLY-1957 > Project: WildFly > Issue Type: Component Upgrade > Components: Transactions > Reporter: Paul Robinson > Assignee: Michael Musgrove > Fix For: 8.0.0.Beta1 > > > In particular, needed for the fix to WFLY-1929. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2193) Upgrade javax.json to version 1.0.3

by Shelly McGowan (JIRA)

Shelly McGowan created WFLY-2193: ------------------------------------ Summary: Upgrade javax.json to version 1.0.3 Key: WFLY-2193 URL: https://issues.jboss.org/browse/WFLY-2193 Project: WildFly Issue Type: Feature Request Reporter: Shelly McGowan Fix For: 8.0.0.CR1 WildFly consumes org.glassfish:javax.json artifacts, version 1.0. This needs to be updated. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 7 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2013