After editing the standalone.sh file to use wildfly instead of jboss I get the following error: The logging.properties files is owner wildfly and permissions rw------.

Unable to read the logging configuration from 'file:/usr/share/wildfly/standalone/configuration/logging.properties' (java.io.FileNotFoundException: /usr/share/wildfly/standalone/configuration/logging.properties (Permission denied))

I am facing the same issue on latest Fedora 20 X86_64 3.17.8-200. I had installed wildfly-8.1.0-3.fc20.noarch.rpm.

From /usr/share/wildfly/bin folder i issued the following command as root user:

wildfly-cp -l /home/admin/wildfly-cp

The o/p if as follows:
cp: cannot stat ‘/usr/share/jboss-as/docs/examples/configs/standalone.xml’: No such file or directory
cp: cannot stat ‘/usr/share/jboss-as/docs/examples/properties/logging.properties’: No such file or directory
cp: cannot stat ‘/usr/share/jboss-as/docs/examples/properties/mgmt-users.properties’: No such file or directory
chmod: cannot access ‘/home/admin/wildfly-cp/configuration/mgmt-users.properties’: No such file or directory
Directory /home/admin/wildfly-cp is prepared to launch WildFly AS!

You can now boot your instance: /home/admin/wildfly-cp/bin/standalone.sh

As mentioned by Karl the standalone.sh point to following path which does not exists:
/usr/share/jboss-as/bin/standalone.sh


wildfly-cp seems to be broken at multiple places.

I'll fix it as part of the upgrade to 8.2.0.Final.

Will we get 8.2.0 update on Fedora 20?

No, it seems that Fedora 20 will not get the update, I don't have time to backport all the required changes.

This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '20'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.