AUR (en) - wildfly

Search Criteria

Package Details: wildfly 31.0.0-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-02-06 12:38 (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-02-06 12:38 (UTC)

Latest Comments

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

Khaithang commented on 2019-05-04 20:58 (UTC)

@stick, this package too have systemd-wrapper, so what is the difference?

stick commented on 2018-10-14 00:40 (UTC)

I've submitted a new AUR package, wildfly-systemd, which uses the systemd setup provided with wildfly. This will be a test to see if users prefer that option. Please vote for one or the other so that we get a good read on who uses what. Thanks.

https://aur.archlinux.org/packages/wildfly-systemd/

stick commented on 2018-03-13 16:34 (UTC)

@hrauch I don't know of any way to conduct such a poll, but I am willing to work on the installation preference problem. However, I'm pulling 60-70 hours a week at work until the end of April, so it will be a bit.

hrauch commented on 2018-03-06 21:05 (UTC)

@nstickney: you certainly got a valid point regarding usage of your systemd approach vs. the current approach which may already be in use by a larger number of users. Maybe either a pool among all wildfly Final AUR users would be adequate or asking the user about his installation preferrence upon processing of the PKGBUILD file.

hrauch commented on 2018-03-06 20:28 (UTC)

@nstickney: Thanks for the hint. I added you as co maintainer.

stick commented on 2018-03-06 03:45 (UTC)

There is a systemd script setup in the WildFly docs, included in the tarball download. I've updated this package to use it, since that appears to be the more "default" installation method, but I'm (1) not the maintainer and I (2) don't want this to break anyone's setup if you're using the current method.

However, if you want 12.0.0.Final, and the recommended systemd setup, it's available at https://github.com/nstickney/wildfly-aur. @d1x/@nachtwandler/@hrauch, feel free to steal it.

d1x commented on 2018-01-25 00:02 (UTC)

My apologies to everyone that I did not update to 11.0 for some time. I was away and now I am truly busy. I do not want to make this happen again so I disown this package. If anyone takes ownership and needs some support, feel free to contact me - I will try to help as much as possible.

stick commented on 2017-11-03 18:15 (UTC)

Working PKGBUILD for version 11.0.0.Final is available here: https://pastebin.com/raw/Faj3c5zx

asbachb commented on 2016-11-15 00:40 (UTC)

Sorry d1x I wasn't notified about your comment. Feel free to change that with the next release. I just configure a server which tries to install some x11 stuff caused by the default openjdk dependency. But since I've my own small build farm I did a fork with the change on github and prebuilt that release. So no pressure from my site.

d1x commented on 2016-11-01 14:05 (UTC)

Hi asbachb - you are right, I think headless would probably do. Anyway, I will change the deps with next release of wildfly as it is not something "blocking". Do you need this change for something or can it wait?