Bug 1002571 - Drools plugin uses Juno as target platform
Summary: Drools plugin uses Juno as target platform
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss BRMS Platform 6
Classification: Retired
Component: Eclipse Tooling
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: ER4
: 6.0.0
Assignee: Kris Verlaenen
QA Contact: Tomas Schlosser
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-08-29 13:04 UTC by Tomas Schlosser
Modified: 2014-08-06 20:15 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-08-06 20:15:52 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Tomas Schlosser 2013-08-29 13:04:22 UTC 
Description of problem:
The plugin is compiled with JBoss Tools 4.0.0 as a target platfor, we should target 4.1.x since BRMS is intended to work with JBDS 7.

Version-Release number of selected component (if applicable):
JBDS 7
JBoss Drools Core 6.0.0.201308222359 org.drools.eclipse.feature.feature.group

Steps to Reproduce:
1. install the plugin
2. check update sites

Actual results:
all the update sites imported by plugin are for Eclipse Juno

Expected results:
Eclipse Kepler update sites

Additional info:
Also some internal classes used by Drools Plugin changed between Juno and Kepler so debugging throws exception that can't be seen on Juno.
Comment 1 Tomas Schlosser 2013-08-29 13:05:10 UTC 
I have submitted a pull request with required changes https://github.com/droolsjbpm/droolsjbpm-tools/pull/25 Please review it and merge it.
Comment 5 Tomas Schlosser 2014-01-15 11:30:59 UTC 
Verified with Drools plugin 6.0.1.Final
Note You need to log in before you can comment on or make changes to this bug.