hi
I tried to use sonar in a multiple-projects env and failure with
outofmemory error.
I have 4 projects and in each project there are only several small (less
than 10) java classes. So the size of projects / class
is not the reason of outofmemory error.
When I use 'gradle -a sonar'
Hi
I tried to use ivy dual resolver and ivy shared repository together to
handle complex dependency management in BIG product.
In my solution, I will have a ivy shared repository to share product
releases in a shared file system such as nfs. And a dual resolver
will be used to limit the
I think it is misleading in the sense that the error is caused by the
project structure being incorrect.
I spent a long time trying to work out why it wasn't finding JAVA_HOME even
though it was set correctly - to clear the problem, all I had to do was
correct the project structure, which doesn't
It can't be that this is such a weird case. I'm sure I'm nit doing it right. A
nudge in the right direction maybe.
Sent from my iPad
On 19/05/2011, at 18:30, Luis Muniz neur0ma...@gmail.com wrote:
Hi
I'm discovering gradle, and though it is really nice, the learning curve is
steeper than
Ok,
Searching around I found this approach, which works:
class Version {
String defaultVersion='0.1'
String releaseType='SNAPSHOT'
def project
String toString() {
switch (project.name) {
case 'myProject':
1.0-${releaseType}
hi there,
We're actually refactoring the griffon build to a multiproject build. At
the moment we avoid resolving transitive dependencies automatically
using the transitive flag. In the dist task of the rootProject I have a
snippet like this:
---
dependencies{
runtime
Hi again,
I recognized that in a project, where no plugin is applied, the default
value for destinationDir is set to the root directory of the project. In
my humble opinion it would be better to set it to build/dist per
default. what do you think?
--
---
regards René
Sorry for the late response. Could you file a Jira?
This is something we really want to fix.
Hans
--
Hans Dockter
Founder, Gradle
http://www.gradle.org, http://twitter.com/gradleware
CEO, Gradleware - Gradle Training, Support, Consulting
http://www.gradleware.com
On Mon, May 9, 2011 at 2:56
Xiaojian Ao wrote:
It seems a bug in gradle ?
Hard to say. Basically all we do is to call the Sonar API. And as far as I
can tell, we don't hold on to anything after a subproject has been analyzed.
I'll have to look at this in the profiler again.
In order to analyze the whole Gradle
I can confirm that running a multi-project build that invokes sonar on several
sub-projects (in this case 5 for me) also fails with an OOME. It fails once
reaching the 3rd or 4th project it encounters -- cannot remember.
Invoking sonar individually on any of the sub-projects does not fail.
We
Likely, you'll want to do what we've done.
war {
classpath = jar.outputs.files + configurations.runtime -
configurations.providedRuntime
}
I suppose this functionality should be added to the core war plugin so
that the user can choose which behavior is desired, but it'd have to be a bit
Hi all,
I'm glad to see that there is so much interest in the gradle tooling
and that there is so much passionate discussion. I just wanted to
send out a reminder that this is primarily for gradle users on the
command line. A more appropriate place to discuss gradle-tooling
issues is the
DualResolver is an Ivy class. It doesn't have a convenience method like
Gradle's RepositoryHandler class to add and configure a resolver at the same
time. However, you can use Gradle's Project.configure() method to accomplish
something similar:
// calls RepositoryHandler.add(Object, Closure)
Since there is no error to run sonar individually to each subproject, can we
change the way that gradle run sonar for multiple projects?
We can start a jvm and run sonar for one project, when finished we can exist
the jvm and restart a new jvm to run sonar for next subproject.Running Sonar
in one
When I run gradle test I get something like this as an output:
Test com.softwareag.bas.plugins.LocalizationPluginTest FAILED
5 tests completed, 1 failure
FAILURE: Build failed with an exception.
* What went wrong:
Execution failed for task ':bas-plugins-localization:test'.
Cause: There were
Hello,
is there an EAR plugin?
If not, does anyone have a sample?
Thanks a lot,
Jefferson
Hi Roger, James,
Some of the things you both mentioned:
- trouble with the menus being greyed
- problems with single module projects
Sound like they are bugs that should be fixed. I would encourage you to
raise a bug issue about those problems, especially if they are reproducible.
If you
Yeah Kris -- it makes sense that it wouldn't work (picking up the
other configured jars).
I guess the trick (as mentioned in the plugin docs).. is how this
works when mixed with other project "natures".. since the GWT one of
course wants to put its own GWT into the
On 20/05/2011, at 2:30 AM, Luis Muniz wrote:
Hi
I'm discovering gradle, and though it is really nice, the learning curve is
steeper than I thought when you start doing funkier stuff. This is obviously
because I am uninformed both in the gradle implementatino and in the
complexity of
On 21/05/2011, at 2:21 AM, phil swenson wrote:
When I run gradle test I get something like this as an output:
Test com.softwareag.bas.plugins.LocalizationPluginTest FAILED
5 tests completed, 1 failure
FAILURE: Build failed with an exception.
* What went wrong:
Execution failed for
I'll take a look next week. Seems like a good idea to put in gradle itself.
phil
On Fri, May 20, 2011 at 2:42 PM, Adam Murdoch
adam.murd...@gradleware.com wrote:
On 21/05/2011, at 2:21 AM, phil swenson wrote:
When I run gradle test I get something like this as an output:
Test
Was curious how most of the people here, who work/use gradle.. also use
their IDE of choice.
In my case.. i've relied on doing tasks like this:
subprojects {
..
stuff
..
task gatherSubProjectDependencies(dependsOn:
configurations.runtime.buildArtifacts, type: Copy) {
into('libs')
Have you tried using the idea or eclipse plugin for gradle?
On May 20, 2011 5:34 PM, Roger Studner rstud...@gmail.com wrote:
Was curious how most of the people here, who work/use gradle.. also use
their IDE of choice.
In my case.. i've relied on doing tasks like this:
subprojects {
..
Xiaojian Ao wrote:
We can start a jvm and run sonar for one project, when finished we can
exist
the jvm and restart a new jvm to run sonar for next subproject.Running
Sonar
in one subjuect is not dependent any other subproject, so I think this is
a
simple way to work around this issue.
M A wrote:
Have you tried using the idea or eclipse plugin for gradle?
On May 20, 2011 5:34 PM, Roger Studner lt;rstud...@gmail.comgt; wrote:
Was curious how most of the people here, who work/use gradle.. also use
their IDE of choice.
You should definitely use the IDEA/Eclipse plugins
Rene Groeschke wrote:
but when executing dist the dependencies of project cli are calculated
transitive again. It seems that gradle does not respect the transitive
= false flag of the configurations in the submodule cli.
Is this intended behaviour or a bug?
I haven't looked deeply into
Bret Marzolf wrote:
In the short time I've worked with Gradle, I've gotten the sense that
Gradle expects that your gradle.build file is at the top level of your
project source tree but what if you wanted to set things up such that
gradle.build was in one location and all of your project
Paulo Pires wrote:
This is the output of ./gradlew -d grails-test-app and it's not helping
me
(the noob) to find my problem.
Can anyone more experienced help me, please?
The log output seems to indicate that some of the integration tests failed.
Did you have a look at the test report
Graeme Rocher-4 wrote:
I can't seem to work out how to produce a combined dependency report.
Seems like it isn't supported yet and you'd have to merge the reports
yourself.
Graeme Rocher-4 wrote:
Also it is fairly hard to work out what rendering options are
available since the javadoc
Jefferson Magno Solfarello wrote:
is there an EAR plugin?
I'm not aware of an existing EAR plugin, but there is a patch waiting to be
applied.
--
Peter Niederwieser
Principal Engineer, Gradleware
http://gradleware.com
Creator, Spock Framework
http://spockframework.org
Blog:
Rene Groeschke wrote:
I recognized that in a project, where no plugin is applied, the default
value for destinationDir is set to the root directory of the project. In
my humble opinion it would be better to set it to build/dist per
default. what do you think?
I guess the idea is that
31 matches
Mail list logo
