Submitted by Dieter Vrancken.
…odule name. This is only relevant when a prefix or postfix is specified in the iml or ipr extensions.
… SonarQube Runner. Submitted by Ross Mahony.
…nerates a remote glassfish configuration in IntelliJ IDEA project files.
…nerated IntelliJ IDEA project and module files.
…t files through methods on the ipr extension ipr.mssql_dialect_mapping, ipr.postgres_dialect_mapping and ipr.sql_dialect_mappings
… used in buildfile. Update the buildr gemspec so that rspec is no longer a required dependency. This enables end-users to use a different version of rspec and buildr in the same project. The rspec version MUST be be compatible with the version used by Buildr if rspec features are used from within Buildr. Buildr also issues a warning if the `check` method is called and rspec has not been loaded. The warning includes directions on how to resolve the issue. Submitted by r6p.
…s marked as a developer dependency
Addresses https://issues.apache.org/jira/browse/BUILDR-705 Since usage of rspec support in buildr is optional, it should be listed only as "development dependency" so others can control their rspec versions independently when not using buildr's rspec support.
… is passed to buildr. A long standing bug existed such that if tests failed to compile, and the option Buildr.options.test is set to :all then the compilation error would not result in a failed build. As many people set the Buildr.options.test to :all in their continuous delivery/integration tools, this has caused some problems. This has been fixed by ensuring all the problems associated with the resolving the prerequisites are not caught when Buildr.options.test is set to :all.
artifacts are added as an asset, by using :target_project option.
…ather that artifacts, without forcing a compilation of dependency when parsing buildfile.
…mpile a project that has no src/main/java.