-
I installed the plugin manually and found that one of the problems is the use of an internal jface viewer api that is no longer present 3.5. Attached is a patch to fix that problem.
2009-10-09 10:28:26 UTC in Dozer
-
I tried installing the plugin on Eclipse 3.5 and received a different error. Apparently the plugin is looking for a specific version of the Spring bundle included with the Spring IDE plugin. Apparently the current version of the Spring plugin has changed the name of its components so the Dozer plugin will not install.
2009-07-11 07:53:34 UTC in Dozer
-
Is there any update to this issue? I would love to be able to use the Eclipse plugin.
2009-07-09 05:40:19 UTC in Dozer
-
Now that I can access the update site, Eclipse says that it cannot install the plugin because:
"Cannot find a solution satisfying the following requirements org.eclipse.debug.ui [3.4.0.v20080529-1300]."
This is on Eclipse 3.4.2 on a Mac running 10.5.7.
2009-07-01 06:35:31 UTC in Dozer
-
Eclipse reports that http://dozer.sourceforge.net/eclipse-plugin is not a plugin site.
2009-06-27 08:37:08 UTC in Dozer
-
Accidental dup.
2009-06-21 04:32:36 UTC in checkstyle
-
The RequireThis check still marks static fields as requiring a "this" prefix. Obviously that is not correct. In fact if you turn on Eclipse's built-in check for requiring "this", which works correctly, you will end up in a situation where you will make Checkstyle happy by adding "this" to a static filed and make Eclipse unhappy because you added "this" to a static field.
2009-06-21 04:31:50 UTC in checkstyle
-
The RequireThis check still marks static fields as requiring a "this" prefix. Obviously that is not correct. In fact if you turn on Eclipse's built-in check for requiring "this", which works correctly, you will end up in a situation where you will make Checkstyle happy by adding "this" to a static filed and make Eclipse unhappy because you added "this" to a static field.
2009-06-21 02:31:19 UTC in checkstyle
-
I separate my unit test source code from my production source code by placing them in separate top level directories. However, to allow testing package level classes and methods, I use the same package for the production source and unit tests. Unfortunately, this confuses the JavadocPackage check. The check flags the package containing the unit tests as not having a package-info.java even though...
2009-06-21 02:22:51 UTC in checkstyle
-
When unit testing a class that implements equals I always pass in null to the equals method to ensure things don't blow up. For example:
assertFalse(foo.equals(null));
The EqualsAvoidNull check flags this as if null is a string literal.
2009-06-21 02:04:09 UTC in checkstyle
