Upgrade java/wildfly10 to 10.1.0.

- Move installation directory to /usr/local/wildfly10.
- Fix directory permissions and ownership (root:wheel everywhere except config.)
- Remove all @dir entries which are now unnecessary.
- Add upgrade notice to UPDATING.

PR:		212052
Submitted by:	olgeni
Approved by:	maintainer

1 files changed, 15 insertions, 6 deletions

diff --git a/UPDATING b/UPDATING
index 70e762651868..c5d05868f517 100644
--- a/UPDATING
+++ b/UPDATING
@@ -5,6 +5,15 @@ they are unavoidable.
 You should get into the habit of checking this file for changes each time
 you update your ports collection, before attempting any port upgrades.
 
+20170116:
+  AFFECTS: users of java/wildfly10
+  AUTHOR: olgeni@FreeBSD.org
+
+  The java/wildfly10 port has been updated to 10.1.0. To complete the
+  migration you must copy your existing configuration (directories
+  "appclient", "standalone", and "domain") from /usr/local/wildfly-10.0.0
+  to /usr/local/wildfly10.
+
 20170115:
   AFFECTS: users of net-mgmt/librenms
   AUTHOR: dvl@FreeBSD.org
@@ -190,7 +199,7 @@ you update your ports collection, before attempting any port upgrades.
 
   Bareos v1.6.x changed the configuration scheme, from one configuration
   file per Bareos component (file daemon, storage daemon, and director)
-  to several configuration files, in several directories, for each 
+  to several configuration files, in several directories, for each
   component. See http://doc.bareos.org/master/html/bareos-manual-main-reference.html
 
   The new scheme will use all files named *.conf in the directory
@@ -218,7 +227,7 @@ you update your ports collection, before attempting any port upgrades.
    - misc/osinfo-db: contains database with OS data
    - devel/libosinfo: the library
 
-  As osinfo-db-tools now ships binaries that previously were 
+  As osinfo-db-tools now ships binaries that previously were
   part of libosinfo, it's required to delete the old libosinfo
   package to prevent conflict because of same files installation:
 
@@ -444,15 +453,15 @@ you update your ports collection, before attempting any port upgrades.
   AFFECTS: Users of net-im/ejabberd
   AUTHOR: ashish@FreeBSD.org
 
-  Before upgrading ejabberd to 16.09, please make sure to backup your 
+  Before upgrading ejabberd to 16.09, please make sure to backup your
   ejabberd data using:
- 
+
      % sudo -u ejabberd -H ejabberdctl backup /path/to/backup/file
 
-  In some cases, ejabberd may fail to start, for which a workaround is to 
+  In some cases, ejabberd may fail to start, for which a workaround is to
   remove the schema.DAT file from /var/spool/ejabberd before starting, and
   then restoring everything from the backup using:
-     
+
      % sudo -u ejabberd -H ejabberdctl restore /path/to/backup/file
 
   For more details: