Browse categories
Explore
Fiverr Pro
English
$
USD
I will modernize your legacy java build system, ant to maven or bazel
About this Gig
I'm a principal engineer with 20+ years in enterprise Java, and the last several have been mostly build systems and developer environments. I've converted 40 Ant modules to Maven, built Bazel integrations for VSCode, and helped launch a remote development environment that took new-engineer onboarding from two days to same-day.
Here, I audit a slow or fragile build, then migrate it from Ant to Maven or Bazel and get your CI passing on the new setup. On larger projects I can also add a devcontainer so new engineers aren't losing a day to setup.
Basic: read-only review of your build, with a written report and prioritized fix list.
Standard: migration of up to 10 modules, CI updated.
Premium: up to 40 modules, CI, a devcontainer, and docs for your team.
What I need: repo access (read-only is fine for the audit), a way to run the current build, and someone who can answer questions about it. I'm happy to sign an NDA.
Over 40 modules, or work beyond the build itself? Message me first; I'll put together a custom offer.
Tools:
Docker
•
Jenkins
•
GitHub
•
Maven
•
Gradle
•
BitBucket
•
Kubernetes
Frameworks:
Npm
•
Terraform
•
Ansible
Programming language:
Bash
•
Java
•
JavaScript
•
Kotlin
•
Python
•
Golang
Expertise:
Migration
•
Debugging
•
Development
FAQ
Which build tools and languages do you work with?
Mostly Java projects moving from Ant to Maven or Bazel. If you're on something else (Gradle, Make, a homegrown script), message me first; I'll tell you honestly whether it's a fit.
Do you need access to my private code?
Yes, past a surface look. Read-only access is enough for the audit; a migration needs a branch I can push to. I'm happy to sign an NDA first, and I delete my local copies after delivery.
Will my current build keep working during the migration?
That's the goal. I work on a branch and leave the old build alone until the new one produces the same artifacts and passes your CI; then you decide when to switch.
Should I start with the audit or go straight to a migration?
If you already know you want off Ant, go to Standard. If the build is just slow or nobody understands it, start with the audit; the report tells you what to fix and in what order.
Do you fix application code that breaks?
Only what the build requires (dependency versions, module layout, test wiring). Bug fixes and feature work are outside these packages; message me and I can quote them separately.
My project has more than 40 modules. Can you still help?
Yes, but not through these packages. Send me a message with the repo size and current build tool, and I'll put together a custom offer.
