Package Details: glassfish-v4 4.1.2-1

Git Clone URL: (read-only)
Package Base: glassfish-v4
Description: GlassFish 4 is a Java EE 7 open source application server
Upstream URL:
Licenses: CDDL
Conflicts: glassfish
Provides: glassfish
Submitter: None
Maintainer: Snowball239
Last Packager: Snowball239
Votes: 19
Popularity: 0.546263
First Submitted: 2013-06-25 04:13
Last Updated: 2017-04-19 10:10

Latest Comments

Marcel_K commented on 2017-08-08 11:37

You may be correct about the other packages, but I there might be a historical reason for these settings: one time there possibly was a package called glassfish or that provided glassfish that this package *did* conflict with. Or it is there simply because glassfish-web-v4 provides glassfish. Generally, it indeed is better to provide general provides and conflicts arrays if your package targets a specific version.

If Glassfish 5 can be installed alongside version 4 I think the correct situation would be to rename this package to glassfish4, remove its provides and conflicts arrays and change those of glassfish-web-v4 to 'glassfish4'.

morealaz commented on 2017-08-08 11:19

@Marcel_K is right about provides and conflicts. but I think they are not suppose to be glassfish either, because different major version of glassfish can be installed and used side by side without any conflict, but packages like glassfish-web-v4 which are in conflict with glassfish-v4 need to have provides and conflicts which are set to glassfish4 not glassfish alone.
I think this package doesn't need to have provides and conflicts.

Marcel_K commented on 2017-08-08 10:06

No, provides and conflicts *should* be glassfish, please read

Snowball239 commented on 2017-08-08 09:48

Makes sense, will do that as soon as I'll have some spare time

morealaz commented on 2017-08-08 08:26

I think it would be better to rename this package to glassfish4 instead of glassfish-v4, like tomcat which have different package for different version as tomcat7 and tomcat8.
also Provides and Conflicts list should be glassfish4 instead of glassfish, and service file should be glassfish4.service.
I create a glassfish5 which can be installed alongside this package.

Snowball239 commented on 2015-03-26 20:21

Hello, I have adopted and updated the glassfish-v4 package, so maybe this package is redundant now and they should be merged.

nslxndr commented on 2014-11-06 07:58

GlassFish 4.1 released, update please.

arcanis commented on 2014-09-06 21:55

Please update dependency list according to the request [1]:

jdk7-compat -> jdk7


fhtagn commented on 2013-11-29 17:41

update, glassfish v3 was updated from network to daemons

fhtagn commented on 2013-11-29 14:29


is asking for consistency a useful comment? glassfishv3 is categorized as network, this is categorized as daemons.
Also, I am thinking of installing this on a raspberry pi. Will it work?

wish commented on 2013-10-02 01:35

there is a small problem with the jdk7-compact dependency. On my system I have oracle-jdk7 package installed and it wouldn't be nice to have jdk7-compact also, but to install this package I need it.
After I have changed the PKGBUILD and glassfish.service to use oracle-jdk7 everything was working nicely. So maybe it should check if someone has ( jdk7-compact OR oracle-jdk7 ) and also the glassfish.service should be changed accordingly.

Anonymous comment on 2013-08-08 00:54

Thanks archan.paul
I updated the package per your suggestions.

archan.paul commented on 2013-08-07 14:09

Suggested to update package to make it dependent on jdk7-compat which can coexist with openjdk of ArchLinux.

[arp@arpc]$ diff PKGBUILD.orig PKGBUILD
< depends=('jdk>=7.25')
< makedepends=('jdk>=7.25')
> depends=('jdk7-compat>=7.25')
> makedepends=('jdk7-compat>=7.25')
< 'bf5a979122c3d2d16511085fb7a95307')
> '4a474d4bc85a5cd354323d71db1be01f')

[arp@arpc]$ diff glassfish.service.orig glassfish.service
< ExecStart = /opt/java/bin/java -jar /opt/glassfish4/glassfish/lib/client/appserver-cli.jar start-domain
< ExecStop = /opt/java/bin/java -jar /opt/glassfish4/glassfish/lib/client/appserver-cli.jar stop-domain
< ExecReload = /opt/java/bin/java -jar /opt/glassfish4/glassfish/lib/client/appserver-cli.jar restart-domain
> ExecStart = /opt/java7/bin/java -jar /opt/glassfish4/glassfish/lib/client/appserver-cli.jar start-domain
> ExecStop = /opt/java7/bin/java -jar /opt/glassfish4/glassfish/lib/client/appserver-cli.jar stop-domain
> ExecReload = /opt/java7/bin/java -jar /opt/glassfish4/glassfish/lib/client/appserver-cli.jar restart-domain

Anonymous comment on 2013-06-25 04:14

Start Glassfish with:
systemctl start glassfish

Then open browser to http://localhost:4848 to reach the admin console