You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 1, 2023. It is now read-only.
I'm working on a large project that uses jasperreports-3.7.0. Needless to say, your wonderful plugin won't work for me as-is.
I toyed with the idea of refactoring to treat the properties differently, depending on which API is available (3.7 doesn't have the DefaultJasperReportsContext, instead using JRProperties) - but that's terribly messy. Multiple ClassLoaders, or wiring up the DI - all require some runtime magic. And the tests would have to be enhanced to include older versions as well.
For now, I've forked this repo and am going to deploy a jasperreports-3.7.0 version into my private Nexus repo with a changed groupId. Not a great community-contributing way of dealing with it, but it'll get me moving forward.
I'd be happy to contribute something back here, if you have a suggestion that you think would work? Given the longevity of Jasper Reports, I can't imagine I'm the only one to have this need.
The text was updated successfully, but these errors were encountered:
I'm working on a large project that uses
jasperreports-3.7.0
. Needless to say, your wonderful plugin won't work for me as-is.I toyed with the idea of refactoring to treat the properties differently, depending on which API is available (3.7 doesn't have the
DefaultJasperReportsContext
, instead usingJRProperties
) - but that's terribly messy. Multiple ClassLoaders, or wiring up the DI - all require some runtime magic. And the tests would have to be enhanced to include older versions as well.For now, I've forked this repo and am going to deploy a
jasperreports-3.7.0
version into my private Nexus repo with a changedgroupId
. Not a great community-contributing way of dealing with it, but it'll get me moving forward.I'd be happy to contribute something back here, if you have a suggestion that you think would work? Given the longevity of Jasper Reports, I can't imagine I'm the only one to have this need.
The text was updated successfully, but these errors were encountered: