search

albfernandez / richfaces

RichFaces - JSF component framework
GNU Lesser General Public License v2.1
16 stars 7 forks source link

Cannot determine module name for richfaces-core 4.6.12.ayg #39

Closed hazendaz closed 4 years ago

hazendaz commented 4 years ago

This error occurs during javadoc report generation with higher jdks. I think the solution is rather simple in just needing to define automatic module naming which is added to the meta data of the jars. Is it possible automatic module naming can be added to the core components here and a quick patch released?

albfernandez commented 4 years ago

I think Automatic-Module-Name is already added in all META-INF/MANIFEST.MF. What are you doing? the problem is compiling your project or Richfaces itfself?

hazendaz commented 4 years ago

Compiling my project. Javadoc plugin run states that its unable to determine the module name for rich faces. I'll look a little deeper and get you better info later thus weekend. It is the only lib out of around 200 in the build with any issue.

Get Outlook for Androidhttps://aka.ms/ghei36

From: Alberto Fernández notifications@github.com Sent: Friday, May 8, 2020 10:22:57 AM To: albfernandez/richfaces richfaces@noreply.github.com Cc: Jeremy Landis jeremylandis@hotmail.com; Author author@noreply.github.com Subject: Re: [albfernandez/richfaces] Cannot determine module name for richfaces-core 4.6.12.ayg (#39)

I think Automatic-Module-Name is already added in all META-INF/MANIFEST.MF. What are you doing? the problem is compiling your project or Richfaces itfself?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://github.com/albfernandez/richfaces/issues/39#issuecomment-625839967, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AAHODI2WFMWLHMEZ2R6BR7LRQQIUDANCNFSM4M32NWWA.

hazendaz commented 4 years ago

@albfernandez Closing. Found the source of issue. Someone in my firm manually uploaded jboss 6.0 pom 3 years ago and it causes a cascading issue that results in this appearance. So this is not an issue here and therefore nothing is needed to be done. Thanks.