JDeprscan plugin 3.0.0 ?

[Andres Almiray]

Hello everyone,

While doing research on Maven plugins hat help you work with modular
applications I couldn't fail to notice that the jdeprscan plugin is listed
at version 3.0.0-alpha-1 and its page marks it as prerelease since 2017

https://maven.apache.org/plugins/maven-jdeprscan-plugin/

As you may be aware this was the case for the jlink plugin which received
some love from Benjamin, Sandra, Karl-Heinz and co. and was able to cross
the 3.0.0 line in late 2020. It's actually now at 3.1.0.

I wonder what's missing in the current state to turn it into 3.0.0? What
can be done to make this plugin cross the 3.0.0 line as well? Happy to help.

Cheers,
Andres

-------------------------------------------
Java Champion; Groovy Enthusiast
http://andresalmiray.com
http://www.linkedin.com/in/aalmiray
--
What goes up, must come down. Ask any system administrator.
There are 10 types of people in the world: Those who understand binary, and
those who don't.
To understand recursion, we must first understand recursion.

[Benjamin Marwell-2]

Sure, I can do that (again) :)

If you don’t mind, I would like to remove some deep nesting in a few
methods and extract some methods in other places as well,
because I might re-use some functionality in a later feature (for
scanning dependencies).

GH Actions would be a nice addition, too.
Maybe add some more ITs, some nits here and there,
and have some never-to-be-merged-branches of other plugins which use this plugin
so we have some more "real life" examples.

Oh, and docs, of course. I would like to add example output.
Please be sure to watch the bug tracker. ;-)

- Ben

Am Mi., 24. Feb. 2021 um 21:22 Uhr schrieb Robert Scholte
<[hidden email]>:

>
> Hi,
>
> I would like to see the plugin being able to use the ToolProvider, as done with the jlink plugin.
> This will make it possible to run on on Windows too with a long list of arguments.
>
> https://issues.apache.org/jira/projects/MJDEPRSCAN is empty (although I will create one for the ToolProvider)
>
> Andres, we did discuss some improvements, not sure the status of it.
> Please file Jira tickets in case you're missing something.
>
> thanks,
> Robert
>
>
> On 24-2-2021 12:12:48, Andres Almiray <[hidden email]> wrote:
> Indeed. Scanning compile & runtime dependencies is a feature Robert and I
> discussed back at JCrete 2018 if not mistaken.
> For comparison the Gradle jdeprscan plugin (for which I'm the author) has
> this feature.
>
> I believe this feature was even added to the issue tracker at some point.
>
> Cheers,
> Andres
>
> On Wed, Feb 24, 2021 at 12:08 PM Benjamin Marwell
> wrote:
>
> > Sounds interesting! Is anyone using this yet?
> >
> > Seems to be a reasonable default plugin for builds, additional to
> > -Dmaven.compiler.showDeprecation=true
> >
> > Probably another (maybe even more useful) goal would be to scan
> > compile- and runtime dependencies as well.
> >
> > Am Di., 23. Feb. 2021 um 20:40 Uhr schrieb Andres Almiray
> > [hidden email]>:
> > >
> > > Hello everyone,
> > >
> > > While doing research on Maven plugins hat help you work with modular
> > > applications I couldn't fail to notice that the jdeprscan plugin is
> > listed
> > > at version 3.0.0-alpha-1 and its page marks it as prerelease since 2017
> > >
> > > https://maven.apache.org/plugins/maven-jdeprscan-plugin/
> > >
> > > As you may be aware this was the case for the jlink plugin which received
> > > some love from Benjamin, Sandra, Karl-Heinz and co. and was able to cross
> > > the 3.0.0 line in late 2020. It's actually now at 3.1.0.
> > >
> > > I wonder what's missing in the current state to turn it into 3.0.0? What
> > > can be done to make this plugin cross the 3.0.0 line as well? Happy to
> > help.
> > >
> > > Cheers,
> > > Andres
> > >
> > > -------------------------------------------
> > > Java Champion; Groovy Enthusiast
> > > http://andresalmiray.com
> > > http://www.linkedin.com/in/aalmiray
> > > --
> > > What goes up, must come down. Ask any system administrator.
> > > There are 10 types of people in the world: Those who understand binary,
> > and
> > > those who don't.
> > > To understand recursion, we must first understand recursion.
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [hidden email]
> > For additional commands, e-mail: [hidden email]
> >
> >

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]