-
Notifications
You must be signed in to change notification settings - Fork 143
Known Issues
As of June 11, 2018, using the example Map Widget requires a valid API key for Google Maps.
Please see the following page for usage instructions:
https://github.com/ozoneplatform/owf-framework/wiki/Example-Map-Widget-API-Key
Older versions of the code will now fail to compile and build due to their reliance on the GOSS infrastructure. The latest versions of the grails plugins necessary have been migrated over to maven central and therefore should get pulled automatically, the problem occurs when the dependency version in whatever version you're building hasn't been moved to maven central.
Options (Maven Dependencies): You need the maven dependencies to run the grails application and anything beyond that (bundling, building, etc.)
-
Send an email to the support team with the dependency version that's failing and we can potentially move the version to maven central for you.
-
If you have access to the DI2E project the old versions of the plugins are available there, you can either try to hook them into the project by adding a
mavenRepo ...
line toBuildConfig.groovy
or you can download the dependency and move it to your~/.m2/repositories
folder directly and it should pull that when you build. -
You can add
mavenRepo 'http://gossnexus01:8081/nexus/content/groups/public'
to yourBuildConfig.groovy
to build from there.
Options (Ivy Dependencies): You will need the ivy dependencies if you're attempting to build a bundle.
-
If you have access to the DI2E project the old versions of the plugins are available there, you can either hook them in by changing
<ibiblio ... />
in yourivysettings.xml
to the correct URL for DI2E. Alternatively, you can download the dependency and move it to your~/.ivy2/cache
folder directly and it should pull that when you build. -
You can change your
ivysettings.xml
andivy.xml
files to match what currently exists in the project folder to pull from the new sources we've started using.
Please enter issues with the product or documentation at OWF Framework Issues.