Community
Participate
Working Groups
we have 9 copies in the SDK ! jface is independent from core so we should at most need 2
There's no point exposing Assert now that we are using JDK 1.4. You can now use the assert keyword.
the assert keyword is bogus - you have to _explicitly_ turn on the runtime check for it. that means we will not delete the 9 Assert classes that we have.
Reopening for consideration
The org.eclipse.core.runtime.Assert class has been exposed as a public API by the org.eclipse.equinox.common plugin and re-exported by the org.eclipse.common.runtime. The "other" Assert's are present in the: org.eclipse.jdt.core.tests.builder org.eclipse.core.internal.expressions org.eclipse.core.internal.runtime org.eclipse.jdt.internal.core org.eclipse.jdt.internal.corext org.eclipse.test.internal.performance.data org.eclipse.ui.internal.misc org.eclipse.update.internal.core org.eclipse.webdav.dom org.eclipse.webdav.internal.kernel.utils (+ 2 Jface cases that probably can be combined) Plus, the AssertionFailedException now exposed as an API in the same way and is duplicated by: org.eclipse.core.internal.expressions org.eclipse.jdt.core.tests.builder org.eclipse.webdav.internal.kernel.utils org.eclipse.jdt.internal.compiler.flow org.eclipse.jdt.internal.core org.eclipse.test.internal.performance.data org.eclipse.webdav.dom
Oleg could you please open bug reports against the various components that still use Assert (even better provide patch) and then close this bug.
The Assert and AssertionFailedException are now provided by the org.eclipse.equinox.common plugin (package org.eclipse.core.runtime). I recorded individual bugs for the plugins in the eclipse.org repository that depend on org.eclipse.equinox.common and provide they own copies of Assert or AssertionFailedException classes: Bug 135110 Bug 135134 Bug 135135 Bug 135136 Bug 135139 Bug 135140
Filed bug 155788 for org.eclipse.jface.util.Assert.