November 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-2576) SimpleApplicationClientTestCase should not use java on path

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-2576?page=com.atlassian.jira.plugin.... ] Tomaz Cerar deleted WFLY-2576: ------------------------------ > SimpleApplicationClientTestCase should not use java on path > ----------------------------------------------------------- > > Key: WFLY-2576 > URL: https://issues.jboss.org/browse/WFLY-2576 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Tomaz Cerar > Assignee: Stuart Douglas > Priority: Critical > > Test should use java that is set by JAVA_HOME and not rely on java being set avalible on path. > This way we can properly run testsuite against diffrent JDKs > currently this is the result: > {noformat} > java.io.IOException: Cannot run program "java": error=2, No such file or directory > at java.lang.UNIXProcess.forkAndExec(Native Method) > at java.lang.UNIXProcess.<init>(UNIXProcess.java:187) > at java.lang.ProcessImpl.start(ProcessImpl.java:134) > at java.lang.ProcessBuilder.start(ProcessBuilder.java:1023) > at java.lang.Runtime.exec(Runtime.java:620) > at java.lang.Runtime.exec(Runtime.java:450) > at java.lang.Runtime.exec(Runtime.java:347) > at org.jboss.as.test.integration.ee.appclient.util.AppClientWrapper.init(AppClientWrapper.java:152) > at org.jboss.as.test.integration.ee.appclient.util.AppClientWrapper.<init>(AppClientWrapper.java:78) > at org.jboss.as.test.integration.ee.appclient.basic.SimpleApplicationClientTestCase.descriptorBasedAppClientTest(SimpleApplicationClientTestCase.java:128) > {noformat} -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2574) CliArgumentsTestCase should not rely on java beeing on path

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-2574?page=com.atlassian.jira.plugin.... ] Tomaz Cerar commented on WFLY-2574: ----------------------------------- Same applies also to CommandsExitCodeTestCase, FileArgumentTestCase & FileWithPropertiesTestCase > CliArgumentsTestCase should not rely on java beeing on path > ------------------------------------------------------------ > > Key: WFLY-2574 > URL: https://issues.jboss.org/browse/WFLY-2574 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: CLI, Test Suite > Affects Versions: 8.0.0.Beta1 > Reporter: Tomaz Cerar > Assignee: Alexey Loubyansky > Priority: Critical > > If there is no java on path tests fail with > {noformat} > java.lang.AssertionError: Failed to start CLI process: Cannot run program "java": error=2, No such file or directory > at org.junit.Assert.fail(Assert.java:88) > at org.jboss.as.test.integration.management.cli.CliScriptTestBase.execute(CliScriptTestBase.java:108) > at org.jboss.as.test.integration.management.cli.CliScriptTestBase.execute(CliScriptTestBase.java:73) > at org.jboss.as.test.integration.management.cli.CliScriptTestBase.execute(CliScriptTestBase.java:69) > at org.jboss.as.test.integration.management.cli.CliArgumentsTestCase.testConnectArgument(CliArgumentsTestCase.java:103) > {noformat} > Test should use JAVA_HOME env variable or java that ran "current" process > without this fix it is really hard to properly test build with different JDKs as test will always use default java for executing commands instead of build provided/configured one -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2576) SimpleApplicationClientTestCase should not use java on path

by Tomaz Cerar (JIRA)

Tomaz Cerar created WFLY-2576: --------------------------------- Summary: SimpleApplicationClientTestCase should not use java on path Key: WFLY-2576 URL: https://issues.jboss.org/browse/WFLY-2576 Project: WildFly Issue Type: Bug Security Level: Public (Everyone can see) Components: Application Client Affects Versions: 8.0.0.Beta1 Reporter: Tomaz Cerar Assignee: Stuart Douglas Priority: Critical Test should use java that is set by JAVA_HOME and not rely on java being set avalible on path. This way we can properly run testsuite against diffrent JDKs currently this is the result: {noformat} java.io.IOException: Cannot run program "java": error=2, No such file or directory at java.lang.UNIXProcess.forkAndExec(Native Method) at java.lang.UNIXProcess.<init>(UNIXProcess.java:187) at java.lang.ProcessImpl.start(ProcessImpl.java:134) at java.lang.ProcessBuilder.start(ProcessBuilder.java:1023) at java.lang.Runtime.exec(Runtime.java:620) at java.lang.Runtime.exec(Runtime.java:450) at java.lang.Runtime.exec(Runtime.java:347) at org.jboss.as.test.integration.ee.appclient.util.AppClientWrapper.init(AppClientWrapper.java:152) at org.jboss.as.test.integration.ee.appclient.util.AppClientWrapper.<init>(AppClientWrapper.java:78) at org.jboss.as.test.integration.ee.appclient.basic.SimpleApplicationClientTestCase.descriptorBasedAppClientTest(SimpleApplicationClientTestCase.java:128) {noformat} -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2548) Automatically add org.wildfly.clustering.api/singleton modules to deployments

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/WFLY-2548?page=com.atlassian.jira.plugin.... ] Paul Ferraro commented on WFLY-2548: ------------------------------------ I've created a separate org.wildfly.clustering.web.api module to contain the @Immutable annotation. This module should be added to the classpath of web deployments, regardless of whether the clustering modules are present. I've located the DUP that adds the org.wildfly.clustering.api and org.wildfly.clustering.singleton modules to the deployment classpath in the jgroups subsystem - since these are only relevant if this subsystem is installed. > Automatically add org.wildfly.clustering.api/singleton modules to deployments > ----------------------------------------------------------------------------- > > Key: WFLY-2548 > URL: https://issues.jboss.org/browse/WFLY-2548 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Clustering > Affects Versions: 8.0.0.Beta1 > Reporter: Radoslav Husar > Assignee: Paul Ferraro > Fix For: 8.0.0.CR1 > > > Since @Immutable annotated classes will silently fail and the object will be considered mutable if the user forgets/doesn't add the dependency himself/herself. -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2575) SimpleApplicationClientTestCase should not use java on path

by Tomaz Cerar (JIRA)

Tomaz Cerar created WFLY-2575: --------------------------------- Summary: SimpleApplicationClientTestCase should not use java on path Key: WFLY-2575 URL: https://issues.jboss.org/browse/WFLY-2575 Project: WildFly Issue Type: Bug Security Level: Public (Everyone can see) Components: Application Client Affects Versions: 8.0.0.Beta1 Reporter: Tomaz Cerar Assignee: Stuart Douglas Priority: Critical Test should use java that is set by JAVA_HOME and not rely on java being set avalible on path. This way we can properly run testsuite against diffrent JDKs currently this is the result: {noformat} java.io.IOException: Cannot run program "java": error=2, No such file or directory at java.lang.UNIXProcess.forkAndExec(Native Method) at java.lang.UNIXProcess.<init>(UNIXProcess.java:187) at java.lang.ProcessImpl.start(ProcessImpl.java:134) at java.lang.ProcessBuilder.start(ProcessBuilder.java:1023) at java.lang.Runtime.exec(Runtime.java:620) at java.lang.Runtime.exec(Runtime.java:450) at java.lang.Runtime.exec(Runtime.java:347) at org.jboss.as.test.integration.ee.appclient.util.AppClientWrapper.init(AppClientWrapper.java:152) at org.jboss.as.test.integration.ee.appclient.util.AppClientWrapper.<init>(AppClientWrapper.java:78) at org.jboss.as.test.integration.ee.appclient.basic.SimpleApplicationClientTestCase.descriptorBasedAppClientTest(SimpleApplicationClientTestCase.java:128) {noformat} -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-766) Add a support for JAAS Security Domain to UsernamePasswordLoginModule

by Ivo Studensky (JIRA)

[ https://issues.jboss.org/browse/SECURITY-766?page=com.atlassian.jira.plug... ] Ivo Studensky resolved SECURITY-766. ------------------------------------ Resolution: Won't Fix The relevant RFE (i.e. EAP5-19) has been rejected. > Add a support for JAAS Security Domain to UsernamePasswordLoginModule > --------------------------------------------------------------------- > > Key: SECURITY-766 > URL: https://issues.jboss.org/browse/SECURITY-766 > Project: PicketBox > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: JBossSX > Affects Versions: JBossSecurity_2.0.5.Final > Reporter: Ivo Studensky > Assignee: Ivo Studensky > Fix For: JBossSecurity_2.0.6.Final > > Attachments: SECURITY-766.patch > > > This is a request for a support of JAAS Security Domain on UsernamePasswordLoginModule as per EAP5-19. It will enable the use of encrypted passwords on the server side, for example in a DatabaseServerLoginModule. > The relevant patch is attached to this jira. -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-766) Add a support for JAAS Security Domain to UsernamePasswordLoginModule

by Ivo Studensky (JIRA)

[ https://issues.jboss.org/browse/SECURITY-766?page=com.atlassian.jira.plug... ] Ivo Studensky updated SECURITY-766: ----------------------------------- Attachment: SECURITY-766.patch > Add a support for JAAS Security Domain to UsernamePasswordLoginModule > --------------------------------------------------------------------- > > Key: SECURITY-766 > URL: https://issues.jboss.org/browse/SECURITY-766 > Project: PicketBox > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: JBossSX > Affects Versions: JBossSecurity_2.0.5.Final > Reporter: Ivo Studensky > Assignee: Ivo Studensky > Fix For: JBossSecurity_2.0.6.Final > > Attachments: SECURITY-766.patch > > > This is a request for a support of JAAS Security Domain on UsernamePasswordLoginModule as per EAP5-19. It will enable the use of encrypted passwords on the server side, for example in a DatabaseServerLoginModule. > The relevant patch is attached to this jira. -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-766) Add a support for JAAS Security Domain to UsernamePasswordLoginModule

by Ivo Studensky (JIRA)

[ https://issues.jboss.org/browse/SECURITY-766?page=com.atlassian.jira.plug... ] Ivo Studensky reassigned SECURITY-766: -------------------------------------- Assignee: Ivo Studensky (was: Anil Saldhana) > Add a support for JAAS Security Domain to UsernamePasswordLoginModule > --------------------------------------------------------------------- > > Key: SECURITY-766 > URL: https://issues.jboss.org/browse/SECURITY-766 > Project: PicketBox > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: JBossSX > Affects Versions: JBossSecurity_2.0.5.Final > Reporter: Ivo Studensky > Assignee: Ivo Studensky > Fix For: JBossSecurity_2.0.6.Final > > > This is a request for a support of JAAS Security Domain on UsernamePasswordLoginModule as per EAP5-10. It will enable the use of encrypted passwords with shutdown script, for example. > The relevant patch is attached to this jira. -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-766) Add a support for JAAS Security Domain to UsernamePasswordLoginModule

by Ivo Studensky (JIRA)

[ https://issues.jboss.org/browse/SECURITY-766?page=com.atlassian.jira.plug... ] Ivo Studensky updated SECURITY-766: ----------------------------------- Description: This is a request for a support of JAAS Security Domain on UsernamePasswordLoginModule as per EAP5-19. It will enable the use of encrypted passwords on the server side, for example in a DatabaseServerLoginModule. The relevant patch is attached to this jira. was: This is a request for a support of JAAS Security Domain on UsernamePasswordLoginModule as per EAP5-10. It will enable the use of encrypted passwords with shutdown script, for example. The relevant patch is attached to this jira. > Add a support for JAAS Security Domain to UsernamePasswordLoginModule > --------------------------------------------------------------------- > > Key: SECURITY-766 > URL: https://issues.jboss.org/browse/SECURITY-766 > Project: PicketBox > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: JBossSX > Affects Versions: JBossSecurity_2.0.5.Final > Reporter: Ivo Studensky > Assignee: Ivo Studensky > Fix For: JBossSecurity_2.0.6.Final > > > This is a request for a support of JAAS Security Domain on UsernamePasswordLoginModule as per EAP5-19. It will enable the use of encrypted passwords on the server side, for example in a DatabaseServerLoginModule. > The relevant patch is attached to this jira. -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-766) Add a support for JAAS Security Domain to UsernamePasswordLoginModule

by Ivo Studensky (JIRA)

[ https://issues.jboss.org/browse/SECURITY-766?page=com.atlassian.jira.plug... ] Ivo Studensky updated SECURITY-766: ----------------------------------- Attachment: (was: SECURITY-766.patch) > Add a support for JAAS Security Domain to UsernamePasswordLoginModule > --------------------------------------------------------------------- > > Key: SECURITY-766 > URL: https://issues.jboss.org/browse/SECURITY-766 > Project: PicketBox > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: JBossSX > Affects Versions: JBossSecurity_2.0.5.Final > Reporter: Ivo Studensky > Assignee: Ivo Studensky > Fix For: JBossSecurity_2.0.6.Final > > > This is a request for a support of JAAS Security Domain on UsernamePasswordLoginModule as per EAP5-19. It will enable the use of encrypted passwords on the server side, for example in a DatabaseServerLoginModule. > The relevant patch is attached to this jira. -- 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

12 years, 8 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira November 2013