Bug 1015400 - CLI module command doesn't allow cross platform resource paths
Summary: CLI module command doesn't allow cross platform resource paths
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: CLI
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: EAP 6.4.2
Assignee: Ivo Studensky
QA Contact: Petr Kremensky
Russell Dickenson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-10-04 06:39 UTC by Ivo Studensky
Modified: 2015-06-15 13:47 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-06-15 13:47:42 UTC
Type: Feature Request
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker WFLY-1871 0 Major Resolved CLI module command doesn't allow cross platform resource paths 2015-06-16 13:28:28 UTC

Description Ivo Studensky 2013-10-04 06:39:07 UTC
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.

Comment 1 Alexey Loubyansky 2013-10-04 14:47:09 UTC
ok, just, please, follow the argument naming convention, i.e. --resource-delimiter

Comment 3 Ivo Studensky 2013-10-04 15:09:00 UTC
Changed to Enhancement.

Comment 4 JBoss JIRA Server 2013-10-04 15:38:20 UTC
Stan Silvert <ssilvert> updated the status of jira WFLY-1871 to Reopened

Comment 5 JBoss JIRA Server 2013-10-04 15:38:20 UTC
Stan Silvert <ssilvert> made a comment on jira WFLY-1871

Reopening.  The naming convention issue on the resource delimiter was missed the first time around.

Comment 8 JBoss JIRA Server 2013-12-23 14:43:01 UTC
Stan Silvert <ssilvert> updated the status of jira WFLY-1871 to Resolved

Comment 10 Carlo de Wolf 2015-06-15 13:47:42 UTC
Triage, no RFE in 6.4.z


Note You need to log in before you can comment on or make changes to this bug.