Found same issue with javadoc plugin in our dist-check tool

Sylwester

niedz., 17 lip 2022, 13:57 użytkownik Gary Gregory <garydgreg...@gmail.com>
napisał:

> On Sun, Jul 17, 2022 at 7:04 AM Michael Osipov <micha...@apache.org>
> wrote:
> >
> > Am 2022-07-17 um 13:02 schrieb Gary Gregory:
> > > (Sorry for the top post) So it sounds like the simplest from a user's
> POV
> > > is to wait for JDepend 2.1.
> >
> > Technically yes, but given the requirements I have depicted I don't
> > expect any release soon. I won't put any effort into this plugin beyond
> > a pure release.
>
> k, I've dropped jdepend-maven-plugin from commons-parent, we can
> always put it back when it is fixed later.
>
> Gary
>
> >
> > M
> >
> > > On Sat, Jul 16, 2022, 16:21 Michael Osipov <micha...@apache.org>
> wrote:
> > >
> > >> Gary,
> > >>
> > >> went through. It is jdepend-maven-plugin only. With:
> > >>> D:\Entwicklung\Projekte\commons-dbcp [master ≡ +0 ~1 -0 !]> git diff
> > >>> diff --git a/pom.xml b/pom.xml
> > >>> index 1269f8b3..694d24e1 100644
> > >>> --- a/pom.xml
> > >>> +++ b/pom.xml
> > >>> @@ -365,6 +365,11 @@
> > >>>               </ignorePathsToDelete>
> > >>>             </configuration>
> > >>>           </plugin>
> > >>> + <plugin>
> > >>> +          <groupId>org.apache.maven.plugins</groupId>
> > >>> +          <artifactId>maven-site-plugin</artifactId>
> > >>> +          <version>3.12.0</version>
> > >>> +        </plugin>
> > >>>           <!-- Allow use of "mvn checkstyle:checkstyle" -->
> > >>>           <plugin>
> > >>>             <groupId>org.apache.maven.plugins</groupId>
> > >>> @@ -457,6 +462,11 @@
> > >>>     </build>
> > >>>     <reporting>
> > >>>       <plugins>
> > >>> + <plugin>
> > >>> +        <groupId>org.codehaus.mojo</groupId>
> > >>> +        <artifactId>jdepend-maven-plugin</artifactId>
> > >>> +        <version>2.1-SNAPSHOT</version>
> > >>> +</plugin>
> > >>>         <plugin>
> > >>>           <groupId>com.github.siom79.japicmp</groupId>
> > >>>           <artifactId>japicmp-maven-plugin</artifactId>
> > >>
> > >> it works:
> > >>> [INFO] Generating "JDepend" report       ---
> > >> jdepend-maven-plugin:2.1-SNAPSHOT:generate
> > >>>
> > >>> Unknown constant: 18
> > >>>
> > >>> Unknown constant: 18
> > >>>
> > >>> Unknown constant: 18
> > >>>
> > >>> Unknown constant: 18
> > >>>
> > >>> Unknown constant: 18
> > >>>
> > >>> Unknown constant: 18
> > >>>
> > >>> Unknown constant: 18
> > >>>
> > >>> Unknown constant: 18
> > >>>
> > >>> Unknown constant: 18
> > >>>
> > >>> Unknown constant: 18
> > >>>
> > >>> Unknown constant: 18
> > >>>
> > >>> Unknown constant: 18
> > >>
> > >>
> > >> The report looks good as well. We now have the following problems:
> > >>
> > >> * JDepend 2.10 isn't in Central and has trouble with Java 8
> > >> * The ITs are horribly outdated plugin/dependency-wise
> > >>
> > >> I'd push a new relese of this plugin if someone could take care at
> least
> > >> of the ITs.
> > >>
> > >> Note: Since the last relese of this plugin is ages ago it depends on a
> > >> deprecated class for about 10 years ago. The ABI incompat is my fault,
> > >> it was already reported by the Asciidoctor team on ASF JIRA and they
> > >> simply aligned their code and it worked again.
> > >>
> > >> Let me know how you'd like to proceed.
> > >>
> > >> M
> > >>
> > >> M
> > >>
> > >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>

Reply via email to