| Summary: | The GA builds include (2) versions of drools-core and drools-compiler .jars | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise SOA Platform 4 | Reporter: | Len DiMaggio <ldimaggi> |
| Component: | Build Process | Assignee: | trev <tkirby> |
| Status: | CLOSED NEXTRELEASE | QA Contact: | |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 4.2 GA | ||
| Target Milestone: | --- | ||
| Target Release: | 4.2 CP01 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| URL: | http://jira.jboss.org/jira/browse/SOA-436 | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: |
soa-4.2.0.GA.zip
standalone-soa-4.2.0.GA.zip
|
|
| Last Closed: | 2008-04-01 15:58:19 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Len DiMaggio
2008-02-25 18:58:34 UTC
[ldimaggi@ldimaggi jboss-soa-p-standalone.4.2.0]$ find /opt/GA -name "drools-compiler*.jar" -print /opt/GA/jboss-soa-p.4.2.0/seam/drools/lib/drools-compiler-3.0.5.jar /opt/GA/jboss-soa-p.4.2.0/jboss-as/server/production/deploy/jbrules.esb/drools-compiler-4.0.2.jar /opt/GA/jboss-soa-p.4.2.0/jboss-as/server/all/deploy/jbrules.esb/drools-compiler-4.0.2.jar /opt/GA/jboss-soa-p.4.2.0/jboss-as/tools/console/console/jboss-esb-console.ear/drools-compiler-3.0.5.jar /opt/GA/jboss-soa-p-standalone.4.2.0/jboss-as/server/default/deploy/jbrules.esb/drools-compiler-4.0.2.jar /opt/GA/jboss-soa-p-standalone.4.2.0/jboss-as/tools/console/console/jboss-esb-console.ear/drools-compiler-3.0.5.jar Link: Added: This issue related SOA-437 Link: Added: This issue is related to JBPAPP-639 Link: Added: This issue related SOA-398 Mike, is there a reason for the drools 3.0.5 jars in the console, can you comment and punt the jira back afterwards please There's no reason. We can remove them. drools components in the tools directory removed as a consequence of the old console being removed. only old drools jar left is in seam which comes from eap - see linked jira Verified in CR01 - the SEAM copy of the old drools lib remains - the console copy was removed [ldimaggi@ldimaggi helloworld_topic_notifier]$ find /opt/CP01 -name "drools-core*.jar" -print /opt/CP01/jboss-soa-p.4.2.0/seam/drools/lib/drools-core-3.0.5.jar /opt/CP01/jboss-soa-p.4.2.0/jboss-as/server/production/deploy/jbrules.esb/drools-core-4.0.6.jar /opt/CP01/jboss-soa-p.4.2.0/jboss-as/server/all/deploy/jbrules.esb/drools-core-4.0.6.jar /opt/CP01/jboss-soa-p-standalone.4.2.0/jboss-as/server/default/deploy/jbrules.esb/drools-core-4.0.6.jar [ldimaggi@ldimaggi helloworld_topic_notifier]$ find /opt/GA -name "drools-core*.jar" -print /opt/GA/jboss-soa-p.4.2.0/seam/drools/lib/drools-core-3.0.5.jar /opt/GA/jboss-soa-p.4.2.0/jboss-as/server/production/deploy/jbrules.esb/drools-core-4.0.2.jar /opt/GA/jboss-soa-p.4.2.0/jboss-as/server/all/deploy/jbrules.esb/drools-core-4.0.2.jar /opt/GA/jboss-soa-p.4.2.0/jboss-as/tools/console/console/jboss-esb-console.ear/drools-core-3.0.5.jar /opt/GA/jboss-soa-p-standalone.4.2.0/jboss-as/server/default/deploy/jbrules.esb/drools-core-4.0.2.jar /opt/GA/jboss-soa-p-standalone.4.2.0/jboss-as/tools/console/console/jboss-esb-console.ear/drools-core-3.0.5.jar |