[jboss-jira] [JBoss JIRA] (WFLY-1871) CLI module command doesn't allow cross platform resource paths
RH Bugzilla Integration (JIRA)
jira-events at lists.jboss.org
Fri Oct 4 02:40:02 EDT 2013
[ https://issues.jboss.org/browse/WFLY-1871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12809295#comment-12809295 ]
RH Bugzilla Integration commented on WFLY-1871:
-----------------------------------------------
Ivo Studensky <istudens at redhat.com> made a comment on [bug 1015400|https://bugzilla.redhat.com/show_bug.cgi?id=1015400]
Description of problem:
Backport of WFLY-1871 to EAP.
Original description:
The CLI module command has an argument called "resources". This argument allows you to specify one or more resources separated by the platform-specific path separator. The problem with this is that you can not create a platform-independent script that uses this resources argument.
I have not found a universal path separator character that would work. However, since the creator of the script knows the characters used in his path, we can allow him to specify his own separator.
As an enhancement, I propose to add an argument called "resourceDelimiter". If present, the ASModuleHandler class will use the user-defined delimiter instead of the platform-specific path separator character.
Example usage:
module add --name=org.foo --resources=firstResource.jar:secondResource.jar --resourceDelimiter=: --module-xml=foo-module.xml
The above command would work on Unix, Windows, or any other platform.
> CLI module command doesn't allow cross platform resource paths
> --------------------------------------------------------------
>
> Key: WFLY-1871
> URL: https://issues.jboss.org/browse/WFLY-1871
> Project: WildFly
> Issue Type: Enhancement
> Components: CLI
> Affects Versions: 8.0.0.Alpha4
> Reporter: Stan Silvert
> Assignee: Stan Silvert
> Fix For: 8.0.0.Beta1
>
>
> The CLI module command has an argument called "resources". This argument allows you to specify one or more resources separated by the platform-specific path separator. The problem with this is that you can not create a platform-independent script that uses this resources argument.
> I have not found a universal path separator character that would work. However, since the creator of the script knows the characters used in his path, we can allow him to specify his own separator.
> As an enhancement, I propose to add an argument called "resourceDelimiter". If present, the ASModuleHandler class will use the user-defined delimiter instead of the platform-specific path separator character.
> Example usage:
> {noformat}
> module add --name=org.foo --resources=firstResource.jar:secondResource.jar --resourceDelimiter=: --module-xml=foo-module.xml
> {noformat}
> The above command would work on Unix, Windows, or any other platform.
--
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
More information about the jboss-jira
mailing list