AUR (en) - wildfly

Search Criteria

Package Details: wildfly 33.0.1-1

Git Clone URL:	https://aur.archlinux.org/wildfly.git (read-only, click to copy)
Package Base:	wildfly
Description:	Wildfly Application Server.
Upstream URL:	http://www.wildfly.org/
Keywords:	jakartaee java javaee
Licenses:	LGPL
Conflicts:	wildfly-devel
Submitter:	nachtwandler
Maintainer:	morealaz (stick)
Last Packager:	morealaz
Votes:	29
Popularity:	0.000000
First Submitted:	2013-05-30 13:14 (UTC)
Last Updated:	2024-08-25 07:45 (UTC)

Git Clone URL:

https://aur.archlinux.org/wildfly.git (read-only, click to copy)

Package Base:

wildfly

Description:

Wildfly Application Server.

Upstream URL:

http://www.wildfly.org/

Keywords:

jakartaee java javaee

Licenses:

LGPL

Conflicts:

wildfly-devel

Submitter:

nachtwandler

Maintainer:

morealaz (stick)

Last Packager:

morealaz

Votes:

Popularity:

0.000000

First Submitted:

2013-05-30 13:14 (UTC)

Last Updated:

2024-08-25 07:45 (UTC)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 Next › Last »

jamesan commented on 2015-08-10 23:01 (UTC)

The latest upstream version is v9.0.1, released July 23, 2015.

victor.badulescu commented on 2015-02-16 12:19 (UTC)

Hello, I had a issue with my java setup, I only had jdk installed from AUR. I did a clean install of java (jdk7-openjdk) and re installed the wildfly package(without any modification to the wrapped.sh file) and now it is up and running without any changes. Thank you for the help provided

d1x commented on 2015-02-16 10:18 (UTC)

Hi Victor, Sourcing two .sh files at the beginning only "imports" variables that are used in these files - they don't execute anything. From that reason I don't think swapping these two lines has any effect (as long as none of them is using variables from other one). Did you changed these files before the swap somehow? I think you may have a problem with your java in Arch. Please try to uninstall WildFly package completely, set the correct java via archlinux-java. Try to test your Java (e.g. by java -version command), install wildfly again and try to start it again via service.

victor.badulescu commented on 2015-02-16 09:58 (UTC)

Hello, I tied to install the package but the service failed to start. I looked at the logs and saw that the jboss-cli command was unable to access the java command. I think this is because in the systemd-wraper.sh the order of the first two source commands is incorrect, sourcing /etc/profile.d/jre.sh should be done before /etc/profile.d/wildfly.sh. I reordered the commands and managed to get service to start.

d1x commented on 2014-09-23 18:56 (UTC)

You are right, changed it to /etc/profile.d/jre.sh as it should be available from java-common package

ilpianista commented on 2014-09-23 16:20 (UTC)

"/opt/wildfly/bin/systemd-wrapper.sh: line 3: /etc/profile.d/jdk.sh: No such file or directory" That file is no more installed by Arch java packages.

d1x commented on 2014-09-22 06:41 (UTC)

From version 8.1.0.Final-2: I moved the package from /usr/share to /opt (as it more suites the package type). You should move your configuration (e.g. standalone.xml) or deployments to new directory. Also configuration in /etc/profile.d/wildfly.sh was slightly changed.

d1x commented on 2014-08-19 16:44 (UTC)

Thanks for your note, I made only system user, not group. Now it should be ok.

ilpianista commented on 2014-08-16 16:50 (UTC)

The group is still installed as user group, not as system.