[jboss-jira] [JBoss JIRA] (JBRULES-2831) The zips should contain a README_DEPENDENCIES.txt file generated by the build

[ https://issues.jboss.org/browse/JBRULES-2831?page=com.atlassian.jira.plug... ] Geoffrey De Smet resolved JBRULES-2831. --------------------------------------- Resolution: Won't Fix Won't fix: just do a listing of the "binaries" directory in the distribution zip. The README_DEPENDENCIES.txt file was not correct up to 5.1 and has been removed since BRMS 5.2. The real problem is that there is no such thing as "a global dependencies list for drools", there is one per artifact, so there is "a dependencies list for drools-core" and "a dependencies list for drools-compiler" and so on. For example: if a user doesn't use the drools-decisiontables jar, he don't need the jexcelapi:jxl jar in the classpath. The dependency tree information is deployed to the maven repository, per artifact in the pom.xml files. Users that use Maven, Gradle, Ivy or Buildr have the tools to parse and use that information: http://search.maven.org/#artifactdetails%7Corg.drools%7Cdrools-compiler%7... However, ANT users might still want something like that README_DEPENDENCIES.txt report. But that's basically just a listing of the "binaries" directory in the distribution zip, so I see no need to duplicate that information in a txt file. If that list is too course-grained, they can look up the information on nexus for a specific artifact, for example for drools-compiler: https://repository.jboss.org/nexus/index.html#nexus-search;gav~org.drools... To get the list, click the tab "maven dependency" and the button "resolve". I hope that explains the problem better and I hope it helps. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira