]
Snjezana Peco resolved JBIDE-7114.
----------------------------------
Resolution: Cannot Reproduce Bug
Please reopen this jira if you can provide more details.
Upgrade from Seam BIRT project created on JBoss Tools 3.1.0/BIRT
2.5.1 having incompatibility issue when running report on latest JBoss Tools version
----------------------------------------------------------------------------------------------------------------------------------------------------------
Key: JBIDE-7114
URL:
https://jira.jboss.org/browse/JBIDE-7114
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: birt, integration, usage
Affects Versions: 3.1.1, 3.2.0.M2
Environment: Fedora 12 (2.6.32.21-166.fc12.i686.PAE)
Reporter: Indra Gunawan
Assignee: Snjezana Peco
Priority: Minor
Fix For: 3.2.0.Beta2
I have a Seam Birt project that I created with JBoss Tools 3.1.0 (BIRT version
2.5.1/3.2.20), then I decided to upgrade my IDE using JBoss Tools 3.2.0 on Eclipse 3.6
(BIRT version 2.6.0/3.2.21). I have no problem on editing project report design file and
saved it using built in designer, except the IDE is much slower than before (I realize
that this are related to WTP bug that has been fixed on Eclipse 3.6.1).
I revert back to older release JBoss Tools 3.1.x (BIRT version 2.5.2/3.2.21), at this
time my IDE is running normal like before. Then I try running my project on JBoss AS 5.0.1
and run a report that I've edited with current IDE and report designer (JBoss Tools
3.1.x (BIRT version 2.5.2/3.2.21)) but it throws:
+ There is no report design object available.
I'm able to give temporary work around with this problem by changing report version
on XML view from 3.2.21 to 3.2.20 although there are many different between both version
specially on the use of scalar parameter dataType and nativeDataType (but I'm not sure
this will cause problem or not).
Because I couldn't find solution/steps about upgrading Seam BIRT version from 2.5.1
to 2.5.2 (from 3.2.20 to 3.2.21), I decided to revert back again to my old IDE (JBoss
Tools 3.1.0 (BIRT version 2.5.1/3.2.20)).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: