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