File | Date | Author | Commit |
---|---|---|---|
.settings | 2017-01-02 |
![]() |
[27ff28] move to Java 8 |
META-INF | 2022-04-01 |
![]() |
[5e807a] release 1.2.8 - renew certificate |
lib | 2017-08-21 |
![]() |
[35f069] new release using ~80% faster base macker |
qisserver | 2012-09-14 |
![]() |
[aa021d] change default location of rules to make macker... |
src | 2017-08-22 |
![]() |
[4373c5] text format |
.classpath | 2017-08-21 |
![]() |
[35f069] new release using ~80% faster base macker |
.gitignore | 2014-07-28 |
![]() |
[a38443] ignore bin |
.project | 2016-06-06 |
![]() |
[f25f27] do not build the plugin itself with macker |
README.md | 2017-02-27 |
![]() |
[4cb26c] new 1.2.4 release |
build.properties | 2017-08-21 |
![]() |
[35f069] new release using ~80% faster base macker |
plugin.xml | 2016-05-30 |
![]() |
[a5bd11] fixed bug 02 by adding relative-attribute to vi... |
The Eclipse Macker Plugin displays warnings and errors about architectural violations discovered by Macker right in Eclipse.
Since release 1.2.4, Eclipse Macker requires Java 8. This is a consequence of Eclipse needing Java 8 since version 4.6 (Neon).
Macker is a Java developers' utility which checks classes against user-defined structural rules. It's meant to model the architectural ideals programmers always dream up for their projects, and then break -- it helps keep code clean and consistent. You can use it to check general "good practice" rules, and you can also tailor a rules file to suit a specific project's structure.
The Macker Eclipse Plugin allows Macker to be used within the Eclipse IDE.
Read more about what it does and what it's for here: http://innig.net/macker/faq.html .
To get started, use the "Project->Clean.." command. The Plugin will run, and problem markers will point to locations in your code which have been identified as architectural violations.
You may customize how the plugin runs by opening the Properties dialog for a Java project