[JBoss JIRA] Created: (JBRULES-2831) The zips should contain a README_DEPENDENCIES.txt file generated by the build
3:25 a.m.
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 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.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:30 a.m.
New subject: [JBoss JIRA] Updated: (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 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
2:16 a.m.
New subject: [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.
---------------------------------------
Fix Version/s: 5.3.0.Final
(was: FUTURE)
Resolution: Done
This was fixed a long time ago, during 5.3.
The documentation was also adjusted:
<para>For up to date info on dependencies in a release, consult the released poms,
which can be found on the maven
repository.</para>
I've searched through the documentation and found no other part that is not up to
date.
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: 5.3.0.Final
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.
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
4:14 a.m.
New subject: [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 reopened JBRULES-2831:
---------------------------------------
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: 5.3.0.Final
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.
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
4:27 a.m.
New subject: [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.
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: 5.3.0.Final
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.
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
4777
days inactive
5141
days old
4 comments
3 participants
participants (3)
-
Geoffrey De Smet (JIRA) -
Geoffrey De Smet (Reopened) (JIRA)
-
Geoffrey De Smet (Resolved) (JIRA)