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

[Geoffrey De Smet (JIRA)]

     [ https://issues.jboss.org/browse/JBRULES-2831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Geoffrey De Smet updated JBRULES-2831:
--------------------------------------

    Description: 
We're removing the current README_DEPENDENCIES.txt file because it contains a lot of incorrect (= misleading) and incomplete info.

But we'd still like to give the users that file, but correct and complete.
The only decent way to keep it correct is to generate it of the build.
In theory we could just take the output of
mvn dependency:tree
but maybe maven has a better report.

Until we do that, the users will have to rely on our released poms, which contain correct info.

  was:
We're removing the current README_DEPENDENCIES.txt file because it contains a lot of incorrect, misleading info.

But we'd still like to give the users that file, but correct.
The only decent way to keep it correct is to generate it of the build.
In theory we could just take the output of
mvn dependency:tree
but maybe maven has a better report.

Until we do that, the users will have to rely on our released poms, which contain correct info.



> The zips should contain a README_DEPENDENCIES.txt file generated by the build
> -----------------------------------------------------------------------------
>
>                 Key: JBRULES-2831
>                 URL: https://issues.jboss.org/browse/JBRULES-2831
>             Project: Drools
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 5.1.1.FINAL
>            Reporter: Geoffrey De Smet
>            Assignee: Geoffrey De Smet
>            Priority: Optional
>             Fix For: FUTURE
>
>
> We're removing the current README_DEPENDENCIES.txt file because it contains a lot of incorrect (= misleading) and incomplete info.
> But we'd still like to give the users that file, but correct and complete.
> The only decent way to keep it correct is to generate it of the build.
> In theory we could just take the output of
> mvn dependency:tree
> but maybe maven has a better report.
> Until we do that, the users will have to rely on our released poms, which contain correct info.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira