v0.1.3

Nothing in the free tool changed. The jar behaves exactly as 0.1.2 did; the version moves because the build is versioned as a whole. If you are using adfmig to assess an estate, there is no reason to upgrade.

What is new is in the paid half: a backlog export. The migration checklist written beside a generated project is addressed to the developer who will do the work — every finding, in place, with the file to open. That is the wrong shape for whoever decides who does it and how long it takes: one real application produces 180 rows, and nobody plans against 180 rows.

--backlog jira|gitlab|trello now also writes a CSV those tools import, where one ticket is one finding in one file rather than one occurrence, grouped by the kind of work rather than by the code that found it. On that application it turns 180 findings into 77 tickets. It writes a file rather than calling an API, so it needs no token and creates nothing twice.

---

Requires JDK 21 or later.

java -jar adfmig-0.1.3.jar apps ~/adf

Assessment, with no limits. Generating the Spring Boot project is adfmig Pro.

Full Changelog: v0.1.2...v0.1.3

v0.1.2

Requires JDK 21 or later.

java -jar adfmig-<version>.jar apps ~/adf

Assessment, with no limits. Generating the Spring Boot project is
adfmig Pro.

Full Changelog: https://github.com/trippysolutions/adfmig/commits/v0.1.2

v0.1.1

Requires JDK 21 or later.

java -jar adfmig-<version>.jar apps ~/adf

Assessment, with no limits. Generating the Spring Boot project is
adfmig Pro.

Full Changelog: v0.1.0...v0.1.1

v0.1.0

Requires JDK 21 or later.

java -jar adfmig-<version>.jar apps ~/adf

Assessment, with no limits. Generating the Spring Boot project is
adfmig Pro.

Full Changelog: https://github.com/trippysolutions/adfmig/commits/v0.1.0