Thanks for your quick reply.
Yes, you are right, I was using the wrong version.
This actually was my first assumption, and I tryed the rm -rf $
{locarepositoy} magic before posting here. It did not help.

I know why I am not getting the newest version - it is not stated in
your repository metadata:

http://gwt-maven.googlecode.com/svn/trunk/mavenrepo/com/totsp/gwt/maven-googlewebtoolkit2-plugin/maven-metadata.xml

Is this a bug or a feature?

Any way, to get the plugin I had to
add

                <pluginManagement>
                        <plugins>
                                <plugin>
                                        <groupId>com.totsp.gwt</groupId>
                                        <artifactId>
                                                maven-googlewebtoolkit2-plugin
                                        </artifactId>
                                        <version>2.0-beta23</version>
                                </plugin>
                        </plugins>
                </pluginManagement>

to my build section, so it is building now. I am putting this here
because it might be that
someone else gets the same problem.

So now I am stuck to the beta23, I won't get any updates
automatically.

brgds,

Papick



On 1 Okt., 14:39, Charlie Collins <[EMAIL PROTECTED]> wrote:
> I have never seen that one before.  If you are using 2.0-beta23
> then . . .
>
> Line 325 of AbstractGWTMojo is this:
> Thread.currentThread().setContextClassLoader(realm.getClassLoader());
>
> The only thing there that could be null is the "realm" I guess.  And
> that comes from lines 315, 318 and 319:
> ClassWorld world = new ClassWorld();
> ClassRealm root = world.newRealm("gwt-plugin",
> Thread.currentThread().getContextClassLoader());
> ClassRealm realm = root.createChildRealm("gwt-project");
>
> None of that should be null, of course, so this is a mystery to me.
>
> All that said, please make sure you are using one of the versions of
> GWT-Maven that is designed to use GWT from the official repo.  If you
> are using an older version of GWT-Maven it won't work (different
> structure).  That is part of what the new versions were created to
> address.  (I ask what version we are talking here because your line
> numbers seem strange, line 124 of ScriptWriterUnix is "}" - but I am
> looking at the trunk not the tag - AND you said Windows works, so this
> seems strange.)
>
> If you are using 2.0-beta23, then I would be happy to look into it
> further, let me know. Maybe do the mvn -X thing and dump the entire
> trace here (or attach it to an issue in the tracker or something).
>
> Also for the record, I use GWT-Maven with Linux all the time, it works
> fine on Linux usually.
>
> On Oct 1, 8:15 am, "P.G.Taboada" <[EMAIL PROTECTED]> wrote:
>
> > Hi,
>
> > I just moved my app to use the actual official repo artifacts.
> > It builds perfectly on windows.
> > It fails on linux:
>
> > Caused by: java.lang.NullPointerException
> >         at java.io.File.<init>(File.java:222)
> >         at
> > com.totsp.mavenplugin.gwt.AbstractGWTMojo.buildClasspathList(AbstractGWTMojo.java:
> > 325)
> >         at
> > com.totsp.mavenplugin.gwt.ScriptWriterUnix.writeCompileScript(ScriptWriterUnix.java:
> > 124)
> >         at
> > com.totsp.mavenplugin.gwt.CompileMojo.execute(CompileMojo.java:65)
>
> > Any help?
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to