When I set Drools internal classes from Discouraged to Accessible in Eclipse, then the jars dissapear from Drools library in Library screen of project. I have thought that setting internal classes to Accesible would remove several warnings from our test suite, but actual result is that there is just Drools library which is without jars. This happens with plugin with version 5.2.0 Final (JBoss Tools SOA 3.3.0.M3) installed from http://download.jboss.org/jbosstools/updates/development/indigo/soa-tooling I use Eclipse 3.7.0 Indigo. The same thing happened before with Eclipse 3.6.2 Helios.
Mario Fusco <mario.fusco> updated the status of jira JBRULES-3456 to Resolved
Update status to ON_QA. Please verify them against ER6.
I have tested this and it is not fixed in BRMS 5.3.0 ER6. Cannot verify since provided plugin file jbosstools-drools-5.3_trunk-Update-SNAPSHOT.zip from here http://jawa05.englab.brq.redhat.com/candidate/BRMS-5.3.0-ER6/jbosstools/ has old date and was not updated. Ryan, please provide us with the latest snapshot of the Drools Eclipse plugin for testing. Update also old md5 checksum file.
Yep, sorry for the old one. Jiri, the latest plugins should have been released seperatedly by Nick in soa-p-announce recently. Is it fixed in that release ( see: http://www.qa.jboss.com/binaries/RHDS/updates/development/5.0.0.Beta1.soa-tooling/ )
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: When using the JBoss Developer Studio Plugin, setting the internal classes from discouraged to accessible removes the the drools jars from the drools library.
I tested this issue again on the 5.3.x branch and it works for me.
This Bugzilla is deprecated, BRMS 5.3 is already released. Setting to verified. If there will be a similar bug found in tooling for BRMS 6, please file a new Bugzilla for tracking.
This product has been discontinued or is no longer tracked in Red Hat Bugzilla.