May 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-4574) Upgrade Mojarra to 2.2.11

by Cody Lerum (JIRA)

Cody Lerum created WFLY-4574: -------------------------------- Summary: Upgrade Mojarra to 2.2.11 Key: WFLY-4574 URL: https://issues.jboss.org/browse/WFLY-4574 Project: WildFly Issue Type: Component Upgrade Components: JSF Reporter: Cody Lerum Assignee: Farah Juma Fix For: 9.0.0.CR1 Mojarra 2.2 now appears to be on a 4-6 month release cycle and 2.2.11 is due for release on May 5th. https://java.net/jira/browse/JAVASERVERFACES/fixforversion/17193/?selecte... It would be great if we could get this updated before 9.1.0.Final. https://java.net/jira/browse/JAVASERVERFACES-3848 for example would be nice to pick up. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 12 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4571) Merge the wildfly BOMs into a single BOM

by Paul Gier (JIRA)

[ https://issues.jboss.org/browse/WFLY-4571?page=com.atlassian.jira.plugin.... ] Paul Gier commented on WFLY-4571: --------------------------------- I updated the PR to retain the separate tools BOM. For both the hibernate3 and tools BOM, they now inherit from the main bom so they also include all of it's dependency management. I think it's a bit better this way so that you normally don't need to import more than one BOM. > Merge the wildfly BOMs into a single BOM > ---------------------------------------- > > Key: WFLY-4571 > URL: https://issues.jboss.org/browse/WFLY-4571 > Project: WildFly > Issue Type: Enhancement > Reporter: Paul Gier > Assignee: Paul Gier > > We had some discussion on the jbossdeveloper list [1] about merging the current wildfly/eap boms into a single one instead of a separate bom for each use case. > The only problematic BOM might be the hibernate3 bom because this includes dependencies which conflict with the hibernate 4 bom. So the hibernate 3 bom will probably need to remain separate. > [1]http://lists.jboss.org/pipermail/jbossdeveloper/2015-April/000347.html -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 12 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-670) Node type is not complete at index 0 after tab completion on an empty resource

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFCORE-670?page=com.atlassian.jira.plugin... ] James Perkins commented on WFCORE-670: -------------------------------------- I added a blocker flag, but IMO it just needs to be fixed by 1.0.0.Final. > Node type is not complete at index 0 after tab completion on an empty resource > ------------------------------------------------------------------------------ > > Key: WFCORE-670 > URL: https://issues.jboss.org/browse/WFCORE-670 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Reporter: James Perkins > Assignee: Alexey Loubyansky > Priority: Blocker > Fix For: 1.0.0.CR1 > > > Using something like {{/system-property=<TAB>}} with no system properties set results in future commands no longer working. > {code:title=Example Output} > [standalone@localhost:9990 /] /system-property= > The operation name is missing or the format of the operation request is wrong. > [standalone@localhost:9990 /] > [standalone@localhost:9990 /] exit > Node type is not complete at index 0 > [standalone@localhost:9990 /] > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 12 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-670) Node type is not complete at index 0 after tab completion on an empty resource

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFCORE-670?page=com.atlassian.jira.plugin... ] James Perkins updated WFCORE-670: --------------------------------- Priority: Blocker (was: Major) > Node type is not complete at index 0 after tab completion on an empty resource > ------------------------------------------------------------------------------ > > Key: WFCORE-670 > URL: https://issues.jboss.org/browse/WFCORE-670 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Reporter: James Perkins > Assignee: Alexey Loubyansky > Priority: Blocker > Fix For: 1.0.0.CR1 > > > Using something like {{/system-property=<TAB>}} with no system properties set results in future commands no longer working. > {code:title=Example Output} > [standalone@localhost:9990 /] /system-property= > The operation name is missing or the format of the operation request is wrong. > [standalone@localhost:9990 /] > [standalone@localhost:9990 /] exit > Node type is not complete at index 0 > [standalone@localhost:9990 /] > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 12 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-670) Node type is not complete at index 0 after tab completion on an empty resource

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFCORE-670?page=com.atlassian.jira.plugin... ] James Perkins updated WFCORE-670: --------------------------------- Fix Version/s: 1.0.0.CR1 > Node type is not complete at index 0 after tab completion on an empty resource > ------------------------------------------------------------------------------ > > Key: WFCORE-670 > URL: https://issues.jboss.org/browse/WFCORE-670 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Reporter: James Perkins > Assignee: Alexey Loubyansky > Priority: Blocker > Fix For: 1.0.0.CR1 > > > Using something like {{/system-property=<TAB>}} with no system properties set results in future commands no longer working. > {code:title=Example Output} > [standalone@localhost:9990 /] /system-property= > The operation name is missing or the format of the operation request is wrong. > [standalone@localhost:9990 /] > [standalone@localhost:9990 /] exit > Node type is not complete at index 0 > [standalone@localhost:9990 /] > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 12 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-670) Node type is not complete at index 0 after tab completion on an empty resource

by James Perkins (JIRA)

James Perkins created WFCORE-670: ------------------------------------ Summary: Node type is not complete at index 0 after tab completion on an empty resource Key: WFCORE-670 URL: https://issues.jboss.org/browse/WFCORE-670 Project: WildFly Core Issue Type: Bug Components: CLI Reporter: James Perkins Assignee: Alexey Loubyansky Using something like {{/system-property=<TAB>}} with no system properties set results in future commands no longer working. {code:title=Example Output} [standalone@localhost:9990 /] /system-property= The operation name is missing or the format of the operation request is wrong. [standalone@localhost:9990 /] [standalone@localhost:9990 /] exit Node type is not complete at index 0 [standalone@localhost:9990 /] {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 12 months

1
0
0 / 0

[JBoss JIRA] (WFLY-156) Unable to start jboss AS on windows if installed on path containig non-ascii characters

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-156?page=com.atlassian.jira.plugin.s... ] Tomaz Cerar closed WFLY-156. ---------------------------- Resolution: Deferred Once https://bugs.openjdk.java.net/browse/JDK-4488646 is fixed this should work with new powershell scripts that are part of WildFly 9. > Unable to start jboss AS on windows if installed on path containig non-ascii characters > ---------------------------------------------------------------------------------------- > > Key: WFLY-156 > URL: https://issues.jboss.org/browse/WFLY-156 > Project: WildFly > Issue Type: Bug > Components: Server > Environment: windows 2008 x64 > Reporter: Ales Kolenc > Assignee: Tomaz Cerar > Priority: Critical > Fix For: Awaiting Volunteers > > > 1.) Install jboss into a folder containing non-ascii characters. (i.e. "C:\Testチ"). > 2.) run standalone.bat > C:\Test?\jboss-as-7.1.1.Final\bin>set JAVA_HOME=C:\Program Files\Java\jre7 > C:\Test?\jboss-as-7.1.1.Final\bin>standalone.bat > Calling "C:\Test?\jboss-as-7.1.1.Final\bin\standalone.conf.bat" > =============================================================================== > JBoss Bootstrap Environment > JBOSS_HOME: C:\Test?\jboss-as-7.1.1.Final > JAVA: C:\Program Files\Java\jre7\bin\java > JAVA_OPTS: -XX:+TieredCompilation -Dprogram.name=standalone.bat -Xms64M -Xmx512M -XX:MaxPermSize=256M -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djava.net.preferIPv4Stack=true -Dorg.jboss.resolver.warning=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djb > oss.server.default.config=standalone.xml > =============================================================================== > Error: Unable to access jarfile C:\Test?\jboss-as-7.1.1.Final\jboss-modules.jar > Press any key to continue . . . > C:\Test?\jboss-as-7.1.1.Final\bin> > 3.) pleas note that: "Testチ" used in path -> 'チ' does not bellong to system locale code page. E.g.: char 'チ' is in CP 932, system locale code page used 437/1252,.. > 4.) i would also like to add that jboss does not start if it installed in "normal" folder, but JBOSS_CONFIG_DIR && JBOSS_LOG_DIR are set to folder with non-ascii characters: > c:\test\jboss-as-7.1.1.Final\bin>set JBOSS_LOG_DIR=c:\Test? > c:\test\jboss-as-7.1.1.Final\bin>set JBOSS_CONFIG_DIR=c:\Test?\configuration > c:\test\jboss-as-7.1.1.Final\bin>dir %JBOSS_CONFIG_DIR% > Volume in drive C has no label. > Volume Serial Number is 2C2F-FA6F > Directory of c:\Test?\configuration > 01/04/2013 02:34 AM <DIR> . > 01/04/2013 02:34 AM <DIR> .. > 01/04/2013 01:42 AM 634 application-roles.properties > 01/04/2013 01:42 AM 812 application-users.properties > 01/04/2013 01:42 AM 2,042 logging.properties > 01/04/2013 01:42 AM 836 mgmt-users.properties > 01/04/2013 01:42 AM 27,024 standalone-full-ha.xml > 01/04/2013 01:42 AM 20,794 standalone-full.xml > 01/04/2013 01:42 AM 20,358 standalone-ha.xml > 01/04/2013 01:42 AM 15,372 standalone.xml > 01/04/2013 02:34 AM <DIR> standalone_xml_history > 8 File(s) 87,872 bytes > 3 Dir(s) 20,185,866,240 bytes free > c:\test\jboss-as-7.1.1.Final\bin>standalone.bat -Djboss.server.config.dir=%JBOSS_CONFIG_DIR% > Calling "c:\test\jboss-as-7.1.1.Final\bin\standalone.conf.bat" > =============================================================================== > JBoss Bootstrap Environment > JBOSS_HOME: c:\test\jboss-as-7.1.1.Final > JAVA: C:\Program Files\Java\jre7\bin\java > JAVA_OPTS: -XX:+TieredCompilation -Dprogram.name=standalone.bat -Xms64M -Xmx512M -XX:MaxPermSize=256M -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djava.net.preferIPv4Stack=true -Dorg.jboss.resolver.warning=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djb > oss.server.default.config=standalone.xml > =============================================================================== > Unable to read the logging configuration from 'file:c:\Test?\configuration/logging.properties' (java.io.FileNotFoundException: c:\Test?\configuration\logging.properties (The filename, directory name, or volume label syntax is incorrect)) > java.lang.IllegalStateException: JBAS018701: Configuration directory does not exist: c:\Test?\configuration > at org.jboss.as.server.ServerEnvironment.<init>(ServerEnvironment.java:371) > at org.jboss.as.server.Main.determineEnvironment(Main.java:242) > at org.jboss.as.server.Main.main(Main.java:83) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) > at java.lang.reflect.Method.invoke(Unknown Source) > at org.jboss.modules.Module.run(Module.java:260) > at org.jboss.modules.Main.main(Main.java:291) > Press any key to continue . . . > c:\test\jboss-as-7.1.1.Final\bin> -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 12 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 May 2015