Fixed redundant -jre dependencies and architecture dependencies and refreshed the packages in REVU queue.
Working on using the debconf to interact with the user during installation. > The "Replaces : glassfish" is being used for overwriting the /usr/bin/asadmin > so that it noe refers to glassfish v2 installation. >>ok, but back to the original question: you do package glassfishv2 with a new package name. what is the rationale about this? If I did understand you correctly glassfish >>and glassfishv2 should be able to install in parallel, so that both versions can run in parallel, and the user/administrator can easily move to the new version. If this is the >>use case, then please name the script adadminv2 and remove the Replaces. If there's not such a use case, then maybe use the same name for the source and the >>binary package. Yes, both installations can run in parallel, but GlassFish convention is for it's script to be named asadmin and hence I was using the 'Replaces:' to achieve this. I will ping the GlassFish leads to get their thoughts/take on renaming to asadmin2 or glassfishv2 to conform to the new package name. > the default domain is created in /var/lib/glassfishv2 >>then there has to be code to cleanup /var/lib/glassfishv2 on package purge. Yes, On package purge, /var/lib/glassfishv2 is cleaned up. > - Using asadmin command by a user results in creation and start of a personal domain for the user >>how? the user doesn't have permissions to do so? When a user uses asadmin, if they don't have a personal domain, the command creates it for them in the user's home directory. > - The log files for each domain are placed under the domain's directory as > per the appserver's conventions. >>in this case, these should go to /var/log/glassfishv2, with a symlink to >>/var/log/glassfishv2 where the appserver expects those. > The docs which are basically a QuickStart guide are currently in the > appserver's install location. >>The same holds for the docs. Please move them to /usr/share/doc, and if the >>appserver expects the docs in some location, then >>create symlinks to /usr/share/doc. > I would like to leave them there because the online documentation for the > glassfish v2 points users to this location. >>Well, the user uses the included documentation, which only should reference >>the locally installed documentation. The docs unfortunately are just a basic QuickStart. Most of the documentation for the server is generally published online. One other issue, is that the documentation is written in such a way that it assumes that the server is installed all in one place. I will look into what can be done. -- GlassFish V2 UR1 https://bugs.launchpad.net/bugs/191658 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
