Apache Maven JDeps Plugin

[Martijn Verburg]

>From my standpoint that would be amazing - we'd always struggled with how
we're going to try and educate millions of developers about running this on
their code base.  Having it as a core report is a great start!

Cheers,
Martijn

On 20 February 2015 at 03:55, Hervé BOUTEMY <herve.boutemy at free.fr> wrote:

> regarding failing or not failing (that's the question):
>
> IMHO, it would be useful to create Maven reports: as a first step, adding
> maven-jdeps-report as report will help people be aware of the state of
> their
> code and publishing it inside their site without taking any fix action at
> the
> moment
>
> concrete use case: I'd like to add this to the Maven parent pom to have
> jdeps
> report for every future release
>
> And I can even dream one step beyond: then add a dist-tool-plugin report to
> get an overview of the state of our full codebase, like [1] :)
>
> this dream should not be that hard to happen
>
> Regards,
>
> Hervé
>
> [1]
> https://builds.apache.org/view/M-R/view/Maven/job/dist-tool-plugin/site/dist-tool-prerequisites.html
>
> Le mardi 17 février 2015 00:04:37 Robert Scholte a écrit :
> > Hi Alan,
> >
> > I've added a flag called failOnWarning (default:true), assuming that the
> > usage of jdkinternals is considered a warning and not an error.
> > With the following configuration you'll be able to run jdeps multiple
> > times within the same build.
> >
> >        <plugin>
> >          <groupId>org.apache.maven.plugins</groupId>
> >          <artifactId>maven-jdeps-plugin</artifactId>
> >          <version>3.0-SNAPSHOT</version>
> >          <executions>
> >            <execution>
> >              <id>classes</id>
> >              <goals>
> >                <goal>jdkinternals</goal>
> >                <goal>test-jdkinternals</goal>
> >              </goals>
> >            </execution>
> >            <execution>
> >              <id>dependencies</id>
> >              <goals>
> >                <goal>jdkinternals</goal>
> >                <goal>test-jdkinternals</goal>
> >              </goals>
> >              <configuration>
> >                <recursive>true</recursive>
> >                <failOnWarning>false</failOnWarning>
> >              </configuration>
> >            </execution>
> >          </executions>
> >        </plugin>
> >
> > This should match your requirements.
> >
> > Robert
> >
> >
> > Op Mon, 16 Feb 2015 19:45:16 +0100 schreef Alan Bateman
> >
> > <Alan.Bateman at oracle.com>:
> > > On 16/02/2015 18:28, Robert Scholte wrote:
> > >> Hi Alan,
> > >>
> > >> if you are referring to the -R / -recursive option of the jdeps tool,
> > >> then yes you can.
> > >> See
> > >>
> http://maven.apache.org/plugins-archives/maven-jdeps-plugin-LATEST/maven->
> >> jdeps-plugin/jdkinternals-mojo.html#recursive I think jdeps is first of
> > >> all interesting for the classes of the
> > >> current Java project, so I've set the default of this parameter to
> > >> 'false'. However, if the majority thinks it is better to activate this
> > >> by default, we will consider to change this value.
> > >
> > > I could imagine wanting to run it twice: once for the current project
> > > where I want the build to fail if it makes direct use of JDK-internal
> > > APIs, and a second time to run with -R and emit warnings if any of the
> > > transitive dependences (that I don't control) are using JDK internal
> > > APIs.
> > >
> > > -Alan
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe at maven.apache.org
> > For additional commands, e-mail: dev-help at maven.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe at maven.apache.org
> For additional commands, e-mail: dev-help at maven.apache.org
>
>