Charlie,
It gets stranger and stranger. From my parent module I can run mvn
compiler:compile and it works fine. I get this output when it gets to
my gwt project
[INFO] [gwt:compile {execution: default}]
[INFO] establishing classpath list (buildClaspathList - scope =
COMPILE)
[INFO] google.webtoolkit.home (gwtHome) *not* set, using project POM
for GWT dependencies
Compiling module demo.core.web.DemoSalesUI
However, If i am in my web project and I run mvn gwt:compile or mvn
gwt:mergewebxml I get the error i have previously posted.
In my parent pom.xml all i have is a list of sub modules and junit 4.5
plugin.
There must be something getting passed to the gwt compiler
incorrectly.
-chris worley
On Jan 23, 8:27 am, cworley420 <[email protected]> wrote:
> Charlie,
>
> Well, I guess my problem is not solved. I started getting the problem
> again so, I decided to delete my repository (~/.m2/repository). Then
> I did the following steps
>
> 1) Install jta 1.0.1B
> 2) mvn install (on my parent module, of about seven projects)
> 3) mvn gwt:compile (on my web sub module)
>
> then i get:
> [INFO] Compile GWT module com.foobar.CoreDataConstant
>
> Here is the module that should get compiled. (my pom.xml is in a
> previous post)
>
> I have modified the package names to hide sensitive info. So, if its
> different from the previous post thats why. But, you can take my word
> that the packages and folders line up. Plus when I use the jar source
> i see all the stuff gwt needs.
>
> As you said earlier maybe it is a gwt problem, not a maven-gwt plugin
> problem. How can I determine what is passed to gwt to compile? Not
> sure why it thinks the module it errors out on should have an entry
> point. Its not the first one listed int his module, which is my
> compile target. But, if i rename the one it thinks should have an
> entry point it goes to the next one found on the classpath and expects
> an entry point on that one.
>
> <module>
> <source path="ui"/>
>
> <inherits name="com.google.gwt.user.User"/>
>
> <inherits name="com.foobar.web.FooBarClient"/>
>
> <inherits name="com.foobar.web.FooBarDTO"/>
>
> <inherits name="com.foobar.CoreData"/>
>
> <inherits name=com.foobar.CoreDataConstant"/>
>
> <inherits name="com.foobar.CoreDataHelper"/>
>
> <inherits name="com.foobar.CoreDataHibernate"/>
>
> <entry-point class="com.foobar.web.ui.DemoModule"/>
>
> </module>
> -chris worley
>
> On Jan 21, 6:52 am, Charlie Collins <[email protected]> wrote:
>
> > Cool, glad you got it going. I wasn't even looking at the repo
> > direction, but I should have been, that has happened to me before
> > (sometimes the files there get corrupted). Good catch.
>
> > On Jan 20, 10:45 pm, cworley420 <[email protected]> wrote:
>
> > > Got it working.
>
> > > in my last post i explained that it worked on my desktop but stopped
> > > working on my laptop.
>
> > > Not sure what happened. But, i copied my ~/.m2/repository directory
> > > off of my desktop and replaced the one on my laptop.
>
> > > Now everything works again for the gwt plugin. Not sure how my
> > > repository got screwed up. Was not the settings file because i have
> > > nothing in it anymore.
>
> > > -chris worley
>
> > > On Jan 19, 3:57 pm, Charlie Collins <[email protected]> wrote:
>
> > > > I use multiple modules often, and usually only one has an entry point,
> > > > works fine for me. I use GWT inheritance in my modules (saying
> > > > "inherits from" is not enough info). At any rate, GWT-Maven just
> > > > hands off the "compileTargets" to the GWT compiler itself, it doesn't
> > > > do the work on it's own. That error message means, the GWT compiler
> > > > can't find the entry point for the module you are specifying using the
> > > > current classpath. Post your POM and module, and any other info if
> > > > you still need help. GWT-Maven does not (should not anyway) just find
> > > > the next "available" module, it uses the configuration specified (it's
> > > > possible though, depending on how you are doing inheritance, that one
> > > > module might lead to another).
>
> > > > On Jan 18, 7:27 pm, cworley420 <[email protected]> wrote:
>
> > > > > Recently I had to modify my pom file to use a different version of
> > > > > maven-gwt than I previously was because it was not longer available.
> > > > > The current version I am using is "2.0-beta26". Everything worked
> > > > > fine for a few days and then maven started ignoring the compile target
> > > > > I specified in the xml file. It appears to pick up the first one it
> > > > > find on the file system. If i rename that one, it goes to the next
> > > > > one.
>
> > > > > Basically com.foobar.DemoModule is contains the entry point and is the
> > > > > compile target i want compiled. DemoModeul inherits from DemoData
> > > > > which is the data model and has not entry points.
>
> > > > > Does anyone know why maven-gwt is ignoring the compileTarget is
> > > > > specify and attempt to find one to compile?
>
> > > > > [INFO] [gwt:compile]
> > > > > [INFO] Compile GWT module com.foobar.DemoData
> > > > > [ERROR] Module has no entry points defined
> > > > > [ERROR] Build failed
>
> > > > > Here is my configuration:
>
> > > > > -----------------------------------------------------------------------
>
> > > > > <repositories>
> > > > > <repository>
> > > > > <id>gwt-maven</id>
> > > > >
> > > > > <url>http://gwt-maven.googlecode.com/svn/trunk/mavenrepo/</
> > > > > url>
> > > > > </repository>
> > > > > </repositories>
>
> > > > > <pluginRepositories>
> > > > > <pluginRepository>
> > > > > <id>gwt-maven</id>
> > > > > <url>http://gwt-maven.googlecode.com/svn/trunk/mavenrepo/</
> > > > > url>
> > > > > </pluginRepository>
> > > > > </pluginRepositories>
>
> > > > > ...
> > > > > ...
> > > > > ...
>
> > > > > <plugin>
> > > > > <groupId>com.totsp.gwt</groupId>
> > > > > <artifactId>maven-googlewebtoolkit2-plugin</
> > > > > artifactId>
> > > > > <version>2.0-beta26</version>
> > > > > <configuration>
> > > > > <logLevel>INFO</logLevel>
> > > > > <!-- style: PRETTY, DETAILED, OBF -->
> > > > > <style>DETAILED</style>
> > > > > <runTarget>com.foobar.DemoModule/DemoModule.jsp</
> > > > > runTarget>
> > > > > <compileTargets>
> > > > > <param>com.foobar.DemoModule</param>
> > > > > </compileTargets>
> > > > > </configuration>
> > > > > <executions>
> > > > > <execution>
> > > > > <goals>
> > > > > <!--
> > > > > <goal>generateClientBeans</goal>
> > > > > -->
> > > > > <goal>mergewebxml</goal>
> > > > > <goal>compile</goal>
> > > > > <!-- goal>testGwt</goal -->
> > > > > </goals>
> > > > > </execution>
> > > > > </executions>
> > > > > </plugin>
>
> > > > > -----------------------------------------------------------------------
>
> > > > > -chris worley
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"gwt-maven" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/gwt-maven?hl=en
-~----------~----~----~----~------~----~------~--~---
