If we are building the Quickfix/j application using maven, then it asks for an archetype so, what should be its archetype?
I tried searching on Stackoverflow but didn't find the answer
Related
I am also facing the same issue with Sonar-Gerrit jenkins plugin. Downloaded it from Jenkins plugins site.Using Sonar-Gerrit plugin 2.2.1, and analysing sonar scan against jenkins workspace.
For a sample,have changed just one file and provided the project base directory to the path of that file, and ran the sonar analysis in issues mode.
Issues are not loaded in Gerrit and jenkins logs say
Report has loaded and contains 759 issues Issues to be commented: 0 Issues to be involved in score calculation: 0 Review has been sent
Have already referred the StackOverflow Page Sonar Gerrit plugin not reporting results. Kindly advice on this
I faced a similar issue and for me the resolution was to point the Project Base Directory to my source folder. If you're using sonar to scan all of your source files then pointing the Project Base directory at only one file I don't think it will like that.
There is a bug in 2.2.1. If you have custom sub-project settings, the filter option "affect changed lines only" is not working correctly and removes all the files from the result. This issue will be fixed in the next release.
For now you can use the plugin without this option (all the issues satisfying severity and is new criteria will be posted to the changed files)
If this does not help, make sure that you have your project settings being set up correctly.
UPD: a new version of plugin with the fix was released
I am building my first Grails app and would like the build to be managed by Gradle. I see that there is a Grails-Gradle plugin and many online searches indicate that it is not possible to build a Grails app using Gradle without this plugin.
My question is: why? Why (specifically) is this plugin necessary in order for Gradle to be able to build a Grails app? What functionality does this plugin provide that is otherwise missing?
I don't know why you think it's impossible to build a Grails app without the plugin. It's possible to issue commands to the grails shell from Gradle without the plugin, but it's not very clean.
That's what this plugin does. It cleans up that process, and makes it much Groovier with a DSL. It also makes your Gradle script more portable to other projects and persons.
If you browse the source code you will see all the inner workings of the plugin and realize what it's setting up in your Gradle script. What it offers is a lot of access to Grails in a very standard and portable manner.
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?
This has been very upsetting for me up till now. Here is what I am trying to do:
IDE I'm using is Intellij IDEA.
Building a grails application.
Grails application specifies two dependencies on in house grails plugins also being developed in IntelliJ as separate grails plugin projects.
Now to make any changes to plugins, I update the source code in plugin projects and use mavan-install (Maven Publisher plugin) to deploy to local Maven repository.
I have to uninstall the plugin in core grails project. Delete the plugin cache from ivy and then run the core grails project which gets the latest copy of plugin from local maven repository.
What's the effective and ideal way to achieve this? A single change makes me do some 5 minutes of labour work to even test and run core application.
Any recommendations/ best practices?
Use inline plugins for this - see section "Specifying Plugin Locations" in http://grails.org/doc/latest/guide/12.%20Plug-ins.html#12.1%20Creating%20and%20Installing%20Plug-ins
By specifying the plugin project directory with grails.plugin.location.<plugin-name> as the location of the installed plugin, you can edit the real files and the changes will affect the test application, and there's no need to sync anything up.
I have recently started a new project using the maven grails archetype - at the time, (a few weeks ago), Grails 1.2.0 was the most recent release. Now that there's a newer release, what are the steps to upgrade? I would assume that since Grails dependencies are defined in the POM, that the POM will need to be updated? Are there any instructions on doing this? Does the maven-grails-plugin handle this? Is this documented anywhere?
Appreciate any pointers. Thanks!
According to this thread:
The recommended way of upgrading grails is simply "grails upgrade" in the project dir when you have downloaded the new version of Grails and set up your paths etc...
Note that I've seen at least one person reporting problems with version 1.2.1 (and the Hibernate plugin), see this thread. There is a workaround in the thread but maybe have a look at the Grails Jira first to see if there are any blocking issues with 1.2.1.
There is no "upgrade" target in the maven grails
plugin, so I'm still looking for information on doing this upgrade with maven.