[jboss-jira] [JBoss JIRA] (WFLY-1871) CLI module command doesn't allow cross platform resource paths
RH Bugzilla Integration (JIRA)
issues at jboss.org
Mon Jun 15 09:48:04 EDT 2015
[ https://issues.jboss.org/browse/WFLY-1871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13079133#comment-13079133 ]
RH Bugzilla Integration commented on WFLY-1871:
-----------------------------------------------
Carlo de Wolf <cdewolf at redhat.com> changed the Status of [bug 1015400|https://bugzilla.redhat.com/show_bug.cgi?id=1015400] from ASSIGNED to CLOSED
> 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.Final
>
>
> 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 was sent by Atlassian JIRA
(v6.3.15#6346)
More information about the jboss-jira
mailing list