403 Forbidden error about grails-birt-plugin

[paulwellnerbou]

@jackradiance Yes, that's possible. Bintray stopped supporting free repositories, and I did not set up a new one.

I won't have time to set up a new repository for it right now -- maybe next week. So for now you'll have to build it by yourself. It will be in your local maven/gradle repository then and can be used by your application.

[jackradiance]

@paulwellnerbou thanks for your response. I cloned the repository in order to build it locally, but I had some issues:

Here is a screenshot of one of the errors after digging a little deeper:

I tried running ./gradlew install (without the check) which created a birt report 4.4.1-SNAPSHOT plugin in my local maven repository, but this doesn't match the version number from the readme instructions. Trying to import this new local maven plugin into my Grails 5 project resulted in this error when running grails run-app:

org.eclipse.birt.runtime:org.eclipse.birt.runtime:4.3.0a is being compiled in the build.gradle file of your plugin code, but it throws an error.

Any help or insight you can provide would be greatly appreciated! I am upgrading the Grails version of a project that was handed to me and I'm having a hard time figuring out how to get the Birt reports to work.

[paulwellnerbou]

@jackradiance I adjusted the tests so that they run under windows, too.

Yes, of course the version is different. Just use the version you have in your repository as dependency. (Or change the version in gradle.properties)

[jackradiance]

@paulwellnerbou thank you! I pulled and the tests ran successfully.

I had to add http://www.it-jw.com/maven as a maven repository in my Grails 5 project in order to fix the org.eclipse.birt.runtime:org.eclipse.birt.runtime:4.3.0a plugin error.

You may want to update your readme so that it uses org.grails.plugins:birt-report:4.4.1-SNAPSHOT as the plugin name in build.gradle instead of org.grails.plugins:birt-report:4.4.0

Thanks again for your help, I was able to get my Birt reports to run successfully after a bit more debugging!