The current version of Eclipse (Kepler as of writing) doesn’t natively support version 8 of the Tomcat server. Although support will be added eventually, this is not likely to be until the release of Eclipse Luna in late June 2014. In the meantime, to add support you can download and install the latest version of the WTP (Web Tools Platform) into your current Eclipse environment.
Go to the WTP Downloads Page and select the link to the latest release (easiest to look at the most recent build date). As of writing the latest version is 3.6.0.
Under the ‘Traditional Zip Files’ section, download the .zip file for Web App Developers.
Extract the archive somewhere and copy all of the files in the ‘features’ and ‘plugins’ directories’ into the corresponding directories in your Eclipse folder (overwriting the existing files).
That’s it. Open up Eclipse and you should see the option for a Tomcat 8 server.
When using any version control system it’s inevitable that you’re going to make some kind of mistake when writing out your commit messages. Luckily Git makes it extremely simple to change the message of your most recent commit. Simply use the amend command:
git commit --amend -m "new message"
For example given this test repository with three previous commits:
To change the message of the most recent commit - in this case “Third commit”, you can use git commit --amend -m "This is a modified message"
A lot of the time when viewing the log in your Git repository you aren’t that interested in the author and date/time of each commit - the message and the hash are the most important parts. It would therefore be helpful to cut out everything from the log apart from the main details of each commit. Luckily, just like most things in Git, this is pretty straightforward to do:
git log --pretty=oneline
Which will output something like:
This is all well and good, yet the hash is pretty long and distracted. Again however there is a way around that as well:
git log --pretty=oneline --abbrev-commit
This time we only get a fraction of the hash for each commit (which is all we really need) and the message - much better!
It happens all so often nowadays in movies -; an extremely smart character writes some really complex bit of code that nobody else can understand in order to hack into some system or otherwise perform some other complicated task.
Quite often we get a good look at the code they are using -; which often looks very obfuscated -; and we just accept it for what it is. But now someone has taken the time to figure out where the code they use in films and TV shows actually comes from. As it turns out the code they are actually use isn’t all that complicate at all -; and in most cases isn’t at all related to the task in hand.