Adam, AWESOME! And congratulations :) This is EXCELLENT! I am very excited about this. Unfortunately, my work day just ended (after about 11 hours,) so I need to take a break, but I will try this out tomorrow. I wonder, does the Gradle eclipse plugin work well enough to resolve dependencies and compile the java file? Again - Thrilled, ~Lincoln On Mon, Aug 19, 2013 at 8:29 PM, Adam Wyłuda <adamwyl92(a)gmail.com&gt; wrote: > Hi, > > I'd like to present you first screenshot of working project creation with > Gradle addon. > > As you could see there are three text editors showing important aspects of > this experiment: > - build.gradle - created by Gradle facets, also updated by JPA - Setup > Forge command (which added managed dependency, but Eclipse log shows it > couldn't resolve something) > - MyEntity.java - class generated using JPA - New entity option > - pom.xml - I don't know how it got here, but I'm sure it is not used, as > Eclipse log shows that Gradle is being run to obtain info about project > (and very interesting thing - performance is much better than in Arquillian > tests, for each Gradle run it seems to take only about 0.3 seconds) > > Project build file was entirely created and modified using only Gradle > facets (if you don't believe you can pull latest version and check it > yourself :)). > > Screenshot: > [image: Obraz w treści 1] > -- Lincoln Baxter, III http://ocpsoft.org "Simpler is better."

_______________________________________________ forge-dev mailing list forge-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/forge-dev

...cool - how is your arquillian test run done ? just run junit from eclipse or run via gradle or how ? Just wondering what makes a difference here since maven aren't involved in a arqullian test run from eclipse. and what is forge.gradle ? /max On Mon, Aug 19, 2013 at 08:34:50PM -0400, Lincoln Baxter, III wrote: > Adam, > > AWESOME! And congratulations :) This is EXCELLENT! > > I am very excited about this. Unfortunately, my work day just ended (after > about 11 hours,) so I need to take a break, but I will try this out > tomorrow. > > I wonder, does the Gradle eclipse plugin work well enough to resolve > dependencies and compile the java file? > > Again - Thrilled, > ~Lincoln > > > On Mon, Aug 19, 2013 at 8:29 PM, Adam Wyłuda <adamwyl92(a)gmail.com&gt; wrote: > > Hi, >> >> I'd like to present you first screenshot of working project creation with >> Gradle addon. >> >> As you could see there are three text editors showing important aspects >> of >> this experiment: >> - build.gradle - created by Gradle facets, also updated by JPA - Setup >> Forge command (which added managed dependency, but Eclipse log shows it >> couldn't resolve something) >> - MyEntity.java - class generated using JPA - New entity option >> - pom.xml - I don't know how it got here, but I'm sure it is not used, as >> Eclipse log shows that Gradle is being run to obtain info about project >> (and very interesting thing - performance is much better than in >> Arquillian >> tests, for each Gradle run it seems to take only about 0.3 seconds) >> >> Project build file was entirely created and modified using only Gradle >> facets (if you don't believe you can pull latest version and check it >> yourself :)). >> >> Screenshot: >> [image: Obraz w treści 1] >> >> > > > -- > Lincoln Baxter, III > http://ocpsoft.org > "Simpler is better." > ______________________________**_________________ > forge-dev mailing list > forge-dev(a)lists.jboss.org > https://lists.jboss.org/**mailman/listinfo/forge-dev<https://lists.jbo... >

Hey Max, I usually run it with Eclipse and first run of Gradle takes about 5 seconds, I think that Gradle caches build files and that's why it works faster after that, but for every test new project is created so why it always takes so much.

I think the solution for this may be installing forge.gradle in user/.gradle directory, so it will compiled only once, which will result in better test performance. About forge.gradle, it is library adding non-standard functionality to Gradle, which is used in Maven and project facets requires that, like profiles, setting archive name and managed/direct dependency support. Also it adds forgeOutput task which is used by addon to read effective project model (evaluated by running Gradle). In future if Gradle tooling API supports that we could remove it, but for now there is no better way to get information about the Gradle project. You can find forge.gradle contents here: https://github.com/forge/addon-gradle/blob/master/impl/src/main/resources...

2013/8/20 Max Rydahl Andersen <manderse(a)redhat.com&gt; > ...cool - how is your arquillian test run done ? just run junit from > eclipse or run via gradle or how ? > Just wondering what makes a difference here since maven aren't involved in > a arqullian test run from eclipse. > > and what is forge.gradle ? > > /max > > > On Mon, Aug 19, 2013 at 08:34:50PM -0400, Lincoln Baxter, III wrote: > >> Adam, >> >> AWESOME! And congratulations :) This is EXCELLENT! >> >> I am very excited about this. Unfortunately, my work day just ended (after >> about 11 hours,) so I need to take a break, but I will try this out >> tomorrow. >> >> I wonder, does the Gradle eclipse plugin work well enough to resolve >> dependencies and compile the java file? >> >> Again - Thrilled, >> ~Lincoln >> >> >> On Mon, Aug 19, 2013 at 8:29 PM, Adam Wyłuda <adamwyl92(a)gmail.com&gt; wrote: >> >> Hi, >>> >>> I'd like to present you first screenshot of working project creation with >>> Gradle addon. >>> >>> As you could see there are three text editors showing important aspects >>> of >>> this experiment: >>> - build.gradle - created by Gradle facets, also updated by JPA - Setup >>> Forge command (which added managed dependency, but Eclipse log shows it >>> couldn't resolve something) >>> - MyEntity.java - class generated using JPA - New entity option >>> - pom.xml - I don't know how it got here, but I'm sure it is not used, as >>> Eclipse log shows that Gradle is being run to obtain info about project >>> (and very interesting thing - performance is much better than in >>> Arquillian >>> tests, for each Gradle run it seems to take only about 0.3 seconds) >>> >>> Project build file was entirely created and modified using only Gradle >>> facets (if you don't believe you can pull latest version and check it >>> yourself :)). >>> >>> Screenshot: >>> [image: Obraz w treści 1] >>> >>> >> >> >> -- >> Lincoln Baxter, III >> http://ocpsoft.org >> "Simpler is better." >> > > > > ______________________________**_________________ >> forge-dev mailing list >> forge-dev(a)lists.jboss.org >> https://lists.jboss.org/**mailman/listinfo/forge-dev<https://lists.jbo... >> > >

Hey Max, I don't think that he meant there was a difference in test speet bewteen build/eclipse. Just that the first test run (from anywhere) takes longer because it is downloading and caching files. Subsequent tests run faster.

Regarding the information that can't be resolved from the gradle tooling API, there is quite a bit, such as it's impossible to get dependency information without doing what adam has done! Silly - hardly a "tooling API" if you ask me!

Take a look at the file adam linked. That shows pretty much everything that gradle does not provide I think, but Adam can give a more comprehensive list.

On Wed, Aug 21, 2013 at 3:21 AM, Max Rydahl Andersen <manderse(a)redhat.com&gt;wrote: > On Tue, Aug 20, 2013 at 03:29:46PM +0200, Adam Wyłuda wrote: > >Hey Max, > > > >I usually run it with Eclipse and first run of Gradle takes about 5 > >seconds, I think that Gradle caches build files and that's why it works > >faster after that, but for every test new project is created so why it > >always takes so much. > > not following - eclipse caches build files too; it doesn't need to build > anything > so why would gradle be faster to run the arquillian tests than eclipse ? > Maybe I misunderstood your initial comment...just read it as arquillian > became > faster to run because it was using gradle...which might be true - but just > trying > to grok what magic it does (caching build files can't be the answer since > eclipse does > that too and just launches the vm with junit which triggers arquillian). > > >I think the solution for this may be installing forge.gradle in > >user/.gradle directory, so it will compiled only once, which will result > in > >better test performance. > > > >About forge.gradle, it is library adding non-standard functionality to > >Gradle, which is used in Maven and project facets requires that, like > >profiles, setting archive name and managed/direct dependency support. Also > >it adds forgeOutput task which is used by addon to read effective project > >model (evaluated by running Gradle). In future if Gradle tooling API > >supports that we could remove it, but for now there is no better way to > get > >information about the Gradle project. You can find forge.gradle contents > >here: > > > https://github.com/forge/addon-gradle/blob/master/impl/src/main/resources... > > ah okey interesting - and yeah, this is example of what eclipse would need > too... > the gradle eclipse plugin uses the tooling api afaik (albeit very slow > last time I looked). > > What are the specifics you can't get from gradle tooling api ? > > /max > > > > > > >2013/8/20 Max Rydahl Andersen <manderse(a)redhat.com&gt; > > > >> ...cool - how is your arquillian test run done ? just run junit from > >> eclipse or run via gradle or how ? > >> Just wondering what makes a difference here since maven aren't involved > in > >> a arqullian test run from eclipse. > >> > >> and what is forge.gradle ? > >> > >> /max > >> > >> > >> On Mon, Aug 19, 2013 at 08:34:50PM -0400, Lincoln Baxter, III wrote: > >> > >>> Adam, > >>> > >>> AWESOME! And congratulations :) This is EXCELLENT! > >>> > >>> I am very excited about this. Unfortunately, my work day just ended > (after > >>> about 11 hours,) so I need to take a break, but I will try this out > >>> tomorrow. > >>> > >>> I wonder, does the Gradle eclipse plugin work well enough to resolve > >>> dependencies and compile the java file? > >>> > >>> Again - Thrilled, > >>> ~Lincoln > >>> > >>> > >>> On Mon, Aug 19, 2013 at 8:29 PM, Adam Wyłuda <adamwyl92(a)gmail.com&gt; > wrote: > >>> > >>> Hi, > >>>> > >>>> I'd like to present you first screenshot of working project creation > with > >>>> Gradle addon. > >>>> > >>>> As you could see there are three text editors showing important > aspects > >>>> of > >>>> this experiment: > >>>> - build.gradle - created by Gradle facets, also updated by JPA - Setup > >>>> Forge command (which added managed dependency, but Eclipse log shows > it > >>>> couldn't resolve something) > >>>> - MyEntity.java - class generated using JPA - New entity option > >>>> - pom.xml - I don't know how it got here, but I'm sure it is not > used, as > >>>> Eclipse log shows that Gradle is being run to obtain info about > project > >>>> (and very interesting thing - performance is much better than in > >>>> Arquillian > >>>> tests, for each Gradle run it seems to take only about 0.3 seconds) > >>>> > >>>> Project build file was entirely created and modified using only Gradle > >>>> facets (if you don't believe you can pull latest version and check it > >>>> yourself :)). > >>>> > >>>> Screenshot: > >>>> [image: Obraz w treści 1] > >>>> > >>>> > >>> > >>> > >>> -- > >>> Lincoln Baxter, III > >>> http://ocpsoft.org > >>> "Simpler is better." > >>> > >> > >> > >> > >> ______________________________**_________________ > >>> forge-dev mailing list > >>> forge-dev(a)lists.jboss.org > >>> https://lists.jboss.org/**mailman/listinfo/forge-dev< > https://lists.jboss.org/mailman/listinfo/forge-dev> > >>> > >> > >> > _______________________________________________ > forge-dev mailing list > forge-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/forge-dev > -- Lincoln Baxter, III http://ocpsoft.org "Simpler is better."

_______________________________________________ forge-dev mailing list forge-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/forge-dev