[
https://issues.apache.org/jira/browse/BUILDR-316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12764866#action_12764866
]
Alex Boisvert commented on BUILDR-316:
--------------------------------------
I think the requirements would be 1) we have a committer volunteering to
maintain it, 2) specs and 3) documentation.
We moved some tasks into addons because they didn't have specs but we didn't
want to remove them completely. Today, I would argue to move them out and let
them evolve independently of Buildr.
> GWT generation task
> -------------------
>
> Key: BUILDR-316
> URL: https://issues.apache.org/jira/browse/BUILDR-316
> Project: Buildr
> Issue Type: New Feature
> Components: Extensions
> Affects Versions: 1.3.4
> Reporter: Antoine Toulme
> Attachments: gwt.rb
>
>
> This is an addon, so it comes wihout specs. It works for me...
> This task works with GWT 1.5.3.
> Here is how to call the task in a project:
> gwt = gwt("myApp", {:max_memory => "512m", :style => "OBF",
> :jvmargs => ["-Djava.awt.headless=true"], :classpath => [GWT, JS_LIBS,
> GWT_RUNTIME, JUNIT] })
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
