Hi JP, what do you mean by "portable JSPWiki binaries for several
OS/platforms"? JSPWiki, being Java, is already portable. I hope it is
not your intention to start distributing application servers such as
Tomcat, we are not in a position to be securing application servers on
everybody's machines nor can we responsibly distribute Tomcat
instances--that's not our job--that's the job of the person choosing to
host JSPWiki, and if he is not smart enough to be able to securely
deploy Tomcat (and keep it maintained with all the necessary patches and
PKI infrastructure, etc.) or to get professional hosting then he has no
business deploying JSPWiki.
What you're describing below seems like a *lot* of maintenance, trying
to keep everything constantly in sync with the latest patches as the
months go on--this team is probably not large enough to be able to
support completely what you're envisioning, and we enjoy coding web
apps, not maintaining web servers. Try to come up with something more
modest and reasonable that a small team can support over a many-month
period--the energy burst you're having now may not be around six months
from now, or may be diverted to other things. Then again, maybe I'm
overconcerned here--I'm not fully understanding what you're envisioning.
Regards,
Glen
On 02/19/2014 07:15 PM, Juan Pablo Santos Rodríguez wrote:
Hi,
I've just committed a new module, meant to generate portable JSPWiki
binaries for several OS/platforms. It isn't integrated into main build yet,
as this is only a first step and there are still things to do. Some
module-related notes (also reachable at
https://jspwiki-wiki.apache.org/Wiki.jsp?page=PortableBinaries):
* based on Siegfried Goeschl's JSPWiki On A Stick [#1]
* not integrated yet into main build, as there is still room for improvement
** just go into jspwiki-portable, run mvn clean install and check inside
target folder
* almost all application files get generated inside ./wiki-files
* right now, only windows portable binaries, although should be easily
extendable to other platforms
** need help here to develop required custom scripting for other OS (should
be easy) and specially for testing outside Windows/Cygwin
*** f.e. JSPWiki On A Stick has some env-specific folders, which seem not
to be used (i.e. [#2], @Siegfried: what are those files and for what are
they used for?)
* almost sure launch4j configuration can be improved:
** tomcat extracts the app into a .extract folder. This can be customized,
by passing "-extractDirectory ./wiki-files/" to the jar execution (at least
according to [#3])
** multiwiki support? we can use a custom tomcat's server.xml file (help
here!)
** how to load/deploy an initial page repo?
** upgrade bundled tomcat to latest? (example at [#3], seems a little
overkill)
* launch4j expects a certain directory structure, which renders the maven
plugin unusable. Hence the use of a custom Ant script
** see woas:app target on build.xml and maven-dependency-plugin usage on
pom.xml
br,
juan pablo
[#1] https://github.com/sgoeschl/jspwiki-on-a-stick/
[#2]
https://github.com/sgoeschl/jspwiki-on-a-stick/tree/master/extensions/woas/resources/macos
[#3]
http://nurkiewicz.blogspot.com.es/2012/11/standalone-web-application-with.html
