This is somewhat embarrassing, but I'm totally lost when it comes to upgrading from Jetty 9.2 to 9.4. 9.2 was installed two years ago using jetty-9.2.0-setup-package.zip. The file contained commons-deamon and more so that the install could be done using command
create-jetty-dist.bat d:\jetty9 Jetty9 80 50001 D:\etc\gateway NO
Now I've downloaded the latest version from https://www.eclipse.org/jetty/download.html]1 - jetty-distribution-9.4.14.v20181114.zip - but, I cannot figure out how to upgrade the installation. Mostly I find docs about Maven and update the POM, but the installation is standalone and no Maven. There is a Chapter 36. Upgrading Jetty about upgrading - but still does not help much
All my Google-skills does not help either.
I have not found the guts yet to simply replace the folder
D:\jetty9\jetty
Maybe I do overthink and the solution is that simple. But still it keeps bugging me that I cannot seem to find an install file for 9.4 like I did for 9.2
I did overthink - is was almost only to replace the 9.2 distribution folder with the 9.4. But for the service to be reconfigured and also to ensure that all changes from 9.2 to 9.4 was implemented me and my colleague had to do:
Edit the .bat file that came with the jetty-9.2.0-setup-package to support 9.4
Off course change the reference for all 9.2 to 9.4 distribution in the script
9.2 used "logging", 9.4 uses "console-capture"
9.2 used "jetty.port", 9.4 uses "jetty.http.port"
Copy the 9.4 distribution file to the folder where the .bat-file is to be found in the setup-package
Then we sc delete jetty9 the service and ran the script.
In short, that was what we needed to do.
Related
Im moving to Apache Netbeans 11.3 and trying to install the C++ plugin on Windows 10, got the follow repos
http://updates.netbeans.org/netbeans/updates/8.2/uc/final/distribution/catalog.xml.gz
http://bits.netbeans.org/dev/nbms-and-javadoc/lastSuccessfulBuild/artifact/nbbuild/nbms/updates.xml.gz
but everytime it hits the 99% it simply give me a timeout error when unpacking org-netbeans-modules-cnd-dwarfdiscovery.nbm
The Plugin Installer found problem timeout of loading C/C++ Repository[org.netbeans.modules.cnd.repository/1.32.6.1] while install the following plugins:
already try versions 10, 11.1, 11.2, 11.3, got the same issue, i even got rid of the windows firewall to no avail.
Check the Java version
For me, I have Java version 14
So this version has no program
unpack200.exe
Problem was solved by copying the unpack200.exe file from Java version 1.8 to the bin folder in java 14
copy and paste pack200, unpack200 and unpack.dil from bin of jdk13 into the bin of jdk14. This worked for me and I assure you that it will work for you. I did this with openjdk.
I am trying to run the GrassGIS modules on external python scripts on a ms windows server 2016 standard. What ever I do (experimenting with different installations of Grass, changing environmental variables, changing python code) - it won't run.
I have tried to run installation with OSGEO4W and standalone version. in 7.2 , 7.4 and 7.6 (7.6 unintentionally as it installed 7.6 despite reading 7.4
(svn checkout https://svn.osgeo.org/grass/grass/branches/releasebranch_7_4 grass74_release >>on https://trac.osgeo.org/grass/wiki/DownloadSource).
I have also experimented with all different recommendations for environmental variables I found online - however, I cannot get it to run.
enter image description here
Any Help - So much appreciated!!!!
I have installed the latest version of Weka(3.9.3). I have also ensured that both Java and MacOS are up to date on my machine.
When I double-click the Weka icon to open it, it bounces for a few seconds and never opens.
I have downloaded Weka 3.8.3 to see if that makes any difference, but the same thing happened.
Any ideas on why this is happening?
I was facing a similar issue but it worked for me when I start weka on the command line.
Change directory into the weka-3-8-0 directory
cd /Applications/weka-3-8-0
invoke the jvm with the weka.jar file located in the above directory
java -jar weka.jar
We have identified the issue with the WEKA 3.8.3 and WEKA 3.9.3 applications for the Mac that, for many users, caused them to fail to start up via double-clicking.
On December 13, we replaced weka-3-8-3-oracle-jvm.dmg and weka-3-9-3-oracle-jvm.dmg on SourceForge with a new .dmg compatible with older versions of OS X, based on the HFS+ file system. Unfortunately, this new “release" included a pre-17 December 2018 version of the Amazon Corretto JVM 1.8.0_192 instead of the Oracle Java VM we had used before. Unfortunately, that particular version of Amazon’s Corretto had a bug on Macs:
"The libfontmanager in Corretto is linked to the libfreetype in X11 and breaks when X11 is not installed."
See https://docs.aws.amazon.com/corretto/latest/corretto-8-ug/change-log.html.
We never noticed this problem and could not reproduce it because if, like us, you had XQuartz installed, or the libfreetype.dylib library was installed on your Mac via Homebrew, the WEKA application still worked in spite of this bug.
We have reproduced the problematic behaviour by removing XQuartz and Homebrew on one of our Macs. And, indeed, the WEKA macOS application no longer started when the bird was double-clicked.
We have just made new “releases” of the WEKA 3.8.3 .dmg and the WEKA 3.9.3 for the Mac that use the latest version of Corretto 8 (8.212.04.2). You can find these .dmg files at
https://sourceforge.net/projects/weka/files/weka-3-8/3.8.3/
and
https://sourceforge.net/projects/weka/files/weka-3-9/3.9.3/
respectively.
They are called
weka-3-8-3-corretto-jvm.dmg
and
weka-3-9-3-corretto-jvm.dmg
respectively.
We have also replaced the links for the Mac applications on the main WEKA downloads page at
https://www.cs.waikato.ac.nz/ml/weka/downloading.html
I am new to Linux. I have been asked to install rose compiler. I installed the dependency Boost by using
apt-get install libboost-all-dev
which installed boost1.58.0 but now when I use
apt-cache search rose
I cant understand which package is for the rose compiler from the list provided. I downloaded rose from the github repository https://github.com/rose-compiler/rose but I cant understand how to install it.
The ROSE installation process is a mangled mess. If you can, use their pre-built image. If you can't, I'd recommend running this shell script instead. Note that the part with downloading Java does not work, so before running the script download JDK 7u51 from Oracle and leave it in the Downloads folder (do not move or rename!) for the script to pick up. This was working as of ~1 month ago (July 2017). No guarantees if it still works.
Also note that the installation process takes a lot of time. The entire ~2 million line project needs to be compiled on your machine. After installation, don't even think about moving any of its folders or dependencies. Best of luck.
If you are using Ubuntu 18.04 or CenOS/RHEL 7 then you can install rose using apt/yum. https://github.com/rose-compiler/rose/wiki/How-to-Set-Up-ROSE has all the information regarding this.
i installed jetty (distribution-9.0.2) on ubuntu server 12.04
from these links step by step
http://degreesofzero.com/article/19
http://pietervogelaar.nl/ubuntu-12-04-install-jetty-9/
at last when i start jetty with the following command:
sudo /etc/init.d/jetty start
or
sudo service jetty start
i get the following error
Starting Jetty: grep: /var/run/jetty.state: No such file or directory
I'm facing with the same problem but on Debian 6 server. Workaround for this problem and articles above, from my perspective, is:
use JETTY_ARGS=jetty.port=8080 instead JETTY_PORT
Add property to /etc/init.d/jetty: JETTY_PID=/opt/jetty/jetty.state
Please, let me know if you have any questions
I've tested this thoroughly with the latest release of jetty and it's working fine. There's been some changes recently in the jetty.sh script. However the changes look good to me and it's working fine for me with the latest release.
Evgenly is right, that JETTY_PORT is deprecated (see comments in jetty.sh for details), however it also works fine for me using JETTY_PORT instead of JETTY_ARGS to define a non standard port.
Please try the latest release from here in case you didn't do already:
http://download.eclipse.org/jetty/
If jetty.sh reports that the start failed, you'll usually find the reason in stderrout.log inside the JETTY_HOME/logs directory (unless you've changed the logging config).