Howdy, Something is wrong here... You want to _extend_ sisu-plexus-shim, codebase that is here to buy out (functionally) old Plexus Containers? The one meant to be a drop-in replacement for legacy Plexus containers? Given we have STILL mixed use of sisu-plexus-shim and "original" plexus-container, having them "drift away" from each other is just opening a big door for problems.
If not proactively working on Plexus Container removal (so not proactively moving to JSR330), then at least keep that code _frozen_, as investing/extending shim-legacy codebase (sisu-plexus) meant to be removed is something I cannot understand, I'd rather look into hooking in Guice TypeConverter SPI than using Plexus oldie AbstractBasicConverter (that servers as superclass of mentioned FileConverter) Ultimately, what's wrong with making that parameter a String and invoke Paths.get(string) with it? We should be by now in blue box, while to me it seems we keep insisting (and extending) red box: https://imgur.com/a/sc3rwPK Re Sisu project: it is healthy and all fine, thanks, 1.0 planned release is soon to come. But given Plexus Shim (shim!) is in place as "compatibility layer", there is not much sense in investing into it, it played it's role, it bought out p-c-d for all these years, but it's role is NOT to become yet-another p-c-d instead of p-c-d. Thanks T On Sat, May 29, 2021 at 5:03 PM Robert Scholte <rfscho...@apache.org> wrote: > Someone needs to implement #563525[1] > I've had the confirmation that increasing source/target of Java makes > sense. > > > thanks, > Robert > > [1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=563525 > On 29-5-2021 16:07:50, Gary Gregory <garydgreg...@gmail.com> wrote: > Hi All, > > How do I use a @Parameter on a NIO Path? > > I don't a place to plugin a factory of some kind. > > TY, > > Gary >
