Sounds like a hasle to require a VM... unless that VM would include
everything to get started.

Just setting up eclipse to be inline with the coding guidelines in GWT and
setting up all the libraries etc are really painful and you need to follow
the steps very carefully (and hopefully no dependency has been changed
since the document was written).

What we do (in an enterprise environment) is to just have a zip or machine
image ready to be installed on a new machine. After 30 minutes or so a new
developer is ready to code.


On Sat, Oct 18, 2014 at 7:25 PM, Brandon Donnelson <[email protected]>
wrote:

> Setting up an images seems ideal to me to get going with less steps.
>
>
> On Friday, October 17, 2014 3:04:05 PM UTC-7, Thomas Broyer wrote:
>>
>>
>>
>> On Friday, October 17, 2014 5:11:10 PM UTC+2, Rene Hangstrup Møller wrote:
>>>
>>> I am just going to repeat my reply from google+ here:
>>>
>>> If you want to encourage contributions from the community, you should
>>> work on lowering the barriers to entry. Pick standard tools that work on a
>>> variety of platforms.
>>>
>>> What went wrong with the conversion to gradle?
>>>
>>
>> Nothing went "wrong", but handling external dependencies still requires
>> that you "svn co" and "svn up" the gwt-tools repo, and Gradle will most
>> likely impact how we'd later modularize GWT (not necessarily a bad thing,
>> but something to be aware of).
>> I'll make a comparison matrix of Gradle vs. Buck vs. Pants when I find
>> time.
>>
>>
>>> Why do you need some obscure build system where first sentence on the
>>> install page is "As of September 2014, alas, Pants is not something you can
>>> just install and use."
>>>
>>
>> It also says that “Once it’s set up, most folks should be able to use the 
>> Pants
>> Conceptual Overview <https://pantsbuild.github.io/first_concepts.html>
>> and not worry about these things.”, i.e. “pants goal idea” or “pants goal
>> eclipse” to setup your IDE, “pants goal jar” and “pants goal test” for
>> everyday use, “pants goal publish” or “pants goal bundle” to build GWT in
>> order to use it in your projects (deploy it in a Maven repo, or create a
>> ZIP with all needed JARs)
>> Note: I haven't tried Pants yet, so this is all from the docs.
>> Existing repositories seem to have a bunch of scripts in them so you can
>> just “git clone” and run “./pants” and Pants will download itself, just
>> like Gradle with ./gradlew. And BUILD files are easy to read and
>> self-explanatory.
>>
>  --
> You received this message because you are subscribed to the Google Groups
> "GWT Contributors" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-web-toolkit-contributors/5f8f2899-82a2-4b06-aca3-9f2554546d3c%40googlegroups.com
> <https://groups.google.com/d/msgid/google-web-toolkit-contributors/5f8f2899-82a2-4b06-aca3-9f2554546d3c%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Contributors" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CABrJHW3eNQEA5Ne9JY4w4AbvqDUvXWS%3D%2B0L-8k%3D%3DxuThaXPxXA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to