[
http://jira.codehaus.org/browse/MOJO-1338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=172806#action_172806
]
Dan Tran commented on MOJO-1338:
--------------------------------
could you scale down a small project to reproduce problem?
I am very reluctant to apply your patch since it may break the backward
compatility. Many you can deploy your own version of this plugin internally
until we have further feedback from users. If needed we will bump the version
up to 2.0 to make sure users aware it it not compatible with the 1.x
-D
> updated Mojo pom with version 3.1.2 of JasperReports
> ----------------------------------------------------
>
> Key: MOJO-1338
> URL: http://jira.codehaus.org/browse/MOJO-1338
> Project: Mojo
> Issue Type: Improvement
> Components: jasperreports
> Affects Versions: buildnumber-maven-plugin-1.0-beta-3
> Reporter: Brian Bonner
> Attachments: updateJasperVersionPatch.txt,
> updateJasperVersionPatch.txt
>
>
> JasperReport plugin was configured to use an older version of JasperReports.
> The new plugin compiles the classes with a new version (3.1.2) of
> JasperReports.
> The older version had problems with supporting older java files as well as
> properly compiling custom classes -- resulting in ClassNotFoundExceptions.
> While attempting to debug the JasperReportPlugin -- and updating the pom to
> the newest version, the compilation problem went away.
> I also updated CommonsLogging to 1.0.4 since our project uses this newer
> version (I anticipate that it's backwards compatible to 1.0.3)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
