I'm using the snapshot since yesterday and it seems to be working great.
On Saturday, 18 October 2014 01:02:35 UTC+1, Thomas Broyer wrote:
On Sat, Oct 18, 2014 at 12:26 AM, Thomas Broyer t.br...@gmail.com
javascript: wrote:
On Friday, October 17, 2014 10:58:49 AM UTC+2, Thomas Broyer
Hi Thomas,
Thanks, I'm up and running again with dependency on gwt-dev and
gwt-codeserver...
Just checking: Presumably this is being pragmatic, working with what Maven
gives us, as they are really plugin dependencies? ie the code I'm compiling
shouldn't be coupled to any of gwt-dev or
Hmm, I don't think I can update the maven version in Eclipse properly - on
'Installations' page it says Embedded runtime is always used for
dependency resolution.
Can we switch to gradle? :D
On Friday, 17 October 2014 01:07:49 UTC+1, Brandon Donnelson wrote:
It appears that the
Haven't used eclipse for a long time but I guess you can tell it to use the
installed maven version instead of the embedded runtime.
Sometimes I have the feeling that one needs a Phd degree to master maven
and probably two if you include the integration into an IDE ;-)
On Fri, Oct 17, 2014 at
On Fri, Oct 17, 2014 at 12:48 AM, Colin Alworth niloc...@gmail.com wrote:
Looks like codehaus's snapshot repo is down, so I'm unable to get the
latest gwt-maven-plugin. This url gives a 504 gateway timeout from ngnix
for me:
As far as I can tell, you can tell it to execute with another runtime, but
it always uses the embedded one for dependency resolution.
I agree. It's one of those it's not rocket science, that would be easy
compared to this things :O
On Friday, 17 October 2014 09:57:55 UTC+1, Ümit Seren wrote:
FWIW my app seems to compile and run ok using gwt-maven-plugin 2.6.1 with
gwt 2.7.0-SNAPSHOT... gwt:run launched the codeserver and the auto
recompile seems to be working :)
On Friday, 17 October 2014 08:55:07 UTC+1, salk31 wrote:
Hi Thomas,
Thanks, I'm up and running again with dependency
Hi Drew, what version of maven are you using? mvn -version?
On Friday, October 17, 2014 2:58:03 AM UTC-7, Drew Spencer wrote:
FWIW my app seems to compile and run ok using gwt-maven-plugin 2.6.1 with
gwt 2.7.0-SNAPSHOT... gwt:run launched the codeserver and the auto
recompile seems to be
Hi Brandon. I've never used maven from the command line but my eclipse
(fresh luna) tells me my embedded version is 3.2.1 but I installed 3.2.3
and am using that, though as I mentioned above eclipse always uses the
embedded version for dependency resolution.
So I'm launching with 3.2.3 and
Oh interesting I haven't considered the Eclipse issue yet. Good to know.
I'll be looking at the GPE configuration system later today and this
weekend, I noticed it was broken with the BOM config, so suspect I could
see the issue in that config and I'll check out the options. I'll do some
more
On Friday, October 17, 2014 10:58:49 AM UTC+2, Thomas Broyer wrote:
This is really really strange, as I'd swear that everything was working
for me with Maven 3.0.5 (before sending the patch to update the samples in
GWT, I ran mvn clean verify and then mvn gwt:run). I never mvn
install
Just a note, I'm digging into the GPE m2e project configurator. It looks
like I've got to add a way to ready the dependency management (BOM). I'll
have a test case setup shortly so I can start getting it to read the
pom.xml configuration. Do you think anything is going to change upstream
yet?
Update, GPE seems to be working, so I'm going to run more tests to verify.
On Friday, October 17, 2014 3:35:33 PM UTC-7, Brandon Donnelson wrote:
Just a note, I'm digging into the GPE m2e project configurator. It looks
like I've got to add a way to ready the dependency management (BOM). I'll
On Sat, Oct 18, 2014 at 12:26 AM, Thomas Broyer t.bro...@gmail.com wrote:
On Friday, October 17, 2014 10:58:49 AM UTC+2, Thomas Broyer wrote:
This is really really strange, as I'd swear that everything was working
for me with Maven 3.0.5 (before sending the patch to update the samples in
Nice job
On Friday, October 17, 2014 5:02:35 PM UTC-7, Thomas Broyer wrote:
On Sat, Oct 18, 2014 at 12:26 AM, Thomas Broyer t.br...@gmail.com
javascript: wrote:
On Friday, October 17, 2014 10:58:49 AM UTC+2, Thomas Broyer wrote:
This is really really strange, as I'd swear that
I think I'm getting two errors relating to the bugs in the POM that Thomas
mentions above:
[ERROR] Failed to execute goal
org.codehaus.mojo:gwt-maven-plugin:2.7.0-SNAPSHOT:compile (default-cli) on
project UsavAppV7: Failed to resolve artifact: Some problems were
encountered while processing
On Thu, Oct 16, 2014 at 11:10 AM, Drew Spencer slugmand...@gmail.com
wrote:
I think I'm getting two errors relating to the bugs in the POM that Thomas
mentions above:
[ERROR] Failed to execute goal
org.codehaus.mojo:gwt-maven-plugin:2.7.0-SNAPSHOT:compile (default-cli) on
project UsavAppV7:
I'm using Eclipse Kepler with m2e 1.4.0.2xx. I think my maven version is
3.0.4 - it's the one that came embedded with eclipse. I'll try the new
eclipse and see what that says.
On Thursday, 16 October 2014 10:38:27 UTC+1, Thomas Broyer wrote:
On Thu, Oct 16, 2014 at 11:10 AM, Drew Spencer
I have the same issue with maven 3.0.5
[ERROR] Failed to execute goal
org.codehaus.mojo:gwt-maven-plugin:2.7.0-SNAPSHOT:compile (gwt-compile) on
project genophenbrowser-client: Failed to resolve artifact: Some problems
were encountered while processing the POMs:
[ERROR] [ERROR] Non-resolvable
gwt-maven-plugin snapshots are deployed to codehaus, but the plugin depends
on GWT snapshots which are at sonatype, and Maven thus uses the
pluginRepositories to download them as dependencies of the gwt-maven-plugin
(it doesn't look like it uses the repositories listed in gwt-maven-plugin's
own
no it didn't help unfortunately.
But I upgraded to maven 3.2.1 and the error went away.
On Thu, Oct 16, 2014 at 1:57 PM, Thomas Broyer t.bro...@gmail.com wrote:
gwt-maven-plugin snapshots are deployed to codehaus, but the plugin
depends on GWT snapshots which are at sonatype, and Maven thus
This is strange, because I tested the samples with Maven 3.0.5 (this is
still my default version) and didn't have this problem :-/
On Thu, Oct 16, 2014 at 2:11 PM, Ümit Seren uemit.se...@gmail.com wrote:
no it didn't help unfortunately.
But I upgraded to maven 3.2.1 and the error went away.
Hmm that's weird. I remember that when I tried to compile the same app with
2.7.0-SNAPSHOT (gwt-maven plugin) two weeks ago it worked fine with maven
3.0.5.
However I have now a different issue:
I have used your gwt archetype (
https://github.com/tbroyer/gwt-maven-archetypes) and I have three
Somehow I made the requestfactory error go away but I'm still getting this
one:
[ERROR] Non-resolvable import POM: Could not find artifact
org.ow2.asm:asm-parent:pom:5.0.3 @ com.google.gwt:gwt:2.7.0-SNAPSHOT,
Ok this error has nothing to do with GWT but with Errai. They iterate
through the current working directory (CWD) to find the output folder to
generate the server side marshalling classes. If the CWD has symbolic links
this will apparently result in a NullPointerException. I have the strong
I'm' also having some trouble. I get errors related to both requestfactory
and asm-parent.
You can see the error message and pom.xml at this gist:
https://gist.github.com/tskardal/0d8287da4265c0fddfc8
I've created a project using the maven archetype, modified the versions and
added the
Thomas I'm noticing the issue coming up on my config. I haven't drilled
down to why yet. I copied the samples config.
[INFO]
[INFO] BUILD FAILURE
[INFO]
I found the reason, trying to find a workaround.
The repository definition is causing it to try to download from snapshots
where it doesn't exist.
--
You received this message because you are subscribed to the Google Groups
Google Web Toolkit group.
To unsubscribe from this group and stop
Looks like codehaus's snapshot repo is down, so I'm unable to get the
latest gwt-maven-plugin. This url gives a 504 gateway timeout from ngnix
for me:
https://nexus.codehaus.org/content/groups/snapshots-group/org/codehaus/mojo/gwt-maven-plugin/2.7.0-SNAPSHOT/maven-metadata.xml
If I set gwt-user
It appears that the org.ow2.asm:asm-parent:pom:5.0.3 @ is fixed after
upgrading to maven 3.2.3. The pom issue goes away.
Brandon
On Thursday, October 16, 2014 3:48:07 PM UTC-7, Colin Alworth wrote:
Looks like codehaus's snapshot repo is down, so I'm unable to get the
latest
Hi all,
If you're using 2.7.0-SNAPSHOT, your build might start failing as of today
as we started unbundling dependencies from gwt-dev as published to the
Central Repository.
java.lang.NoClassDefFoundError: org/objectweb/asm/ClassVisitor
If you get this error, be sure to also update your
Great news! thanks to all the team for all the work on SDM, did the
migration to 2.7 last week, brought me the smile again while working with
GWT.
On Sun, Oct 12, 2014 at 5:35 AM, Thomas Broyer t.bro...@gmail.com wrote:
Hi all,
If you're using 2.7.0-SNAPSHOT, your build might start failing as
Adding http://mvnrepository.com/artifact/org.ow2.asm/asm/5.0.3 it worked
again.
El diumenge 12 d’octubre de 2014 10:35:09 UTC+2, Thomas Broyer va escriure:
Hi all,
If you're using 2.7.0-SNAPSHOT, your build might start failing as of today
as we started unbundling dependencies from
Yes, there's actually a bug in the parent POM:
https://gwt-review.googlesource.com/9642
(note: you need more than asm –see POM–, but possibly only under some
conditions – classic DevMode?)
On Sun, Oct 12, 2014 at 8:53 PM, Ramon Salla rsal...@gmail.com wrote:
Adding
34 matches
Mail list logo
