An effort is going on for Netbeans/Gradle integration.
http://blogs.oracle.com/geertjan/entry/gradle_in_netbeans
Maybe we'll see a usable plugin soon :-)
/Paul
--
Paul Merlin - eskatos.github.com
___
qi4j-dev mailing list
[email protected]
h
Quoting Paul Merlin :
Quoting Stanislav Muhametsin :
- IDEA
- Running gradlew idea seemed to generate proper files, however when
using New project -> from existing sources, all the modules were named
"Main", "Main1", "Main2", etc for sources, and "Test", "Test1",
"Test2", etc for test sources
Quoting Stanislav Muhametsin :
> - IDEA
> - Running gradlew idea seemed to generate proper files, however when
> using New project -> from existing sources, all the modules were named
> "Main", "Main1", "Main2", etc for sources, and "Test", "Test1",
> "Test2", etc for test sources. The project se
To sum it up:
- Eclipse
- The eclipse plugin generates the eclipse-related files for
container projects (the ones which are of type POM in Maven), like the
root project, and sub-projects (core, extensions, libraries). These
files must be deleted in order to import all Eclipse projects at o
On 3/28/11 18:28 , Niclas Hedhman wrote:
On Mon, Mar 28, 2011 at 12:53 PM, Rickard Öberg wrote:
Hi,
I'm seeing some abysmally poor Gradle performance. If I do e.g. "gradlew
idea" (generate Idea modules/project), and attach to it using VisualVM, the
CPU usage is somewhere between 1%-10%. I.e. t
On Mon, Mar 28, 2011 at 12:53 PM, Rickard Öberg wrote:
> Hi,
>
> I'm seeing some abysmally poor Gradle performance. If I do e.g. "gradlew
> idea" (generate Idea modules/project), and attach to it using VisualVM, the
> CPU usage is somewhere between 1%-10%. I.e. the poor performance seems to be
> d
Hi,
I'm seeing some abysmally poor Gradle performance. If I do e.g. "gradlew
idea" (generate Idea modules/project), and attach to it using VisualVM,
the CPU usage is somewhere between 1%-10%. I.e. the poor performance
seems to be due to not doing anything.
Does anyone have any idea why this
Gang,
This is a heads-up; I can confirm that the Gradle dependency resolver
is pretty neat. Tests in let's say core-api can have compile and/or
runtime dependency on core-runtime's compile/runtime output without
messing up classpaths or thinking cyclic dependencies are happening.
So, I am integra
On Mon, Nov 15, 2010 at 8:00 AM, Stuart McCulloch wrote:
> FYI: http://www.gradle.org/osgi_plugin.html
Thanks for noticing that.
> btw, I noticed the qi4j core pom locks the release plugin to 2.0-beta-9
> and the git
> branch issue might be fixed in 2.1 - but you probably don't mind about that
On 14 November 2010 16:56, Niclas Hedhman wrote:
> On Mon, Nov 15, 2010 at 12:35 AM, Rickard Öberg
> wrote:
>
> > Ok, so that's good. How about the OSGi thing? Currently we create bundled
> > jar files. Can Gradle do that too?
>
> Since I need that for my R&D at work, rest assure I'll make it wo
On Mon, Nov 15, 2010 at 12:35 AM, Rickard Öberg wrote:
> Ok, so that's good. How about the OSGi thing? Currently we create bundled
> jar files. Can Gradle do that too?
Since I need that for my R&D at work, rest assure I'll make it work.
Worst case it is an Ant call, since BND drives the Maven pk
On 2010-11-14 17.28, Niclas Hedhman wrote:
* How does this impact users of Qi4j? In my project we use Maven
for all dependencies. Will the artifacts still be published into a
Maven repo?
The Qi4j projects will still be published as Maven artifacts as
before. This is a requirement for half the J
On Sun, Nov 14, 2010 at 11:38 PM, Rickard Öberg wrote:
> I looked at the scripts, and they are refreshingly simple.
Yes, that is what I like about it too.
> Some questions:
> * Will the Maven POM's still be there?
For a while...
> * If yes, we need to keep them in synch right, with dependenci
On 2010-11-14 11.37, Niclas Hedhman wrote:
Gang,
I have made a first cut to migrate away from Maven and onto Gradle.
Gradle comes with a pretty nifty task that creates batch/shell scripts
to auto-bootstrap Gradle, so that subsequent developers don't need to
bother with installing Gradle itself.
Gang,
I have made a first cut to migrate away from Maven and onto Gradle.
Gradle comes with a pretty nifty task that creates batch/shell scripts
to auto-bootstrap Gradle, so that subsequent developers don't need to
bother with installing Gradle itself.
In essence, Gradle is based on the Groovy pr
15 matches
Mail list logo
