· 1 observation
Technical updates · 1
Package or technical metadata updated
View technical comparison →Vitor Hugo Alves Ferreira v1.0.5
Build legacy JRXML
From the developer
Not specified in the available declarations: limitations, pricing & account requirements.
Create a JasperReports 2.x JRXML form from an official PDF.
Developer declarations; not independently tested. Listing last checked Nov 22, 2026. Package observed Nov 21, 2026.
From the marketplace listing
Create, inspect, compile, and validate dense legacy iReport and JasperReports 2.x JRXML reports without silently introducing incompatible modern syntax.
Language: English · Automatically detected from descriptions.
· 1 observation
Package or technical metadata updated
View technical comparison →· 2 observations
Package or technical metadata updated
View technical comparison →· 2 observations
Package or technical metadata updated
View technical comparison →Package or technical metadata updated
View technical comparison →Finding similar plugins… Results will appear here automatically.
Browse plugins →--- name: jasper-jrxml description: Use when creating, editing, inspecting, compiling, or validating complex legacy iReport/JasperReports JRXML reports, especially JasperReports 2.x/2.0.4, old DTD-based templates, dense official forms, absolute-position layouts, subreports, or .jrxml to .jasper compilation. license: MIT --- # Legacy iReport/JasperReports JRXML Build high-fidelity complex reports for **legacy iReport/JasperReports 2.x**, especially **JasperReports 2.0.4** and old DTD-based JRXML. Treat modern JasperReports features as incompatible until the consuming project's legacy compiler proves otherwise. Compatibility requires file access and a shell. The bundled compiler targets Windows/PowerShell with JDK 8 and project-provided JasperReports 2.x dependencies. ## Read first - Read [`references/legacy-jrxml-layout.md`](references/legacy-jrxml-layout.md) before authoring or changing a dense fixed-layout report. - Read [`references/project-integration.md`](references/project-integration.md) before wiring fields, parameters, subreports, data sources, deployment paths, or runtime loading. - Read [`references/official-report-sources.md`](references/official-report-sources.md) before downloading or inspecting official forms and JasperReports examples. - Read the consuming project's `docs/report/` Markdown files before changing an existing report. These contain validated local conventions and corrections. Paths in this skill are relative to the root of the **consuming project**, unless explicitly stated otherwise. ## Scope - Author `.jrxml` by cloning the nearest compatible project model and rewriting only the necessary section. - Reproduce dense official forms with numbered fields, boxes, dividers, checkboxes, rotated sidebars, and absolute coordinates. - Compile and validate `.jrxml` into `.jasper` with the project’s exact legacy JasperReports dependencies. - Integrate fields, parameters, subreports, data-source keys, runtime lookup, and optional deployment without assuming a particular application structure. ## Mandatory compatibility rules 1. Detect the JasperReports/iReport version and JRXML header/DTD before editing. 2. Prefer a report already compiling in the same project as the model. 3. Do not migrate DTD-based JRXML to a modern schema unless explicitly requested. 4. Do not introduce components, attributes, expressions, or Java APIs that the legacy compiler has not accepted. 5. Compile after every meaningful layout or expression change. The compiler is the structural validator. 6. Generate a PDF in the consuming application and compare it with the source form; compilation alone does not prove visual fidelity. ## Prerequisites for JasperReports 2.0.4 - A **JDK 8** installation. Very old JasperReports expression compilers may fail on newer modular JDKs. - The consuming project's compatible JasperReports and transitive jars, including the XML parser dependencies it actually uses. - A project build or dependency directory that provides those jars. - PowerShell for the bundled headless compiler driver. Never download random legacy jars into a private project without checking its build and license constraints first. Prefer the dependency set already proven by that project. ## Compile and validate Use [`scripts/compile-jrxml.ps1`](scripts/compile-jrxml.ps1): ```powershell pwsh -NoProfile -File path/to/jasper-jrxml/scripts/compile-jrxml.ps1 ` -Jrxml "reports/complex-form.jrxml" ` -ProjectRoot "." ` -LibDirectory "target/app/WEB-INF/lib" ``` Optionally publish the compiled artifact to one runtime directory: ```powershell pwsh -NoProfile -File path/to/jasper-jrxml/scripts/compile-jrxml.ps1 ` -Jrxml "reports/complex-form.jrxml" ` -ProjectRoot "." ` -LibDirectory "target/app/WEB-INF/lib" ` -DeployDirectory "src/main/webapp/WEB-INF/reports" ``` Use `-JdkHome` when JDK 8 is not discoverable. Use `-AdditionalClasspath` for required jars outside `-LibDirectory`. The `.jasper` is written beside the `.jrx
Preview of the first 4,000 characters. Read full instructions →
Referenced files: 8 — file references are metadata, not package contents.
Publisher declarations from the archived package. These are separate from our research and the live service's terms.
Package observed Nov 21, 2026.
plugins_6a739d78d3a4819189ca29a5f7ab389f
Download plugin data (JSON)Plugin details: freshly prepared. Prepared . Refreshed when plugin data changes or after 6 hours. Your account and Follow status are live.