Is it a way to avoid the version comment to be added?
<?xml version="1.0" encoding="UTF-8"?>
<!-- Created with Jaspersoft Studio version 6.5.1.final using JasperReports Library version 6.5.1 -->
Not the whole team use the exact same version, some have 6.4, 6.5, 6.5.1, so this comment generate unnecessary changes on Git
Could not find a simple solution.
As a workaround, force the jrxml and compiler versions on Window > Preferences > Jasper Studio > Compatibility to a desired version. This way, the comment will still be there but will always be the same
Related
I have installed eclipse-4.16 (2020-06) on FreeBSD-12.1p10 in order to use Jaspersoft Studio with iDempiere-7.1. iDempiere-7.1 uses net.sf.jasperreports.engine_6.6.0.jar as its report engine. The current Jaspersoft Studio (6.16.0) plug-in will not install due to a dependency error.
Cannot complete the install because some dependencies are not satisfiable
org.eclipse.equinox.p2.iu; com.jaspersoft.studio.feature.feature.group
[6.16.0.final,6.16.0.final] cannot be installed in this environment because
its filter is not applicable.
I have learned that the latest Jaspersoft Studio that is known to work with iDempiere-7.1 is 6.5.1. I added https://sourceforge.net/projects/jasperstudio/files/updatesite/6.5.1/ as a plug-in site and that version is indeed selected when I attempt to install Jaspersoft Studio. But it gives the same dependency error.
How do I get Jaspersoft Studio to install?
I have installed tibco jaspersoft Studio last version and wanted to edit some jasper files. I have imported the project from git and everytime when I open the project it loads for ever and hangs by searching Data Adapters see screenshot:
It takes resources and time. Any Idea how to solve this problems?
p.s.: I have also tried pluging for eclipse and got the same problem
I'd like to compile my reports with earlier versions of the JasperReports, so I'm trying to add other versions of the JasperReports to my Jaspersoft Studio on: Project -> Properties -> Jaspersoft Studio -> Compatibility -> Use Project Settings -> Manage JasperReports Version.
I choose the Add From URL option and then I select some version on combobox. After a few moments I get the error below:
I tried to install many versions but all of them failed.
I'm opening the Jaspersoft Studio with admin privilegies on Windows and my environment is as follows:
Windows 7
Java 8
Jaspersoft Studio 6.3.0
Note: I've already tried with Jaspersoft Studio 6.3.1 too.
I'd like to know if this is a problem of my environment. Anyone have any tips?
Don't fight the problem, workaround it
I also have had some problems like "handsake-failure" ecc, trying to use url system to download, unzip and install older versions.
Blaarg, lets install it by hand.
Download the version you like from Sourceforge, for example
5.6.1
Unzip it
Press Add From Path and select the jasper-reports folder
Ok, Ok and your problem should be solved, basically this way your are eliminating all problems related to download and unzipping the project.
If you like you can open an issue on the jasper-reports bugs tracker, but in the mean while you are up and running
I am using the Vaadin Plug-in for Netbeans version 1.1.0 with NetBeans 8.1 & 8.2 (as shown here. This plugin defaults to using Vaadin 7.5.9 rather than the current version of Vaadin for a new project created by choosing File > New Project > Categories (list) > Vaadin > Projects (list) > Vaadin Multi Module Project.
How does one change the Vaadin version from 7.5.9 to 7.7.3 (the latest)?
By context-clicking on the “…-ui” module in the Projects navigator in NetBeans, I accessed the Properties > Project Properties > Categories (list) > Vaadin (list item) > Vaadin Version pop-up menu.
This seemed to work. But when I do a clean-and-build on the …-parent module, I still see line items for Vaadin version 7.5.9 in the NetBeans console output.
So what is the proper way to get a Vaadin multi-module project in NetBeans 8 to use a later version of Vaadin?
You are right. Something is broken with latest Vaadin version support for projects.
Version 7.5.9 used to be the latest available version when the NetBeans plugin has been built. To be able to support latest stable versions plugin reads some URL from vaadin.com site and uses versions from there.
But apparently this is broken. New projects are created with old version.
Could you please create a ticket for that here https://github.com/vaadin/netbeans-plugin/issues ? Thanks a lot.
We are working currently on Vaadin version 8.0 and soon we will have to release new NetBeans plugin version to support it. So this issue might be fixed in this update.
Multimodule project support is not completely implemented unfortunately. That's why version is not correctly updated via project settings.
You can create an issue about this as well (though I think I already made it in our old tracker https://dev.vaadin.com/).
But back to your issue: you can fix it via editing POM file manually.
Please open POM.xml file in your root parent project and find
<properties>
section.
There is <vaadin.version>7.5.9</vaadin.version> string. Just replace 7.5.9 with required version.
Thanks and sorry for inconvenience.
After editing a jaspersoft template in Studio version 6.0.3 is it possible to export or upload the jrxml file to my server via sftp directly from JasperSoft Studio?
Currently after edits are made and saved I have to go to the ftp client to upload files.
you could try to use Eclipse RSE installing the dedicated feature. It's possible from Jaspersoft Studio. You simply need to add the update site for it.
I would suggest you use Indigo one, because the Juno (dedicated to 4.2.x) may screw up UI and other JSS capabilities.
Even if the Eclipse 3.8.2 version, the platform used by JSS product, is referred as Juno, it can be more like a bug-fix version of Indigo 3.7.x.
So you could add the Indigo update site: http://download.eclipse.org/releases/indigo/
Later you can select the feature "Remote System Explorer End-User Runtime", install it and you are free to try if it suits your needs.
See screenshot below:
Personally I simply installed, but I didn't play with it.
Anyhow I suggest you to also give a look to the following blog post: http://rays-blog.de/2012/05/05/94/use-winscp-to-upload-files-using-eclipses-autobuild-feature/
Maybe it's better to set-up a custom script, like this user did because not completely satisfied of the Eclipse-like solutions.
It's worth mentioning also this one: http://www.jcraft.com/eclipse-sftp/
In my case it didn't work even if installation appeared to have completed successfully. Maybe it's too old for the latest Eclipse versions.
Regards,
Massimo.