[jboss-jira] [JBoss JIRA] (WFLY-10567) Broken JSF module installer
[
https://issues.jboss.org/browse/WFLY-10567?page=com.atlassian.jira.plugin...
]
Jan Kašík edited comment on WFLY-10567 at 7/26/18 7:15 AM:
-----------------------------------------------------------
Issue is present in wildfly-14.0.0.Beta2-SNAPSHOT (commit
c80c2b1d84846c4546a07506c7d5e18e1958595a) again, probably caused by commit
b2878c33bf12e4430c6ad90d54d41ef7b54d5c77
was (Author: jkasik):
Issue is present in wildfly-14.0.0.Beta2-SNAPSHOT again, probably caused by commit
b2878c33bf12e4430c6ad90d54d41ef7b54d5c77
Broken JSF module installer
---------------------------
Key: WFLY-10567
URL: https://issues.jboss.org/browse/WFLY-10567
Project: WildFly
Issue Type: Bug
Components: JSF
Affects Versions: 14.0.0.CR1
Reporter: Jan Kašík
Assignee: Dmitrii Tikhomirov
Fix For: 14.0.0.CR1
Attachments: hello-jsf-version-0.0.1-SNAPSHOT.war
It is currently not possible to deploy *.cli built by multi-jsf-installer shipped with
WildFly. When attempting to deploy, this message will appear:
{code}
org.jboss.as.cli.CommandFormatException: org.jboss.as.cli.CommandLineException:
java.util.concurrent.ExecutionException: org.jboss.as.cli.CommandLineException: Failed to
locate
/tmp/vfs/cli-1528866094723/cli-1528866094723450313ef1dc90cff/install-mojarra-2.2.17.cli-212b6d42ba0c47e1/jsf-api-2.2.17.jar,
if you defined a nonexistent resource on purpose you should use the
--allow-nonexistent-resources option
{code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)