For the ones using the plugin source code (and who have not recently updated), please note that v.5.0.0a1 is now head/trunk and the 4.x version of the plugin has a corresponding branch.
Since iReports is being deprecated in 2015, is Servoy planning to include Jaspersoft Studio as an installable item (under the ‘Help → Install New Software… → Work with:’ pull-down selection list) where it would become another Perspective to the Servoy Eclipse platform?
I installed the stand-alone version of JasperReports Studio, and it works fine. However, I tried to install it as an update to the Servoy Eclipse by following the ‘update’ link you gave, but the link does not resolve properly:
An error has been encountered in accessing this page.
If I try http://jasperstudio.sourceforge.net, I get redirected to the JasperReports community page, and I could find no mention of the update there. Is there another way to accomplish this?
Kim,
The way I installed it in Servoy is as follows in the developer:
Help | Install new Software…
Click on Add button to add a new site.
The popup dialog “Add Repository” shows:
Give it a name e.g. “JasperStudioReports” or whatever you prefer.
Specify the location as ``` http://jasperstudio.sourceforge.net/updates/
Then OK to close this dialog.
Check/select the box after the "Business Intelligence, Reporting Tools" show up under the Name area.
Then continue with next button etc.
Works fine with me (using Servoy 7.4 and Windows 7)
Yes, that is what I was doing. I didn’t catch the link difference in Tom’s original reply. I used the ‘update’ link in the Eclipse ‘install new software’ section, and it installed correctly.
Remember that for any new Servoy install you will have to add Eclipse plugins like this each time.
Sorry not to have made the explanation more clear.
Let us know of issues using the studio.
One of the first that I had was to specify the correct “datasource adapter” when I pulled in a iReport (jrxml) file.
I tried to use 5.00a a few months ago but found it buggy regarding sub-reports and graphics and, consequently, reverted to version 4.0.2.
I, too, am somewhat dismayed at the slow pace of revision to the Jasper Report plugin but attribute it to the workload of getting Servoy 8 up and running along with the recent personnel changes. I don’t think the Jasper Report plugin is officially supported by Servoy…but, in my opinion, it should be as many seem to use it. It would be nice to see regular updates to this plugin.
lwjwillemsen:
Clear example of the downside of open sourcing of a (much used) plugin…
Not sure how you figure that.
The fact that it’s Open Source or Closed Source doesn’t mean that the author(s) will keep it maintained or not.
In fact because it’s Open Source it protects you from being stuck with an abandoned piece of software. Someone, you for example, can pick up the source and fork it or supply patches for bugs or new features.
In either case there is always the expectation of users that the source keeps being maintained.
I know that of course ! If you have the time and resources there is no problem with open sourcing.
Also when the user base is large enough (10000+ ?) the open source concept will work better.
That’s why I prefer the Jasper report plugin as being part of Servoy development and support.
Our (and our customers) dependency of it is too large…
lwjwillemsen:
I know that of course ! If you have the time and resources there is no problem with open sourcing.
Also when the user base is large enough (10000+ ?) the open source concept will work better.
That’s why I prefer the Jasper report plugin as being part of Servoy development and support.
Our (and our customers) dependency of it is too large…
+1
Especially now printing internally (with forms) is totally dropped in Servoy 8!
NGClient Compatibility
printing a form from scripting is not possible, browser printing needs to be used or jasper reports for reports
lwjwillemsen:
Clear example of the downside of open sourcing of a (much used) plugin…
Not sure how you figure that.
The fact that it’s Open Source or Closed Source doesn’t mean that the author(s) will keep it maintained or not.
In fact because it’s Open Source it protects you from being stuck with an abandoned piece of software. Someone, you for example, can pick up the source and fork it or supply patches for bugs or new features.
In either case there is always the expectation of users that the source keeps being maintained.
+1, but I think this work needs to be done by Servoy.
lwjwillemsen:
Clear example of the downside of open sourcing of a (much used) plugin…
Not sure how you figure that.
The fact that it’s Open Source or Closed Source doesn’t mean that the author(s) will keep it maintained or not.
In fact because it’s Open Source it protects you from being stuck with an abandoned piece of software. Someone, you for example, can pick up the source and fork it or supply patches for bugs or new features.
In either case there is always the expectation of users that the source keeps being maintained.
+1, but I think this work needs to be done by Servoy.
Obviously, since they are the project maintainers. They decide what goes into the project and when.
My argument was that the lack of progress has nothing to do with it being Open Source or not.