[JBoss JIRA] (WFLY-3733) ChannelInstanceResourceDefinition doesn't expose non-primitive fields and any of @ManagedAttribute methods
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/WFLY-3733?page=com.atlassian.jira.plugin.... ]
Radoslav Husar updated WFLY-3733:
---------------------------------
Fix Version/s: 9.0.0.Beta1
> ChannelInstanceResourceDefinition doesn't expose non-primitive fields and any of @ManagedAttribute methods
> ----------------------------------------------------------------------------------------------------------
>
> Key: WFLY-3733
> URL: https://issues.jboss.org/browse/WFLY-3733
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Clustering
> Affects Versions: 8.1.0.Final
> Reporter: Radoslav Husar
> Assignee: Radoslav Husar
> Priority: Minor
> Fix For: 9.0.0.Beta1
>
>
> It seems to me that org.jboss.as.clustering.jgroups.subsystem.ChannelInstanceResourceDefinition#getProtocolMetricResourceDefinition
> doesnt expose ManagedAttributes that would have to be registred as strings
> org/jboss/as/clustering/jgroups/subsystem/ChannelInstanceResourceDefinition.java:213
> and doesnt expose any of the annotated methods
> org/jboss/as/clustering/jgroups/subsystem/ChannelInstanceResourceDefinition.java:208
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months
[JBoss JIRA] (WFLY-3733) ChannelInstanceResourceDefinition doesn't expose non-primitive fields and any of @ManagedAttribute methods
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/WFLY-3733?page=com.atlassian.jira.plugin.... ]
Radoslav Husar commented on WFLY-3733:
--------------------------------------
Example of #1 is at org.jgroups.protocols.FRAG2#num_frags_sent.
> ChannelInstanceResourceDefinition doesn't expose non-primitive fields and any of @ManagedAttribute methods
> ----------------------------------------------------------------------------------------------------------
>
> Key: WFLY-3733
> URL: https://issues.jboss.org/browse/WFLY-3733
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Clustering
> Affects Versions: 8.1.0.Final
> Reporter: Radoslav Husar
> Assignee: Radoslav Husar
> Priority: Minor
>
> It seems to me that org.jboss.as.clustering.jgroups.subsystem.ChannelInstanceResourceDefinition#getProtocolMetricResourceDefinition
> doesnt expose ManagedAttributes that would have to be registred as strings
> org/jboss/as/clustering/jgroups/subsystem/ChannelInstanceResourceDefinition.java:213
> and doesnt expose any of the annotated methods
> org/jboss/as/clustering/jgroups/subsystem/ChannelInstanceResourceDefinition.java:208
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months
[JBoss JIRA] (WFLY-3703) arq.container.domain.ManagementClient.readRootNode does not see servers on remote hosts
by Arcadiy Ivanov (JIRA)
[ https://issues.jboss.org/browse/WFLY-3703?page=com.atlassian.jira.plugin.... ]
Arcadiy Ivanov updated WFLY-3703:
---------------------------------
Git Pull Request: https://github.com/wildfly/wildfly/pull/6609 (was: https://github.com/wildfly/wildfly/pull/6565)
> arq.container.domain.ManagementClient.readRootNode does not see servers on remote hosts
> ---------------------------------------------------------------------------------------
>
> Key: WFLY-3703
> URL: https://issues.jboss.org/browse/WFLY-3703
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Test Suite
> Affects Versions: 8.1.0.Final
> Environment: Linux aimobile-sm.servicemesh.com 3.15.6-200.fc20.x86_64 #1 SMP Fri Jul 18 02:36:27 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
> Reporter: Arcadiy Ivanov
> Assignee: Alexey Loubyansky
> Priority: Blocker
> Attachments: non-recursive.txt, recursive-runtime.txt, recursive.txt
>
>
> Trying to use Arquillian with remote multi-host domain.
> Now see the code snippet below:
> * readRootNode calls readResource with includeRuntime set to true.
> * readResource also sets recursive to true.
> However due to this behavior of read-resource *no hosts other than domain controller's are visible to Arquillian*:
> [proxies – (boolean, default is false) – whether to include remote resources in a recursive query (i.e. host level resources from slave Host Controllers in a query of the Domain Controller; running server resources in a query of a host).|https://docs.jboss.org/author/display/WFLY8/Global+operations]
> +As a result if I have a DC on localhost with no servers and Host1 with Node1 on 127.0.0.2 and Host2 with Node2 on 127.0.0.3, Arquillian will not find ANY servers to deploy to - no proxies (remote hosts) will be enumerated.+
> {noformat}
> private void readRootNode() throws Exception {
> rootNode = readResource(new ModelNode());
> }
> private ModelNode readResource(ModelNode address) throws Exception {
> return readResource(address, true);
> }
> private ModelNode readResource(ModelNode address, boolean includeRuntime) throws Exception {
> final ModelNode operation = new ModelNode();
> operation.get(OP).set(READ_RESOURCE_OPERATION);
> operation.get(RECURSIVE).set("true");
> operation.get(INCLUDE_RUNTIME).set(includeRuntime);
> operation.get(OP_ADDR).set(address);
> return executeForResult(operation);
> }
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months
[JBoss JIRA] (WFLY-3740) standalone.sh does not compute correct module path in Cygwin
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFLY-3740?page=com.atlassian.jira.plugin.... ]
Tomaz Cerar reassigned WFLY-3740:
---------------------------------
Assignee: Tomaz Cerar (was: Jason Greene)
> standalone.sh does not compute correct module path in Cygwin
> ------------------------------------------------------------
>
> Key: WFLY-3740
> URL: https://issues.jboss.org/browse/WFLY-3740
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Scripts
> Affects Versions: 8.1.0.Final
> Environment: Windows with Cygwin
> Reporter: David Del Vecchio
> Assignee: Tomaz Cerar
> Priority: Minor
>
> standalone.sh does not seem to compute the correct JBOSS_MODULEPATH on Cygwin as a result, starting up the server gives the following error:
> {noformat}
> org.jboss.modules.ModuleNotFoundException: org.jboss.as.standalone:main
> at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:240)
> at org.jboss.modules.Main.main(Main.java:385)}}
> {noformat}
> The problem seems to be somewhat related to this issue in that a mix of Windows and Unix style paths are being computed:
> https://issues.jboss.org/browse/WFLY-2523
> Since {{JBOSS_MODULEPATH}} is not set until after all the paths (such as {{JBOSS_HOME}}) have been converted to Windows style, {{JBOSS_MODULEPATH}} ends up with a Unix style forward slash at the end of what is otherwise a Windows style path.
> The fix for me was to move the code which sets the {{JBOSS_MODULEPATH}} to earlier in the script. I moved it to right after the {{export JBOSS_HOME}} line:
> {code:title=standalone.sh|borderStyle=solid}
> ...
> export JBOSS_HOME
> if [ "x$JBOSS_MODULEPATH" = "x" ]; then
> JBOSS_MODULEPATH="$JBOSS_HOME/modules"
> fi
> ...
> {code}
> Probably the key thing is just that the {{JBOSS_MODULEPATH}} gets set before everything is switched to Windows paths in this section of the script:
> {code:title=standalone.sh|borderStyle=solid}
> # For Cygwin, switch paths to Windows format before running java
> if $cygwin; then
> JBOSS_HOME=`cygpath --path --windows "$JBOSS_HOME"`
> JAVA_HOME=`cygpath --path --windows "$JAVA_HOME"`
> JBOSS_MODULEPATH=`cygpath --path --windows "$JBOSS_MODULEPATH"`
> JBOSS_BASE_DIR=`cygpath --path --windows "$JBOSS_BASE_DIR"`
> JBOSS_LOG_DIR=`cygpath --path --windows "$JBOSS_LOG_DIR"`
> JBOSS_CONFIG_DIR=`cygpath --path --windows "$JBOSS_CONFIG_DIR"`
> fi
> {code}
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months
[JBoss JIRA] (WFLY-3740) standalone.sh does not compute correct module path in Cygwin
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFLY-3740?page=com.atlassian.jira.plugin.... ]
Tomaz Cerar updated WFLY-3740:
------------------------------
Component/s: Scripts
> standalone.sh does not compute correct module path in Cygwin
> ------------------------------------------------------------
>
> Key: WFLY-3740
> URL: https://issues.jboss.org/browse/WFLY-3740
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Scripts
> Affects Versions: 8.1.0.Final
> Environment: Windows with Cygwin
> Reporter: David Del Vecchio
> Assignee: Jason Greene
> Priority: Minor
>
> standalone.sh does not seem to compute the correct JBOSS_MODULEPATH on Cygwin as a result, starting up the server gives the following error:
> {noformat}
> org.jboss.modules.ModuleNotFoundException: org.jboss.as.standalone:main
> at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:240)
> at org.jboss.modules.Main.main(Main.java:385)}}
> {noformat}
> The problem seems to be somewhat related to this issue in that a mix of Windows and Unix style paths are being computed:
> https://issues.jboss.org/browse/WFLY-2523
> Since {{JBOSS_MODULEPATH}} is not set until after all the paths (such as {{JBOSS_HOME}}) have been converted to Windows style, {{JBOSS_MODULEPATH}} ends up with a Unix style forward slash at the end of what is otherwise a Windows style path.
> The fix for me was to move the code which sets the {{JBOSS_MODULEPATH}} to earlier in the script. I moved it to right after the {{export JBOSS_HOME}} line:
> {code:title=standalone.sh|borderStyle=solid}
> ...
> export JBOSS_HOME
> if [ "x$JBOSS_MODULEPATH" = "x" ]; then
> JBOSS_MODULEPATH="$JBOSS_HOME/modules"
> fi
> ...
> {code}
> Probably the key thing is just that the {{JBOSS_MODULEPATH}} gets set before everything is switched to Windows paths in this section of the script:
> {code:title=standalone.sh|borderStyle=solid}
> # For Cygwin, switch paths to Windows format before running java
> if $cygwin; then
> JBOSS_HOME=`cygpath --path --windows "$JBOSS_HOME"`
> JAVA_HOME=`cygpath --path --windows "$JAVA_HOME"`
> JBOSS_MODULEPATH=`cygpath --path --windows "$JBOSS_MODULEPATH"`
> JBOSS_BASE_DIR=`cygpath --path --windows "$JBOSS_BASE_DIR"`
> JBOSS_LOG_DIR=`cygpath --path --windows "$JBOSS_LOG_DIR"`
> JBOSS_CONFIG_DIR=`cygpath --path --windows "$JBOSS_CONFIG_DIR"`
> fi
> {code}
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months
[JBoss JIRA] (WFLY-3740) standalone.sh does not compute correct module path in Cygwin
by David Del Vecchio (JIRA)
[ https://issues.jboss.org/browse/WFLY-3740?page=com.atlassian.jira.plugin.... ]
David Del Vecchio updated WFLY-3740:
------------------------------------
Description:
standalone.sh does not seem to compute the correct JBOSS_MODULEPATH on Cygwin as a result, starting up the server gives the following error:
{noformat}
org.jboss.modules.ModuleNotFoundException: org.jboss.as.standalone:main
at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:240)
at org.jboss.modules.Main.main(Main.java:385)}}
{noformat}
The problem seems to be somewhat related to this issue in that a mix of Windows and Unix style paths are being computed:
https://issues.jboss.org/browse/WFLY-2523
Since {{JBOSS_MODULEPATH}} is not set until after all the paths (such as {{JBOSS_HOME}}) have been converted to Windows style, {{JBOSS_MODULEPATH}} ends up with a Unix style forward slash at the end of what is otherwise a Windows style path.
The fix for me was to move the code which sets the {{JBOSS_MODULEPATH}} to earlier in the script. I moved it to right after the {{export JBOSS_HOME}} line:
{code:title=standalone.sh|borderStyle=solid}
...
export JBOSS_HOME
if [ "x$JBOSS_MODULEPATH" = "x" ]; then
JBOSS_MODULEPATH="$JBOSS_HOME/modules"
fi
...
{code}
Probably the key thing is just that the {{JBOSS_MODULEPATH}} gets set before everything is switched to Windows paths in this section of the script:
{code:title=standalone.sh|borderStyle=solid}
# For Cygwin, switch paths to Windows format before running java
if $cygwin; then
JBOSS_HOME=`cygpath --path --windows "$JBOSS_HOME"`
JAVA_HOME=`cygpath --path --windows "$JAVA_HOME"`
JBOSS_MODULEPATH=`cygpath --path --windows "$JBOSS_MODULEPATH"`
JBOSS_BASE_DIR=`cygpath --path --windows "$JBOSS_BASE_DIR"`
JBOSS_LOG_DIR=`cygpath --path --windows "$JBOSS_LOG_DIR"`
JBOSS_CONFIG_DIR=`cygpath --path --windows "$JBOSS_CONFIG_DIR"`
fi
{code}
was:
standalone.sh does not seem to compute the correct JBOSS_MODULEPATH on Cygwin as a result, starting up the server gives the following error:
{{org.jboss.modules.ModuleNotFoundException: org.jboss.as.standalone:main
at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:240)
at org.jboss.modules.Main.main(Main.java:385)}}
The problem seems to be somewhat related to this issue in that a mix of Windows and Unix style paths are being computed:
https://issues.jboss.org/browse/WFLY-2523
Since {{JBOSS_MODULEPATH}} is not set until after all the paths (such as {{JBOSS_HOME}}) have been converted to Windows style, {{JBOSS_MODULEPATH}} ends up with a Unix style forward slash at the end of what is otherwise a Windows style path.
The fix for me was to move the code which sets the {{JBOSS_MODULEPATH}} to earlier in the script. I moved it to right after the {{export JBOSS_HOME}} line:
bq. ...
export JBOSS_HOME
if [ "x$JBOSS_MODULEPATH" = "x" ]; then
JBOSS_MODULEPATH="$JBOSS_HOME/modules"
fi
...
Probably the key thing is just that the {{JBOSS_MODULEPATH}} gets set before everything is switched to Windows paths in this section of the script:
bq. # For Cygwin, switch paths to Windows format before running java
if $cygwin; then
JBOSS_HOME=`cygpath --path --windows "$JBOSS_HOME"`
JAVA_HOME=`cygpath --path --windows "$JAVA_HOME"`
JBOSS_MODULEPATH=`cygpath --path --windows "$JBOSS_MODULEPATH"`
JBOSS_BASE_DIR=`cygpath --path --windows "$JBOSS_BASE_DIR"`
JBOSS_LOG_DIR=`cygpath --path --windows "$JBOSS_LOG_DIR"`
JBOSS_CONFIG_DIR=`cygpath --path --windows "$JBOSS_CONFIG_DIR"`
fi
> standalone.sh does not compute correct module path in Cygwin
> ------------------------------------------------------------
>
> Key: WFLY-3740
> URL: https://issues.jboss.org/browse/WFLY-3740
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 8.1.0.Final
> Environment: Windows with Cygwin
> Reporter: David Del Vecchio
> Assignee: Jason Greene
> Priority: Minor
>
> standalone.sh does not seem to compute the correct JBOSS_MODULEPATH on Cygwin as a result, starting up the server gives the following error:
> {noformat}
> org.jboss.modules.ModuleNotFoundException: org.jboss.as.standalone:main
> at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:240)
> at org.jboss.modules.Main.main(Main.java:385)}}
> {noformat}
> The problem seems to be somewhat related to this issue in that a mix of Windows and Unix style paths are being computed:
> https://issues.jboss.org/browse/WFLY-2523
> Since {{JBOSS_MODULEPATH}} is not set until after all the paths (such as {{JBOSS_HOME}}) have been converted to Windows style, {{JBOSS_MODULEPATH}} ends up with a Unix style forward slash at the end of what is otherwise a Windows style path.
> The fix for me was to move the code which sets the {{JBOSS_MODULEPATH}} to earlier in the script. I moved it to right after the {{export JBOSS_HOME}} line:
> {code:title=standalone.sh|borderStyle=solid}
> ...
> export JBOSS_HOME
> if [ "x$JBOSS_MODULEPATH" = "x" ]; then
> JBOSS_MODULEPATH="$JBOSS_HOME/modules"
> fi
> ...
> {code}
> Probably the key thing is just that the {{JBOSS_MODULEPATH}} gets set before everything is switched to Windows paths in this section of the script:
> {code:title=standalone.sh|borderStyle=solid}
> # For Cygwin, switch paths to Windows format before running java
> if $cygwin; then
> JBOSS_HOME=`cygpath --path --windows "$JBOSS_HOME"`
> JAVA_HOME=`cygpath --path --windows "$JAVA_HOME"`
> JBOSS_MODULEPATH=`cygpath --path --windows "$JBOSS_MODULEPATH"`
> JBOSS_BASE_DIR=`cygpath --path --windows "$JBOSS_BASE_DIR"`
> JBOSS_LOG_DIR=`cygpath --path --windows "$JBOSS_LOG_DIR"`
> JBOSS_CONFIG_DIR=`cygpath --path --windows "$JBOSS_CONFIG_DIR"`
> fi
> {code}
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months
[JBoss JIRA] (WFLY-3740) standalone.sh does not compute correct module path in Cygwin
by David Del Vecchio (JIRA)
[ https://issues.jboss.org/browse/WFLY-3740?page=com.atlassian.jira.plugin.... ]
David Del Vecchio updated WFLY-3740:
------------------------------------
Description:
standalone.sh does not seem to compute the correct JBOSS_MODULEPATH on Cygwin as a result, starting up the server gives the following error:
{{org.jboss.modules.ModuleNotFoundException: org.jboss.as.standalone:main
at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:240)
at org.jboss.modules.Main.main(Main.java:385)}}
The problem seems to be somewhat related to this issue in that a mix of Windows and Unix style paths are being computed:
https://issues.jboss.org/browse/WFLY-2523
Since {{JBOSS_MODULEPATH}} is not set until after all the paths (such as {{JBOSS_HOME}}) have been converted to Windows style, {{JBOSS_MODULEPATH}} ends up with a Unix style forward slash at the end of what is otherwise a Windows style path.
The fix for me was to move the code which sets the {{JBOSS_MODULEPATH}} to earlier in the script. I moved it to right after the {{export JBOSS_HOME}} line:
bq. ...
export JBOSS_HOME
if [ "x$JBOSS_MODULEPATH" = "x" ]; then
JBOSS_MODULEPATH="$JBOSS_HOME/modules"
fi
...
Probably the key thing is just that the {{JBOSS_MODULEPATH}} gets set before everything is switched to Windows paths in this section of the script:
bq. # For Cygwin, switch paths to Windows format before running java
if $cygwin; then
JBOSS_HOME=`cygpath --path --windows "$JBOSS_HOME"`
JAVA_HOME=`cygpath --path --windows "$JAVA_HOME"`
JBOSS_MODULEPATH=`cygpath --path --windows "$JBOSS_MODULEPATH"`
JBOSS_BASE_DIR=`cygpath --path --windows "$JBOSS_BASE_DIR"`
JBOSS_LOG_DIR=`cygpath --path --windows "$JBOSS_LOG_DIR"`
JBOSS_CONFIG_DIR=`cygpath --path --windows "$JBOSS_CONFIG_DIR"`
fi
was:
standalone.sh does not seem to compute the correct JBOSS_MODULEPATH on Cygwin as a result, starting up the server gives the following error:
{{org.jboss.modules.ModuleNotFoundException: org.jboss.as.standalone:main
at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:240)
at org.jboss.modules.Main.main(Main.java:385)}}
The problem seems to be somewhat related to this issue in that a mix of Windows and Unix style paths are being computed:
https://issues.jboss.org/browse/WFLY-2523
Since {{JBOSS_MODULEPATH}} is not set until after all the paths (such as {{JBOSS_HOME}}) have been converted to Windows style, {{JBOSS_MODULEPATH}} ends up with a Unix style forward slash at the end of what is otherwise a Windows style path.
The fix for me was to move the code which sets the {{JBOSS_MODULEPATH}} to earlier in the script. I moved it to right after the {{export JBOSS_HOME}} line: {{
...
export JBOSS_HOME
if [ "x$JBOSS_MODULEPATH" = "x" ]; then
JBOSS_MODULEPATH="$JBOSS_HOME/modules"
fi
...}}
Probably the key thing is just that the {{JBOSS_MODULEPATH}} gets set before everything is switched to Windows paths in this section of the script:
{{# For Cygwin, switch paths to Windows format before running java
if $cygwin; then
JBOSS_HOME=`cygpath --path --windows "$JBOSS_HOME"`
JAVA_HOME=`cygpath --path --windows "$JAVA_HOME"`
JBOSS_MODULEPATH=`cygpath --path --windows "$JBOSS_MODULEPATH"`
JBOSS_BASE_DIR=`cygpath --path --windows "$JBOSS_BASE_DIR"`
JBOSS_LOG_DIR=`cygpath --path --windows "$JBOSS_LOG_DIR"`
JBOSS_CONFIG_DIR=`cygpath --path --windows "$JBOSS_CONFIG_DIR"`
fi}}
> standalone.sh does not compute correct module path in Cygwin
> ------------------------------------------------------------
>
> Key: WFLY-3740
> URL: https://issues.jboss.org/browse/WFLY-3740
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 8.1.0.Final
> Environment: Windows with Cygwin
> Reporter: David Del Vecchio
> Assignee: Jason Greene
> Priority: Minor
>
> standalone.sh does not seem to compute the correct JBOSS_MODULEPATH on Cygwin as a result, starting up the server gives the following error:
> {{org.jboss.modules.ModuleNotFoundException: org.jboss.as.standalone:main
> at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:240)
> at org.jboss.modules.Main.main(Main.java:385)}}
> The problem seems to be somewhat related to this issue in that a mix of Windows and Unix style paths are being computed:
> https://issues.jboss.org/browse/WFLY-2523
> Since {{JBOSS_MODULEPATH}} is not set until after all the paths (such as {{JBOSS_HOME}}) have been converted to Windows style, {{JBOSS_MODULEPATH}} ends up with a Unix style forward slash at the end of what is otherwise a Windows style path.
> The fix for me was to move the code which sets the {{JBOSS_MODULEPATH}} to earlier in the script. I moved it to right after the {{export JBOSS_HOME}} line:
> bq. ...
> export JBOSS_HOME
> if [ "x$JBOSS_MODULEPATH" = "x" ]; then
> JBOSS_MODULEPATH="$JBOSS_HOME/modules"
> fi
> ...
> Probably the key thing is just that the {{JBOSS_MODULEPATH}} gets set before everything is switched to Windows paths in this section of the script:
> bq. # For Cygwin, switch paths to Windows format before running java
> if $cygwin; then
> JBOSS_HOME=`cygpath --path --windows "$JBOSS_HOME"`
> JAVA_HOME=`cygpath --path --windows "$JAVA_HOME"`
> JBOSS_MODULEPATH=`cygpath --path --windows "$JBOSS_MODULEPATH"`
> JBOSS_BASE_DIR=`cygpath --path --windows "$JBOSS_BASE_DIR"`
> JBOSS_LOG_DIR=`cygpath --path --windows "$JBOSS_LOG_DIR"`
> JBOSS_CONFIG_DIR=`cygpath --path --windows "$JBOSS_CONFIG_DIR"`
> fi
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months