it compiles against spring 2.0 and pulls this in as well, but I have no idea why it does it. I've now removed the specific version so we fall back to the spring version defined in the parent pom. I also upgraded it to the latest 5.3.x which also seems a bit outdated already.
So probably even keep it and just modernise the plugin? LieGrue, strub > Am 27.07.2026 um 10:05 schrieb Romain Manni-Bucau <[email protected]>: > > Think there were some other usages but also think they are all legacy and > unlikely to use any new release (not even sure v3 was used) so +1 from me > > Romain Manni-Bucau > @rmannibucau <https://x.com/rmannibucau> | .NET Blog > <https://dotnetbirdie.github.io/> | Blog <https://rmannibucau.github.io/> | > Old Blog <http://rmannibucau.wordpress.com/> | Github > <https://github.com/rmannibucau> | LinkedIn > <https://www.linkedin.com/in/rmannibucau> | Book > <https://www.packtpub.com/en-us/product/java-ee-8-high-performance-9781788473064> > Javaccino founder (Java/.NET service - contact via linkedin) > > > Le lun. 27 juil. 2026 à 09:28, Mark Struberg via dev <[email protected] > <mailto:[email protected]>> a écrit : >> hi! >> I created https://issues.apache.org/jira/browse/XBEAN-362 for removing the >> maven plugin from xbean. >> >> Please should out if one is still using it (which I doubt). >> Afaiu the maven-xbean-plugin exists to create spring XML definitions for >> spring 2. This is stone old and not a supported spring environment for more >> than a decade. >> >> We should imo just remove it. It is btw also named wrongly. Since around >> 2008 a convention exists that only Maven own plugins should be named >> maven-*-plugin. Other projects should use project-maven-plugin as naming >> scheme. >> >> >> >> LieGrue, >> >> strub >> >> >>
