[jboss-jira] [JBoss JIRA] (WFLY-10567) Broken JSF module installer

[Dmitrii Tikhomirov (JIRA)]

     [ https://issues.jboss.org/browse/WFLY-10567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dmitrii Tikhomirov updated WFLY-10567:
--------------------------------------
    Steps to Reproduce: 
{code}
git clone https://github.com/wildfly/wildfly
cd wildfly
mvn clean install -DskipTests
cd jsf/multi-jsf-installer
mvn -Djsf-version=2.2.17 -Pmojarra-2.x clean assembly:single
cp target/install-mojarra-2.2.17.zip target/install-mojarra-2.2.17.cli

deploy ~/workspace/wildfly/jsf/multi-jsf-installer/target/install-mojarra-2.2.17.cli
/subsystem=jsf/:write-attribute(name=default-jsf-impl-slot,value=mojarra-2.2.17)
{code}

  was:
{code}
git clone https://github.com/wildfly/wildfly
cd wildfly
mvn clean install -DskipTests
cd jsf/multi-jsf-installer
mvn -Djsf-version=2.2.17 -Pmojarra-2.x clean assembly:single
cp target/install-mojarra-2.2.17.zip target/install-mojarra-2.2.17.cli

deploy ~/workspace/wildfly/jsf/multi-jsf-installer/target/install-mojarra-2.2.17.cli
{code}



> 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)