Delete iPOJO

[wilx]

TL;DR: Delte iPOJO.

Reverse-dependency analysis

Activity was checked on 2026-08-24. The reverse-dependency data was collected for every Apache Felix iPOJO artifact found in this repository and every version indexed by deps.dev. Apache Felix artifacts themselves were then excluded.

The resulting data contained 743 dependency relationships from 331 distinct external artifacts.

OW2 projects

• 549 of 743 dependency relationships were from OW2: 73.9%.
• 227 of 331 distinct dependent artifacts were from OW2: 68.6%.
• The six largest OW2 families accounted for 528 of the 549 OW2 relationships: 96.2%.

OW2's official repository registry classifies all the major projects below as archived.

Project family	Relationships / artifacts	Website and repository	Activity
Fuchsia	168 / 60	Historical wiki.chameleon.ow2.org is unavailable; GitHub repository	Repository archived; last commit August 2016. Latest affected artifact release: January 2015.
JASMINe	127 / 45	Historical wiki is unavailable; OW2 source archive	No active public repository; the current OW2 GitLab group is empty. Latest affected release: October 2013.
JOnAS/JPaas	96 / 45	JOnAS website; OW2 GitLab repository	Website survives but is stale. Last source commit April 2014; latest affected release October 2013.
Kerneos	56 / 21	Historical kerneos.ow2.org is unavailable; OW2 source archive	Archived; latest affected release October 2013.
Chameleon, excluding Fuchsia	46 / 23	GitHub core repository	OW2 marks the project archived. The last default-branch commit was a Dependabot JUnit update in October 2020; latest affected release December 2015.
Shelbie	35 / 15	Historical shelbie.ow2.org is unavailable; OW2 source archive	Archived; latest affected release August 2013.
Orchestra	7 / 5	Historical orchestra.ow2.org is unavailable; OW2 source archive	Archived; latest affected release November 2012.
Sirocco Cloud Manager	5 / 4	GitHub organization; Cloud Manager repository	OW2 marks it archived; last commit September 2015. Latest affected release November 2013.
Fractal Binding Factory	4 / 4	Current Fractal site; GitLab group	Fractal's Juliac project is active in 2026, but the affected Binding Factory artifacts belong to the deprecated legacy tree. Their latest release was March 2013.
EasyBeans	3 / 3	Historical easybeans.ow2.org is unavailable; OW2 source archive	Current GitLab group is empty. Latest affected release September 2013.
Two OW2 utility artifacts	2 / 2	Bnd iPOJO plugin and OSGi SPI Registry	Both were published in 2013; no separate active project was found.

None of these exact 227 OW2 artifacts has received a release since December 2015. Fractal is the only family with current development, and that activity is in Juliac rather than the Binding Factory artifacts referencing iPOJO.

Remaining projects

After excluding OW2 and synthetic MyPOJO test artifacts, 188 dependency relationships from 101 distinct artifacts remained.

Project	Relationships / artifacts	Activity	iPOJO in latest/current source?
Wisdom Framework	105 / 44	Dormant. The main release was in 2017; Wisdom JCR 0.5.0 was released in September 2022, with no subsequent commits.	Yes. Current source still specifies iPOJO 1.12.1 and includes its iPOJO module and Maven plugin in the root POM.
SAlly4	52 / 33	Apparently inactive. Latest release was 1.0.0 in February 2015; its declared GitLab repository now requires authentication, with no visible public activity.	Yes in its final release. The 1.0.0 artifacts still depend on iPOJO 1.12.1.
Roboconf	13 / 10	Dormant. Latest Maven release was 0.9.1 in 2017; the last default-branch commit in 2022 only changed website URLs.	Yes. Current master still declares iPOJO 1.12.1 and maven-ipojo-plugin in its POM.
Faerie	5 / 5	Inactive; latest release was 1.2.9 in July 2012.	Yes in its final release. The 1.2.9 configuration still includes the iPOJO extender handler.
Velossity	5 / 2	Inactive; latest release was 1.0.14 in February 2015.	Yes in its final release. iPOJOAdapter is explicitly an iPOJO sample and depends on the runtime and Maven plugin in its published POM.
Chameria	3 / 3	Inactive; last source commit was February 2012.	Yes. Its frozen source still contains iPOJO imports and dependencies.
Gradle iPOJO plugin	2 / 1	Inactive; final publication was 1.2.0 in December 2016.	Final artifact: yes. Current upstream: no. The old plugin depends on the iPOJO manipulator, but current osgi-run merely has it commented out.
Apache Axiom	1 / 1	Active in 2026.	No. The relationship comes from the old axiom-osgi-build:1.2.9; current Axiom source contains no iPOJO reference.
GlassFish JAXB RI	1 / 1	Active in 2026.	Yes, test-only. The latest 4.0.9 release source still depends on org.apache.felix.ipojo.junit4osgi:1.0.0, but explicitly excludes the iPOJO runtime. OSGi tests are skipped by default.
Spring Roo	1 / 1	Inactive and archived.	No. Only the old 1.3.1 bootstrap artifact used iPOJO; the final source does not.

Wisdom Framework, SAlly4, and Roboconf account for 170 of the 188 remaining relationships, but all three are dormant. Axiom and JAXB RI are the only clearly active projects. Axiom has removed iPOJO; JAXB RI's sole verified current use is limited to the obsolete junit4osgi test harness rather than production component wiring.

Repository changes

• Delete the complete self-contained ipojo/ reactor: 1,972 tracked files.
• Remove iPOJO from the top-level project list.
• Preserve historical changelog entries and generic documentation references to previously released iPOJO artifacts.

There were no iPOJO dependencies or module references in build files outside the deleted subtree.

Validation

• Confirmed that no iPOJO references remain in POMs, Gradle files, Bnd files, Bnd run descriptors, properties files, or build XML outside deleted historical content.
• env JAVA_HOME=/opt/jdks/latest-17 nice -n 10 /opt/maven/latest/bin/mvn -B -V -Dstyle.color=always -f pom/pom.xml clean verify
  • Maven 3.9.16
  • Java 17.0.16
  • BUILD SUCCESS