# TIP: Using Lombok and Other tools

DevFeed: [TIP: Using Lombok and Other tools](<https://devfeed.tech/articles/tip-using-lombok-and-other-tools-19611.md>)

Original publisher: [Read original article](<https://www.codenameone.com/blog/tip-using-lombok-other-tools/>)

Author: Shai Almog

Published: 2017-10-09T00:00:00Z

Content type: tutorial

Language: en

Sources: [CodeName One](<https://devfeed.tech/sources/codename-one.md>)

Topics: [Java](<https://devfeed.tech/topics/java.md>), [Tool](<https://devfeed.tech/topics/tool.md>), [Code](<https://devfeed.tech/topics/code.md>)

Tags: [bytecode](<https://devfeed.tech/tags/bytecode.md>), [compiler](<https://devfeed.tech/tags/compiler.md>), [java](<https://devfeed.tech/tags/java.md>), [tools](<https://devfeed.tech/tags/tools.md>)

## AI overview

This tutorial explains that Lombok can be used with Codename One without code changes and outlines how to add it to a project's build path and classpath. It also notes that other static code-manipulation tools may work similarly.

## Source excerpt

A few weeks back maaartinus asked on stack overflow whether we can get lombok working with Codename One. After a short back and forth it seems that this was as easy as I'd hoped and he was able to get it working without a change. Personally, I like our approach of property objects more but that's obviously a matter of taste. Lombok works by processing the bytecode after compilation to convert annotations to terse code. E.g. this Java code using Lombok: