Hans Dockter wrote:
Hello,
we are working intensely on Gradle 0.6. One focus is to make our DSL
more intuitive. To achieve this we are improving the syntax of the DSL
as well as how the different elements play together.
Here is a link to the current draft of the new DSL:
http://docs.codeh
+1 for getting sources by default.
On Thu, Feb 26, 2009 at 6:09 PM, Hans Dockter wrote:
>
> On Feb 26, 2009, at 5:52 PM, Galder Zamarreno wrote:
>
>>
>>
>> Hans Dockter wrote:
>>>
>>> On Feb 24, 2009, at 10:05 PM, Galder Zamarreno wrote:
Hi Hans,
First of all, thanks very much
I don't mind specifying it explicitly :). However, it might be cool to
have single 'javaCompatibility' field that would be used for both
target and source. Most projects use the same value for target &
source anyway.
Cheers,
Szczepan
On Thu, Feb 26, 2009 at 6:59 PM, Levi Hoogenberg
wrote:
> Or 1
On Feb 26, 2009, at 4:09 PM, Martin Vlcek wrote:
I would rather stay more closely to the current syntax and merge
some of your
suggestions to make it more like groovy instead of a java builder:
configurations {
newConf extends:compile, ...
// and alternatively
newConf {
ext
On Feb 26, 2009, at 6:43 PM, Marcus Better wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hans Dockter wrote:
Here is a link to the current draft of the new DSL:
http://docs.codehaus.org/display/GRADLE/Dependencies
We are very interested in your feedback.
I put some comments on the
Hans Dockter wrote:
On Feb 25, 2009, at 7:46 PM, Galder Zamarreno wrote:
Hi,
If I add the following dependency to my build.gradle file:
testCompile "org.jboss.test:jboss-test:1.1.3.GA"
I get this error when doing "gradle eclipse":
:eclipseCp
:: problems summary ::
WARNINGS
On Feb 26, 2009, at 4:30 PM, Hans Dockter wrote:
On Feb 26, 2009, at 4:26 PM, Peter Niederwieser wrote:
I agree with all of Sczcepan's points. The more declarative the
better.
MavenCentralRepo is better than OfficialMavenRepo, even though I once
suggested the latter. :-) Also I've always
Or 1.6 - it's mature enough, right? (Not saying *you* should expect that,
just that if Gradle would default these values, I'd like to see them 1.6,
not 1.5.)
On Thu, Feb 26, 2009 at 6:37 PM, Russel Winder wrote:
> It seems that the Java plugin no longer defines default values for
> sourceCompati
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hans Dockter wrote:
> Here is a link to the current draft of the new DSL:
> http://docs.codehaus.org/display/GRADLE/Dependencies
>
> We are very interested in your feedback.
I put some comments on the wiki page.
Cheers,
Marcus
-BEGIN PGP SIGN
It seems that the Java plugin no longer defines default values for
sourceCompatibility and targetCompatibility. Thus the Gradle file:
usePlugin 'java'
defaultTasks 'compile'
leads to:
Execution failed for task ':compile'.
Cause: The sourceCompatibility and targetCompatibility mu
On Feb 26, 2009, at 1:44 PM, Russel Winder wrote:
I am setting about writing a short book on Gradle and how to use it.
This is not intended to be a reference per se thought there will be an
element of that -- it is really the role of the online documentation
to
be the reference. The idea of
On Feb 26, 2009, at 5:52 PM, Galder Zamarreno wrote:
Hans Dockter wrote:
On Feb 24, 2009, at 10:05 PM, Galder Zamarreno wrote:
Hi Hans,
First of all, thanks very much for your help with this.
Hans Dockter wrote:
On Feb 17, 2009, at 8:24 PM, Galder Zamarreno wrote:
Hi,
Hello to every Gr
Hans Dockter wrote:
On Feb 24, 2009, at 10:05 PM, Galder Zamarreno wrote:
Hi Hans,
First of all, thanks very much for your help with this.
Hans Dockter wrote:
On Feb 17, 2009, at 8:24 PM, Galder Zamarreno wrote:
Hi,
Hello to every Gradle user. This is my first ever post to this list. I
On Feb 26, 2009, at 3:34 PM, szczepiq wrote:
Hi,
we are working intensely on Gradle 0.6. One focus is to make our
DSL more
intuitive.
Cool! Here is my feedback on the syntax.
1. Personally, I'd like to recommend 'declarative' style of naming.
Example:
'create', 'addMavenRepo' (old sy
On Feb 26, 2009, at 4:09 PM, Martin Vlcek wrote:
I would rather stay more closely to the current syntax and merge
some of your
suggestions to make it more like groovy instead of a java builder:
configurations {
newConf extends:compile, ...
// and alternatively
newConf {
ext
On Feb 26, 2009, at 4:26 PM, Peter Niederwieser wrote:
I agree with all of Sczcepan's points. The more declarative the
better.
MavenCentralRepo is better than OfficialMavenRepo, even though I once
suggested the latter. :-) Also I've always wondered why it's
mandatory to
specify a reposito
I agree with all of Sczcepan's points. The more declarative the better.
MavenCentralRepo is better than OfficialMavenRepo, even though I once
suggested the latter. :-) Also I've always wondered why it's mandatory to
specify a repository name, and what this name is used for (log output?).
Cheers,
I would rather stay more closely to the current syntax and merge some of your
suggestions to make it more like groovy instead of a java builder:
configurations {
newConf extends:compile, ...
// and alternatively
newConf {
extends = compile
...
}
}
repositories {
On Feb 25, 2009, at 7:46 PM, Galder Zamarreno wrote:
Hi,
If I add the following dependency to my build.gradle file:
testCompile "org.jboss.test:jboss-test:1.1.3.GA"
I get this error when doing "gradle eclipse":
:eclipseCp
:: problems summary ::
WARNINGS
[NOT FOUND ] org.jboss.jbos
Exactly what I needed thanks.
I added:
File.pathSeparator + classesDir.absolutePath
to the end of taskPath to pick up my non-test classes, and job done!
levi_h wrote:
>
> I do something like
>
> dependencies {
> testCompile ':testng:5.8' // or similar
> }
>
> createTask('test', depends
Gary,
I can strongly recommend pulling Gradle trunk (using Bazaar, Git or even
Subversion :-) and installing it yourself. TestNG support is integrated
and "Just Works" (tm).
All I have to do is add a testCOmpile dependency on a TestNG jar and my
project builds and tests fine.
usePlugin ( 'java'
Hi,
> we are working intensely on Gradle 0.6. One focus is to make our DSL more
> intuitive.
Cool! Here is my feedback on the syntax.
1. Personally, I'd like to recommend 'declarative' style of naming. Example:
'create', 'addMavenRepo' (old syntax), etc are not really declarative
- they express
On Feb 26, 2009, at 2:49 PM, Bernard Niset wrote:
Hi Hans,
As a current Ant and Ivy user, gradle is really the build tool I
have been dreaming about for a long time. So thanks a lot for making
it possible...
I will probably have more requests in the future, but one that comes
from the top
I do something like
dependencies {
testCompile ':testng:5.8' // or similar
}
createTask('test', dependsOn: 'testCompile', overwrite: true) {
ant {
def taskdefPath =
dependencies.testCompile.resolve().join(File.pathSeparator)
def taskPath = taskdefPath + File.pathSeparator
Idiot!
ok, remembering that doing a google search rather than just a forum search
returns more results!
So, Tom Eyckmans is working on all this, so it's not in the current release.
Is there a short-term fix (hint: noob-proof details, if possible!) that I
can use to get my testNG stuff running?
On Feb 26, 2009, at 2:50 PM, GaryMcWilliams wrote:
complete noob here trying to use gradle against a small project. Can
get it
all working except the testng tests. I searched the forum here, got
some
hits against testng, but nothing that give a poor noob any real help!
Anyone offer any hi
On Feb 24, 2009, at 10:05 PM, Galder Zamarreno wrote:
Hi Hans,
First of all, thanks very much for your help with this.
Hans Dockter wrote:
On Feb 17, 2009, at 8:24 PM, Galder Zamarreno wrote:
Hi,
Hello to every Gradle user. This is my first ever post to this
list. I
have a question:
Ev
complete noob here trying to use gradle against a small project. Can get it
all working except the testng tests. I searched the forum here, got some
hits against testng, but nothing that give a poor noob any real help!
Anyone offer any hints on getting my testNG tests to run?
- I note a referenc
Hi Hans,
As a current Ant and Ivy user, gradle is really the build tool I have
been dreaming about for a long time. So thanks a lot for making it
possible...
I will probably have more requests in the future, but one that comes
from the top of my head: is it possible to use a native ivy
configu
On Feb 25, 2009, at 9:26 AM, Levi Hoogenberg wrote:
Ah, good to know. I got lazy and just added an empty 'default'
configuration to my repository. Glad to see you got it working.
On Wed, Feb 25, 2009 at 9:21 AM, Bernard Niset
wrote:
Thanks Levi and Neil,
I finally got it working with thi
Hello,
we are working intensely on Gradle 0.6. One focus is to make our DSL
more intuitive. To achieve this we are improving the syntax of the DSL
as well as how the different elements play together.
Here is a link to the current draft of the new DSL:
http://docs.codehaus.org/display/GRADL
I am setting about writing a short book on Gradle and how to use it.
This is not intended to be a reference per se thought there will be an
element of that -- it is really the role of the online documentation to
be the reference. The idea of the book is to be a tutorial introduction
for people, es
32 matches
Mail list logo
