Re: [ANN] net.ltgt.gwt.maven:gwt-maven-plugin:1.0-alpha-1 released

As the error says, gwt:compile needs the module name to be supplied,
and it obviously isn't on "EventBinder (Parent)" which has
packaging=pom.

Why are you calling gwt:compile directly? gwt:compile is bound to the
prepare-package phase of the gwt-app packaging so just use "mvn
package" (or "mvn prepare-package").

On Wed, Jun 5, 2013 at 6:32 PM, Lexis Nexis <lexisnexis5490@gmail.com> wrote:
> I got the following error Once I run mvn -V gwt:compile for
> gwteventbinder-master. What am I missing?
>
> ----------------------------------------------------
> C:\gwt\gwteventbinder-master>c:\apache\maven\3.0.5\bin\mvn -V gwt:compile
> Apache Maven 3.0.5 (r01de14724cdef164cd33c7c8c2fe155faf9602da; 2013-02-19
> 08:51:28-0500)
> Maven home: c:\Apache\maven\3.0.5\bin\..
> Java version: 1.6.0_35, vendor: Sun Microsystems Inc.
> Java home: C:\Program Files\Java\jdk1.6.0_35\jre
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows"
> [INFO] Scanning for projects...
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Reactor Build Order:
> [INFO]
> [INFO] EventBinder (Parent)
> [INFO] EventBinder
> [INFO] EventBinder Sample Application
> [INFO]
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Building EventBinder (Parent) 1.0.1-SNAPSHOT
> [INFO]
> ------------------------------------------------------------------------
> [INFO]
> [INFO] --- gwt-maven-plugin:1.0-alpha-2:compile (default-cli) @
> eventbinder-parent ---
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Reactor Summary:
> [INFO]
> [INFO] EventBinder (Parent) .............................. FAILURE [0.213s]
> [INFO] EventBinder ....................................... SKIPPED
> [INFO] EventBinder Sample Application .................... SKIPPED
> [INFO]
> ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Total time: 2.130s
> [INFO] Finished at: Wed Jun 05 12:30:33 EDT 2013
> [INFO] Final Memory: 8M/151M
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] Failed to execute goal
> net.ltgt.gwt.maven:gwt-maven-plugin:1.0-alpha-2:compile (default-cli) on
> project eventbinder-parent: The parameters 'mo
> duleName' for goal net.ltgt.gwt.maven:gwt-maven-plugin:1.0-alpha-2:compile
> are missing or invalid -> [Help 1]
>
> --------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>
> On Wednesday, June 5, 2013 5:36:32 AM UTC-4, Thomas Broyer wrote:
>>
>>
>>
>> On Tuesday, June 4, 2013 8:24:53 PM UTC+2, Lexis Nexis wrote:
>>>
>>> I have the following two questions:
>>> 1. Can we have more sub source folders under src/main such as
>>> src/main/java, src/main/gwt for GWT, src/main/birt,for BIRT, src/main/config
>>> for Spring Java configuration.
>>
>>
>> gwt-lib and gwt-app packagings are for GWT code only (gwt-app will only
>> package the generated JS/HTML); you shouldn't mix client and server code in
>> the same Maven module (you can make a "shared" module, but then I think you
>> shouldn't bundle your gwt.xml, sources and super-sources within that JAR;
>> YMMV). Have a look at the e2e integration test for an example, and see
>> http://blog.ltgt.net/announcing-gwt-maven-archetypes-project/ for the
>> rationale (well, I think I explained it in this blog post).
>> Otherwise, well, they'll use all source roots and resources so you can
>> have as many as you want (e.g. some plugin that generates Java sources and
>> adds the folder as a source root; or using the build-helper-maven-plugin to
>> add a folder from src/main as a source root; it doesn't matter where the
>> source root comes from).
>>
>>>
>>> 2. I have a huge project (> 1000 database tables). I like to generate
>>> many gwtar files for my internal team in order to reduce gwt compilation
>>> time. How do I do it? Should I use CompileModule from prompt? I like to get
>>> one script how to generate a gwtar file?
>>
>>
>> I'd call CompileModule using the exec-maven-plugin then. At the
>> process-classes or prepare-package phases, everything (compiled classes and
>> their sources, and resources) should be in the
>> ${project.build.outputDirectory} so you shouldn't have to deal with the
>> classpath and can just use ${project.build.outputDirectory} as the -out
>> folder for CompileModule.
>>
>> I'm curious now: did you measure the gains? I've been told Google actually
>> doesn't use gwtar for their internal libs and given how their build system
>> works they can't take advantage of the PersistentUnitCache from previous
>> runs; admittedly they have huge build resources but we also know that speed
>> matters for them, so if they could save some time in downstream compilations
>> I'd think they'd use the existing tool (CompileModule) for that?
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Google Web Toolkit" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/google-web-toolkit/O8HaPzExxhc/unsubscribe?hl=en.
> To unsubscribe from this group and all its topics, send an email to
> google-web-toolkit+unsubscribe@googlegroups.com.
> To post to this group, send email to google-web-toolkit@googlegroups.com.
> Visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>



--
Thomas Broyer
/tɔ.ma.bʁwa.je/

--
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.