# Don't use junit.framework

DevFeed: [Don't use junit.framework](<https://devfeed.tech/articles/don-t-use-junit-framework-37702.md>)

Original publisher: [Read original article](<https://carlosbecker.com/posts/dont-user-junit-framework/>)

Author: Carlos Alexandro Becker

Published: 2014-12-14T00:00:00Z

Content type: tutorial

Language: en

Sources: [Carlos Becker](<https://devfeed.tech/sources/carlos-becker.md>)

Topics: [Maven](<https://devfeed.tech/topics/maven.md>), [deprecated](<https://devfeed.tech/topics/deprecated.md>), [Code](<https://devfeed.tech/topics/code.md>)

Tags: [classes](<https://devfeed.tech/tags/classes.md>), [configuration](<https://devfeed.tech/tags/configuration.md>), [deprecated](<https://devfeed.tech/tags/deprecated.md>), [import](<https://devfeed.tech/tags/import.md>), [junit](<https://devfeed.tech/tags/junit.md>), [maven](<https://devfeed.tech/tags/maven.md>), [maven-plugin](<https://devfeed.tech/tags/maven-plugin.md>), [org](<https://devfeed.tech/tags/org.md>), [script](<https://devfeed.tech/tags/script.md>)

## AI overview

The article recommends replacing deprecated junit.framework imports with org.junit imports and preventing old imports from entering new code. It suggests using a Bash script for replacement and restrict-maven-plugin configuration to fail builds that contain the old imports.

## Source excerpt

Every once in a while I see somewhere a wrong import to the old, deprecated junit.framework instead of org.junit.