Can somebody tell me, how to integrate the Ember-CLI dist-folder into a Grails plugin? My plan is to have a Grails application that could be extended by grails plugins. A plugin should contain a Grails server (with REST-services) and an Ember-CLI client. The Ember-CLI *.hbs should be displayed in the content area of the main grails application.
Related
is it possible to use the latest spring security plugin in grails 2 app?
http://plugins.grails.org/plugin/grails/spring-security-core
If, by latest, you mean the current Grails 3 version of the Spring Security Plugin, then I'd say the quick answer is "no", it's not compatible with a Grails 2 application.
Plugins in Grails 2 and Grails 3 differ in form, installation scripts, etc. For instance, in Grails 2 you have to install the plugin, whereas in Grails 3 you just depend on the plugin.
That said, Grails 3 plugins are basically just zip/jar files, and you could try just depending on the Grails 3 plugin, which would get you the classes on your classpath at least, but none of the setup that Spring Boot performs when using that plugin in Grails 3. Furthermore, the plugin assumes Spring Boot and newer Spring libraries exist in your application (as they would in a Grails 3 app). You'd be buying a big chuck of dependency hell.
I'm not sure why you're trying to do this, but I don't recommend it.
Unfortunately we have an application running Grails 1.3.9 that is earmarked for upgrade soon. However, before resources can be put into this upgrade we need to expose some of our services as SOAP endpoints. We also need to interact with an external SOAP API.
Do versions of the following plugins exist that work with Grails 1.3.9?
cxf
cxf-client
If no such compatible versions exist, the wslite plugin looks like an attractive alternative for the cxf-client plugin. Are there any such alternatives for the cxf plugin that can help expose services to SOAP requests?
You can check in the repo to see which plugin versions exist. It would be nice to have a Grails script for this.
http://repo.grails.org/grails/plugins/org/grails/plugins/cxf/
0.7 is the last version of the SOAP provider plugin that is Grails 1.x compatible, 1.6 is the last version of the plugin.
I've upgraded to Grails 2.x in the meantime so I haven't tested these, just didn't want to leave the question hanging.
I've created new grails plugin with this quick start reference.
How could I install it to local and remote repository to make it available for other plugins to depend on.
Thanks.
If you are creating a grails "plugin", you should be referring to this information instead. The one you are referring is for creating a Grails Application.
Gist:
Grails app (one you are referring to) creates a deployable component which can be deploed to any container and accessed. On the other hand, grails plugins are extension/modules that are created and maintained separately. packaged as zip and are plugged to any Grails Application when required.
If you are creating a grails plugin and want to push it to local/remote repositories, you need to use the release plugin which comes inside a plugin by default.
grails maven-install
The command is taken from release plugin to push your plugin to local maven repositories, if you have any.
I'm developing grails application and I also created a plugin and packaged it as zip.
I develop on two computers - one at work, one at home. I'd like to embed this plugin somehow in project (lib folder maybe?), so I could commit it with application to repo and then on another machine during dependecy refresh grails could install this plugin.
Is it possible?
I've been working with a grails 1.3.7 project within STS for the last few months.
Our test and production environments use JBoss 5.1.
I upgraded our grails app to 2.1.0 recentlly and it all ran ok locally.
Major problems occured when I deployed it to our test environment (Jboss issues).
So in order to avoid this in future I would like to develop locally using JBoss also.
Is there a Eclipse/STS plugin I can use for this?
Thanks
Don't think there's a specific plugin for jboss
Seems your only options now are tomcat and jetty, if you need to stick with the 'run-app' command
If you can give up the debug console and check your test info at the browser, then you can probably write a small script to auto-deploy to a local jboss server, which you can set up through eclipse workspace