Bug 751023

Summary:	Eclipse drools plugin - drools jars disappear from drools library when internal classes are switched from Discouraged to Accessible
Product:	[JBoss] JBoss Enterprise BRMS Platform 5	Reporter:	Jiri Svitak <jsvitak>
Component:	Tooling (JBDS)	Assignee:	Mario Fusco <mfusco>
Status:	VERIFIED ---	QA Contact:
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	BRMS 5.2.0.GA	CC:	kverlaen, manstis, mbaluch, mfusco
Target Milestone:	---
Target Release:	One Off Releases
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	When using the JBoss Developer Studio Plugin, setting the internal classes from discouraged to accessible removes the the drools jars from the drools library.	Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Jiri Svitak 2011-11-03 09:32:00 UTC

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.

Comment 1 JBoss JIRA Server 2012-04-12 14:54:07 UTC

Mario Fusco <mario.fusco> updated the status of jira JBRULES-3456 to Resolved

Comment 2 Ryan Zhang 2012-04-23 07:37:17 UTC

Update status to ON_QA. Please verify them against ER6.

Comment 3 Jiri Svitak 2012-04-30 09:10:57 UTC

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.

Comment 4 Ryan Zhang 2012-05-09 07:52:45 UTC

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/ )

Comment 6 lcarlon 2012-06-13 03:35:30 UTC

    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.

Comment 8 Mario Fusco 2012-11-15 09:46:46 UTC

I tested this issue again on the 5.3.x branch and it works for me.

Comment 10 Jiri Svitak 2013-06-27 09:26:32 UTC

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.