[Quicktip] CVS-Changelog plugin for eclipse

As you know CVS is file-based and therefore it has many issues.

For example: In Eclipse (using the standard CVS-plugin) you can only see changes of the currently selected file in the history view. When you select the project, you see no history entries in the project like you are used to using SVN. I know, you can call "cvs log" to see all changes of all file, but that is not very comfortable.

A solution: Install the changelog plugin (http://code.google.com/a/eclipselabs.org/p/changelog/) and working with CVS is now easier… Internally it will call  "cvs log" and present the processed results in a clear table view manner. (See the screenshot at the project page and you will see what i mean.)

Advertisements

[Update] Monitoring tomcat instances

Here are some OSS projects to monitor your tomcat instances (f.e. memory-/cpu-usage, sessions, mbeans)

Off course you can also monitor your tomcat via VisualVM (http://visualvm.java.net/ or included in JDK6)

Update: Or use JRDS http://jrds.fr/

[Quicktip] Importing a “dependencyManagement”-section from an external artefact

Situation: You have a parent pom with defined dependencies in the “dependency management”-section. This way you do not have to provide versions for your dependencies. Standard-Maven-Stuff.

New situation: BUT for some reason you have to switch to another totally different parent pom with totally different “dependency management”-section. Your previously declared dependencies have no version, so there will be errors when invoking maven on this pom.

One solution: A cool thing you can do since Maven 2.0.9 is the import of the “dependency management”. So still no versions required for your previously declared dependencies…

This is accomplished by declaring a pom artifact as a dependency with a scope of “import”.

The offical documentation can be found here