Reverse engineering a custom Java builder written in Perl
We need full documentation of the currently undocumented program. Specifically in POD (Plain Old Documentation - [url removed, login to view]) inline, and compiled into HTML files (UNIX-style man pages would be appreciated as well). Additionally UML diagrams to help explain work flow and structure are required.
We have a fairly large Java code base made by a third party developer and they decided that Apache Maven was no longer appropriate for them. They made a custom builder in Perl. However the custom builder works nowhere but on the third party’s development environment because of missing dependencies.
We believe it was meant to be compiled on a Linux of the RPM variety, CentOS most likely. Like their Java code base, the Perl has limited documentation that is frequently unhelpful. They obtained Perl modules from CPAN and from wherever, creating a dependency problem with different versions that did not work together and with no documentation, no way to replicate that specific dev environment.
The Perl seems to be derived from the behavior of Maven and may use the [url removed, login to view] files that Maven uses. There are 40+ .pm and .pl files along with .xslts.